Windows Updates during OSD

[Chris_J]

Hi All,

 

I have an OSD task sequence with Windows Updates deployed to the collection and it is working ok, finds the updates and appears to install them, but I can't figure out why it sits there doing nothing for maybe an hour after the last update is installed.

 

Currently it is sat on Installing 132 of 132 Updates, eventually it will reboot but sometimes the updates fail to apply. Any ideas where I'm going wrong?

 

 

[Chris_J]

Also getting this in the WUAHandler.log

 

Unable to read existing WUA resultant policy. Error = 0x80070002. WUAHandler 11/05/2015 11:21:50 AM 1108 (0x0454)
Seems Group Policy is not yet initialized because client is in provisioning mode, writing WSUS Server location in registry. WUAHandler 11/05/2015 11:21:50 AM 1108 (0x0454)
Restarting WU Agent service... WUAHandler 11/05/2015 11:21:50 AM 1108 (0x0454)
Stopped the service 'wuauserv' successfully WUAHandler 11/05/2015 11:21:50 AM 1108 (0x0454)
Waiting for 30 secs for policy to take effect on WU Agent. WUAHandler 11/05/2015 11:21:51 AM 1108 (0x0454)
Added Update Source ({9295CFAB-B7A6-45B9-8E5F-EE52ECD5CDA7}) of content type: 2 WUAHandler 11/05/2015 11:22:21 AM 1108 (0x0454)
Scan results will include all superseded updates. WUAHandler 11/05/2015 11:22:21 AM 1108 (0x0454)
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'A38C835C-2950-4E87-86CC-6911A52C34A3')) WUAHandler 11/05/2015 11:22:21 AM 1108 (0x0454)
Async searching of updates using WUAgent started. WUAHandler 11/05/2015 11:22:21 AM 1108 (0x0454)
Async searching completed. WUAHandler 11/05/2015 11:22:24 AM 1220 (0x04C4)
Successfully completed scan. WUAHandler 11/05/2015 11:22:24 AM 1108 (0x0454)
Its a WSUS Update Source type ({9295CFAB-B7A6-45B9-8E5F-EE52ECD5CDA7}), adding it. WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Existing WUA Managed server was already set (http://NAT:8530), skipping Group Policy registration. WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Added Update Source ({9295CFAB-B7A6-45B9-8E5F-EE52ECD5CDA7}) of content type: 2 WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Scan results will include all superseded updates. WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Async searching of updates using WUAgent started. WUAHandler 11/05/2015 11:22:24 AM 2276 (0x08E4)
Async searching completed. WUAHandler 11/05/2015 11:23:15 AM 3992 (0x0F98)
OnSearchComplete - Failed to end search job. Error = 0x80244010. WUAHandler 11/05/2015 11:23:15 AM 3268 (0x0CC4)
Scan failed with error = 0x80244010. WUAHandler 11/05/2015 11:23:15 AM 3268 (0x0CC4)

[Chris_J]

Also is the task sequence variable _SMSTSMediaType Not Equals FullMedia required for the Install Updates step?

[simulacra75]

Personally, and your opinion may differ here, i wouldn't have the Apply Software Updates step in there at all. In my own experience have all the updates applied in your Build & Capture and redo this every 6 months (my own schedule). The Apply Software Updates step is a potential gothca in OSD and adds considerable time to the rollout of an image (as you are seeing now). Of course the downside is that the updates apply once the OS has been applied but this is not a huge issue either and you can at least see progress/faliures from within Windows itself. That's the way i would do it.

[Garrett804]

I'd agree, Update your image more often and include the updates pre-installed in the package. I wouldn't exactly do 6 months but more like 3 months or each quarter to be specific. Microsoft puts out a lot more updates now and days then they ever did in the past so each patch tuesday you may find 20+ updates sometimes.