Hi all,
we use "WUS Offline Update" tool to apply latest MS updates to our reference images - e.g. we applied latest 2018-02 Cummulative Update (KB4074588)
to "Windows 10 Enterprise x64 English 1709" which lifted OS version to Build numver 16299.248 before we sysprep it and create teh WIM using MDT
as it is best practice to keep a reference image offline to avoid issues with updated UWP apps.
So the assumption would be that a new machine which got this image applied is already at the latest patch level.
But when we click on "Check for Updates" in the "Settings" app of such machine it re-detects the same 2018-02 update and also redownloads it.
Then when it comes to installation the Windows Update client or the CU itself recognizes that it is already installed and therfore does not ask for a reboot.
This is bad behaviour, as it creates unnecessary network load.
Therfore our questions:
1) Is this a Windows bug or intended bahaviour or caused by the design of the Windows Update client?
2) Is there a way to avoid this?
3) Can it be caused by our "Cleanup before sysprep" script (see below) which runs in the MDT Task sequence to create teh Reference image?
Additional information:
1. We point our machines to an internal WSUS server to control the OS updates but let the clients download from MS Windows update CDN network directly.
2. We run the "Cleanup before Sysprep" script from
https://deploymentbunny.com/2014/06/05/ ... ge-in-mdt/
https://github.com/DeploymentBunny/File ... oreSysprep
to compress our reference image which of course also wipe the "C:\Windows\SoftwareDistribution" folder*
*another source, which seems to do the same things but is based on Powershell is this one:
https://gallery.technet.microsoft.com/s ... o-12de6135
Many Thanks!
Sebastian Rübesamen