MDT reboots before Deployment Wizard

mdtmdt-2013windows 10windows-server-2008

I was having issues with Windows 10 not showing a language to install in MDT, so I updated MDT to 2013u2 and regenerated the boot images. Now when I use PXE boot, the MDT background comes up for about 30 seconds, then cuts to black and reboots to the hard disk.

I tried adding new drivers, disabling MDAC in the boot images, I removed some settings in the CustomSettings.ini, and updated the boot image after doing each of those. Nothing has worked so far.

Some extra info; I'm using MDT with WDS on Server 2008 R2, no SCCM.

Could rolling back to 2013u1 fix this? Is it safe to do so? Is there anything else I can do?

I was hoping to get Windows 10 deployment working properly by the end of the day but now I'm just hoping to get MDT up and running again haha…

Best Answer

So I figured it out... for the most part. During the boot image generation, DISM does not add any of the WinPE Optional Components for 64 bit, works perfectly fine for 32 bit, but it hates 64 bit for some reason. It'll state that the specified package is not applicable to this image. I tried manually mounting the boot.wim and adding the components but that didn't work either. I suspect that it's because the version of WADK is for build 10586 of 10, and that the boot.wim is based on an older build... but that wouldn't explain why it worked for 32 bit...

Related Solutions

Adding Drivers To MDT 2012 Deployment Share

The answer to 1 and 3 is "yes, but..." You may want to organize your drivers according to whether you need to use them in the boot (PE) images or the install images. Separating the drivers by model of computer can make it easier to replace the correct drivers when new versions are released. Updating the deployment share depends on where the drivers are going to be used.

The answer to number 2 is, If you are adding drivers to the boot image, then yes, update the share and regenerate the boot images (using selection profiles for the boot image drivers is advised), then, yes you will have to replace the boot images in WDS to use these new boot images.

For the OS deployment, MDT uses PnP calls to install the correct drivers. However,there is a task named 'Inject drivers' where you can specify which driver selection groups get installed. If you don't have many different models, you can just leave it at 'Everything', but as time you get many models or different operating systems, the selection profiles are very handy for keeping it all straight.

For the boot images and USB or DVD installations this keeps the size of media smaller since you are only using the drivers you need instead of all of them. Johan Arwidmark has a great article on the 3 methods of driver management in MDT that should help you to decide the proper course for your situation.

Hope this helps,

(signature for disclosure purposes)

David

Windows Outreach Team - IT Pro

MDT 2013 – Language to Install Missing

You need to add the skip local selection to your system otherwise it will still ask what you want to do and your settings do nothing.

SkipLocaleSelection=YES

I have added mine above the local settings like this:

[Settings]
Priority=Default
Properties=MyCustomProperty
DeploymentType=NEWCOMPUTER

[Default]
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipDeploymentType=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES

JoinWorkGroup=Elliot Labs



 SkipLocaleSelection=YES



 KeyboardLocale=0409:00000409

UserLocale=en-US
UILanguage=en-US

SkipTimeZone=YES
TimeZoneName=Eastern Standard Time

SkipSummary=YES

Best Answer

Related Solutions

Adding Drivers To MDT 2012 Deployment Share

MDT 2013 – Language to Install Missing

Related Topic