SCCM configMgr Multicast service point. Critical.Help.

[clivebuckwheat]

Hi

 

I checked my test SCCM server and the configMgr Multicast service point is Critical.Would this cause advertisements not to run on machines?, more importantly how can I fix this?

 

 

Here is the logs for the critical error on for the multicast service point

 

Error Milestone QAZ 6/25/2011 8:40:23 AM W2K8-DC1 SMS_MULTICAST_SERVICE_POINT 7102 MCS Control Manager detected MCS is not responding to HTTP requests. The http error is 500. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MCS. For more information, refer to Microsoft Knowledge Base article 838891. 2220 1716

Error Milestone QAZ 6/25/2011 8:39:59 AM W2K8-DC1 SMS_DISCOVERY_DATA_MANAGER 679 This component failed to retrieve the list of SMS sites from the site database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. 2800 1716

Error Milestone QAZ 6/25/2011 8:39:57 AM W2K8-DC1 SMS_OBJECT_REPLICATION_MANAGER 1104 SMS Executive detected that this component stopped unexpectedly. Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly. Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. 2128 1716

Error Milestone QAZ 6/25/2011 8:39:55 AM W2K8-DC1 SMS_CI_ASSIGNMENT_MANAGER 5804 SMS CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. 2376 1716

Error Milestone QAZ 6/25/2011 8:39:55 AM W2K8-DC1 SMS_HIERARCHY_MANAGER 3303 SMS Hierarchy Manager cannot connect to the SMS site database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. 2908 1716

[anyweb]

i'm curios what your component logs state look like, is the management point or anything else failing ?

[clivebuckwheat]

i'm curios what your component logs state look like, is the management point or anything else failing ?

 

Where can I find these logs so I can post them?, thank you for the reply.

[tacke]

Where can I find these logs so I can post them?, thank you for the reply.

The MCR has a lot of prerequisites on the system where it should be installed:

1. W2k8 OS

2. WDS should be installed before enabling MCR

3. IIS and WEBDAV, ISAPI ext and IIS6 management compatibility must be installed before

4. UDP Ports should be configured on Firewalls (Soft+Hardware) for OS deployment with Multicast

5. Bits should be configured before enabling

6. Distribution Point (not Branch and not Server share) should be configured before enabling MCR (MCR cannot be enabled if this role is not installed!)

7. Windows Firewall settings has to be adjusted to allow connection of clients

8. Local Security (GPEDIT.MSC / SEPOL.MSC) has to be adjusted when running SCCM on a DC!

9. OS packages should be activate for Multicast and deployed to the MCR DP after enabling MCR!

10. Verify that the MP has signed the MCR. Check SignedSerializedMCSkey in Registry section of MCS. It should not be empty otherwise MCR will not work in your environment!

 

ON other server:

11. Healty SCCM primary Server with MP is the first preliminary as the MP is responsible for the signing of the Role!

12. DHCP Service should be configured for dyn. Multicast client support only if you not use the static configuration within SCCM or WDS for Multicast clients

13. IPHelper should be configured in segmented networks to reach the WDS,PXE Server

 

 

OPTIONAL INFORMATION

ADD Network Access Account User Account to the PXE share with read rights to all folders.

=> After configuration of the ACL right for the Network Access Account deploy your WinPE images only to the PXE Share

and not as always suggested also to "normal" package shares! During the Setup of the Role the Network Access Account will not be added to the PXE share!

[tacke]

The MCR has a lot of prerequisites on the system where it should be installed:

1. W2k8 OS

2. WDS should be installed before enabling MCR

3. IIS and WEBDAV, ISAPI ext and IIS6 management compatibility must be installed before

4. UDP Ports should be configured on Firewalls (Soft+Hardware) for OS deployment with Multicast

5. Bits should be configured before enabling

6. Distribution Point (not Branch and not Server share) should be configured before enabling MCR (MCR cannot be enabled if this role is not installed!)

7. Windows Firewall settings has to be adjusted to allow connection of clients

8. Local Security (GPEDIT.MSC / SEPOL.MSC) has to be adjusted when running SCCM on a DC!

9. OS packages should be activate for Multicast and deployed to the MCR DP after enabling MCR!

10. Verify that the MP has signed the MCR. Check SignedSerializedMCSkey in Registry section of MCS. It should not be empty otherwise MCR will not work in your environment!

 

ON other server:

11. Healty SCCM primary Server with MP is the first preliminary as the MP is responsible for the signing of the Role!

12. DHCP Service should be configured for dyn. Multicast client support only if you not use the static configuration within SCCM or WDS for Multicast clients

13. IPHelper should be configured in segmented networks to reach the WDS,PXE Server

 

 

OPTIONAL INFORMATION

ADD Network Access Account User Account to the PXE share with read rights to all folders.

=> After configuration of the ACL right for the Network Access Account deploy your WinPE images only to the PXE Share

and not as always suggested also to "normal" package shares! During the Setup of the Role the Network Access Account will not be added to the PXE share!

LOGS location: SCCM installation folder \logs

Verify services and corresponding locks: Tools\ConfigMgr Service Manager or registry under HKLM/Software/Microsoft/ccm/logging...or HKLM/software/wow6432node\microsoft/ccm/logging...