Issues with SCCM CB Updates kb4016483 and 1702

By | April 1, 2017

Although the prerequisite check and the installation ended with success two components did not install and the SMS_SITE_COMPONENT_MANAGER retried the installation every 60 minutes.

The main problem was that the restart the WMI service (winmgmt) failed and stopped the SMS Agent Host which is vital for the Management Point.

In case you experience the same, here’s a description how to fix the problems.

Issue 1: SCCM fails to stop the Windows winmgmt service to install the Reporting Service Point Server (it doesn’t become clear from the logs which component causes the problem until the installation starts successfully)

Symptoms: SMS Agent Host is not running so that the Management Point stops working. http://[server]/sms_mp/.sms_aut?mplist returns error 500 since IIS is not responding.

Error message 1090 in the events of the component server (System Status->Site Status): “Site Component Manager could not stop the winmgmt service on site system.”

Fix: During the installation, the Site Component Manager tries to stop the service Windows Management Instrumentation (winmgmt). If you look at the dependencies, you see that other services depend on it as well and have to be terminated before WMI can be stopped. Try net stop winmgmt to test what is wrong. I found that the IP Helper got stuck in the state stopping. Unfortunately, the SMS Host Agent was terminated successfully. The SMS Host Agent service gets installed with the Management Point role. Thus, the Management Point stops functioning. Since the Site Component Manager retries the installation every 60 minutes in case of a failure, a manual restart doesn’t help for long.

Terminating the IP Helper Service fixed the problem:

Run sc queryex iphlpsvc to get the PID of the process

Run taskkill /f /PID [PID #]

Afterwards you just have to wait for the Component Manager to start the installation the next time (it retries every 60 minutes). Footnote: I heard and read that the same may happen with other dependencies and there have obviously been cases where a TrendMicro service depended of winmgmt.

Issue 2: SCCM Update fails to run the bgbsetup (SMS_NOTIFICATION_SERVER)

The problem was fixed by a modification of the .Net Framework configuration file regsvcs.exe.config in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 and a restart of the SMS_SITE_COMPONENT_MANAGER afterwards (with a server restart you are probably on the safe side).

The installation started to work after adding the bold lines to the regsvcs.exe.config:

<?xml version =”1.0″?>

<configuration>
   <startup useLegacyV2RuntimeActivationPolicy=”true”>       
      <requiredRuntime safemode=”true” imageVersion=”v4.0.30319″ version=”v4.0.30319″/>

   </startup>
   <runtime>
      <loadFromRemoteSources enabled=”true”/>
   </runtime>
</configuration>

 

2 thoughts on “Issues with SCCM CB Updates kb4016483 and 1702

Leave a Reply

Your email address will not be published.