Manually trigger (re)publishing of SCCM site information to AD

During an upgrade of SCCM I ran into a scenario where I had to delete some (mSSMSManagementPoint) items from the System Management container that SCCM creates as part of publshing site information for clients to use.

All documentation says SCCM should be the only one to create items in this container, however, I couldn’t find any documented way of telling SCCM to re-check the items and create any that were now missing.

Solution: The Site Component Manager controls this. Stop and Start the SMS_SITE_COMPONENT_MANAGER service and SCCM will republish the data.

After restarting the service, eventually the following lines appear in sitecomp.log:

A note: In my specific scenario I found that the Component Manager was still busy processing work related to the Site upgrade. This queue of work (which took many hours for me) had to be processed first before the service hit the AD publish section. I assume the order of processing in SCCM’s code has the AD publishing as one of the last things to do.