Wednesday, December 18, 2013

Microsoft Deployment Toolkit (MDT) - Command Prompt/Window

Spent the last two weeks trying to figure out why my Windows 2012 ISO built with Microsoft MDT 2013 would boot up, then go immediately to a command prompt.  The Windows Deployment Wizard should come up.  I was comparing the wpeinit.log file located in X:\Windows\System32 and noticed the good deployment had the following optional components, while the faulty deployment did not:


Thinking back, when I originally built the working ISO, I disabled McAfee to speed Deployment Share updates.  Having McAfee disabled was allowing all components to be successfully added to the WIM.  With McAfee enabled, certain things were being blocked, such as these optional, but mandatory components.

When I started building this new ISO, McAfee was enabled which was preventing WinPE-HTA, WinPE-WMI and WinPE-WSH from being added properly.  These items are mandatory in order for the MDT scripts to properly execute and launch the Deployment Wizard.  You can see these in the log output when updating the Deployment Share and Media:


So, when you are updating your Deployment Share or Media resources, ensure to disable McAfee or any other virus scanner.

1 comment:

  1. After Removing the McAfee following issue was resolved. Thank you so much for your information.

    ReplyDelete