In my ongoing effort to avoid issues with updates that cause multiple reboots, I decided to build a new reference machine from scratch, install updates, then capture it. With that process finished, I deployed the new WIM with my task sequence.
After pacakges and applications are installed, I have the step to run ztiwindowsupdate.wsf. Prior to that step is the use tool kit package step and the gather step. I also set the WSUSServer variable to the local WSUS server. WHen the task sequence runs the ztiWindowsUpdate script, it ignores the WSUS server entirely and uses Microsoft's servers. This causes unwanted updates to be installed, including IE 11 and the Bing Bar. I've created an MDT-integrated TS from scratch and the same issue occurs. How do I figure out why the task sequence variable (and even the customsettings.ini) are being ignored by ztiwindowsupdate.wsf? I looked at the script and found on line 555 the section that configures WIndows Update settings. It should be configuring the registry settings to point to WSUS, but it is seeing WsusServer as blank and not configuring the registry at all. Has anyone else seen this? Thanks, Jeff
