Recently for a customer, we ran into an issue in which the SCCM 1511 upgrade was hanging at the following screen.
If we open the SCCM install log file on the primary site, found at C:\ConfigMgrSetup.log, we will see the following message:
This step should only take a few minutes to complete, if you’ve waited a while, like 20 minutes for us–then go ahead and help SCCM out.
It’s trying to kill the SMS Component Manager service, and the SMS Exec service. If you’ve got a complex environment, it can take a long time to complete this step. Go ahead and stop the services manually using the task manager.
If this doesn’t work (it didn’t work for me, the services hung at ‘stopping’), you can use powershell to kill the service instead.
From the Task manager, look at the process ID for your SMS component manager service, and then run
Stop-Process -ID SMSExecID,SMS_SITE_COMPONENT_MGRID
And your install should proceed with no issues!
I had a similar issue, except in my case Trend OfficeScan was holding up the WMI service to it’s listener service so I had to unload the AV before proceeding….
LikeLike
I encountered this issue in my environment while installing baseline 1702, but I noticed in my sitecomp.log that SCCM was very busy stopping components on all my site servers so I left it alone. It took more than 20 minutes for it to shut down all the services on every DP and component server in my environment, but it finally succeeded without intervention.
LikeLike
Jason, Thank you for the tip! We have a large infrastructure and monitoring sitecomp.log helped to know what was happening.
LikeLiked by 1 person