SCCM 2012 : Software Updates Process

This is a high-level view of the Windows Update process from a ConfigMgr clients view utilizing a SUP (Software Update Point).

The Software Update process from the ConfigMgr client

  • After refreshing machine policy, kick off the Software Update Scan. We can then see the Software Update Scan Cycle has started via the WUAHandler.log (C:\Windows\CCM\Logs\WUAHandler.log)
  • The Windows Update Handler initiates the Windows Update service against the ConfigMgr SUP. (C:\Windows\WindowsUpdate.log)
  • After the scan is completed, we then run the Software Update Deployment Evaluation Cycle. Use the UpdatesDeployment.log to view this process (C:\Windows\CCM\Logs\UpdatesDeployment.log)
  • The Content Access Service finds the content on the Distribution Point and downloads it
  • Update Deployment attempts to install updates, Service Window Manager blocks the installation (C:\Windows\CCM\Logs\UpdatesDeployment.log)
  • Service Window Manager blocking the installation (C:\Windows\CCM\Logs\ServiceWindowManager.log)

And when the window opens, the updates should install. Check the UpdatesDeployment.log. Also, the WindowsUpdate.log success, and reboot if required (and scheduled).  You can find more detailed info here …

ConfigMgr 2012 Windows Update Client Process

 

Related posts

Leave a Comment