“NOOOOOOO” -Darth Vader
Wait, that didn’t happen, I’m a despecialized camper. So I do what anyone does, rinse and repeat and create a new patched WIM. Ugg same error. Do a deploy from the previous quarter WIM and that works so nothing else was changed. Just not the new B&C WIM. What changed? Checking %WINDIR%PantherUnattend.XML, this section looks fine without any common problems. Parsing the panther logs didn’t really pull up anything other then that there was a syntax error. Back in Unattend.XML start looking closer. Computer name is under 15 characters (its a VM that gets set to ‘VMHost’), No illegal characters in the computer name, serial key is correct, CS.INI is still good, etc. I bet it was something WSUS was giving it. Hmm, back to unattend.xml to do a diff of the unattend.xml against one used for Windows 8.1 as that did a quarterly update process fine. Found one difference under specialized other then the serial key:
<!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->
There are several ways to fix it. I just modified unattend.xml in \MDTSERVERDeploymentShareControlTaskSequenceID. I also changed each XML for each TS.
Another way is to go into the Deployment Workbench and right click your task sequence and goto the OSInfo tab and select edit unattend.xml. Wait a while for it to process as it extracts the WIM. Then use windows system image manager (WSIM) and find (ARCHITECTURE)_Microsoft-Windows-IE-InternetExplorer. Then look for IEWelcomeMsg and right click and disable “write image value”, or delete it. Save the unattend and your good to go. Or open the Unattend.XML in the Control folder directly with WSIM. It was just quicker to edit it with Notepad etc.
Looking at the MDT 2013 templates under %ProgramFiles(x86)%Microsoft Deployment ToolkitTemplates it does not have this setting so MDT 2013 will not create new TS unattends with this and this only affects existing TS created in older versions of MDT. Another reason to create a new TS and migrate steps I suppose. I do that in ConfigMgr each Release or SP and sometimes CU if I suspect it will impact built in Task Sequence steps.
Turns out what the root cause was is they moved from IE9 to IE11 by approving it in WSUS. Starting with IE10, MS deprecated this IEWelcomeMsg setting and replaced with DisableWelcomePage. Additionally, Its deprecated in Windows 8 and up. This is why I deleted it from the XML.