In this deployment of SCCM 2012 R2, the WSUS is installed on a separate server.
There are so many options that need to configured to make SCCM work that I missed one thing and SCCM was not able to do initial configuration on WSUS server which is done at the 1st Sync.
Upon checking Monitoring/Component Status/SMS_WSUS_SYNC_MANAGER.
The best way to deploy windows updates according to my experience is by using Automatic Deployment rules.
To setup a working Deployment rule there are few configurations and settings that need to be in place and working without errors.
1. Software Update Point (SUP) : Products and Sync Schedule
2. Site System role : Proxy Account
3. Device Collection : Query based collection
4. Client Settings
5. Automatic deployment rule
In one of my recent attempt to configure SCCM 2012 SP1 for windows 2012 R2 updates, I saw that the clients was scanning the system for updates but they were not getting installed on system.
Upon checking UpdatesDeployment.log on target system, the message “Waiting for third party orchestrator to initiate installation”
While doing a test of MDT task sequence, I ran into an error “Failed to Run Task Sequence : Program files for <SITECODE>00001 cannot be located on a distribution point”
The keyword in this message is “Distribution Point” which should direct us to check if we missed any package that has not been distributed.
If we check Monitoring / Distribution Status / Content Status and refer to the PackageID mentioned in the error “VHL0001” we see the compliance column is blank.
When we distribute this package to the distribution point, the compliance will show 100% and Task Sequence should move ahead.