Failed to Sync Update. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted.

I was seeing the above error in the Configuration Manager 2012 SP1 wsyncmgr.log in a customer environment and I suspected this was as a result of SQL services being interrupted during the WSUS syncronisation process – which is never a good thing.  Despite trying to remove classifications and removing/reinstalling the SUP role the problem persisted.  When I loaded up the WSUS console and filtered for all updates I noticed that around 12 updates were showing that their content download (the EULA) had not been successfully downloaded.  I simply highlighted the affected updates, right clicked and chose to “Retry Download” and these changed to Pending Download and eventually all was OK.  A re-sync in Configuration Manager then resulted in a happy wsyncmgr.log and a successful sync event.

There is apparently a hotfix available for this issue which might be worth a try if you encounter this issue when proxy credentials are required;

http://support.microsoft.com/kb/2838998

Advertisements

Automatic Updates behaviour during Task Sequenced Windows 7 Build

I’ve come to the conclusion that whilst in the Post-Install phase of a Task Sequence, it’s probably not a good idea for the machine being built to go swanning off to Windows Update and start automatically applying minor updates.  As well as undermining the whole concept of centrally managing updates – it throws up the risk of upsetting your ‘Install Software’ task sequence steps as they fight for Windows Installer time.

Thus, I find myself trudging with my wading gear into the murk of the unattend.xml file to yet again change what I feel is behaviour that just shouldn’t be switched on by default.

The setting we are concerned with is the “ProtectYourPC” option in the “x86_Microsoft-Windows-Shell-Setup_neutral” section.  We change this to have a value of “3” which effectively turns off the automatic nature of Windows 7 so that our build can complete exactly as per the plan.  Corporate Group Policy settings come down to lock down the behaviour of Windows Update when all is finished.