Ryfujk

How to count occurrences of text in a file?

What does convergence in distribution "in the Gromov–Hausdorff" sense mean?

Why am I allowed to create multiple unique pointers from a single object?

Preparing Indesign booklet with .psd graphics for print

Why do professional authors make "consistency" mistakes? And how to avoid them?

Why do remote companies require working in the US?

WOW air has ceased operation, can I get my tickets refunded?

How did people program for Consoles with multiple CPUs?

Rotate a column

Which tube will fit a -(700 x 25c) wheel?

Inappropriate reference requests from Journal reviewers

Is there a difference between "Fahrstuhl" and "Aufzug"

Won the lottery - how do I keep the money?

Why do airplanes bank sharply to the right after air-to-air refueling?

Is there a way to save my career from absolute disaster?

Anatomically Correct Strange Women In Ponds Distributing Swords

Can we say or write : "No, it'sn't"?

What exact does MIB represent in SNMP? How is it different from OID?

Are there any limitations on attacking while grappling?

Is it my responsibility to learn a new technology in my own time my employer wants to implement?

To not tell, not take, and not want

Bold, vivid family

Should I tutor a student who I know has cheated on their homework?

Written every which way

MDT reboots before Deployment Wizard

0

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...

windows-server-2008 windows-10 mdt mdt-2013

share|improve this question

asked Feb 5 '16 at 19:38

campj90campj90

262

bumped to the homepage by Community♦ 11 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to make sure, did you update your deployment share after the 2013u2 install or just regen the image? Also do you have a logging target setup?
  
  – Zypher
  Feb 5 '16 at 19:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I updated the share and regenerated the boot images. I don't currently have logging set up but I'll configure it and try doing a PXE boot again.
  
  – campj90
  Feb 5 '16 at 20:52
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So I enabled logging and nothing populates in the shared log when I do a PXE boot. I was able to pull up the command prompt and that seemed to halt the reboot. I had seen that there is supposed to be a directory in X: called MININT, but I don't have that. So maybe something is really messed up with the boot image? In X:, I have Deploy, Program Files, Program Files (x86), sources, Users, Windows, and the unattend.xml file.
  
  – campj90
  Feb 5 '16 at 21:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  hmm, I'd try a full regen again sounds like something went wrong. The other thing I can think of is it is relying on something in 2012+. Also, another check - you've replaced the boot image in WDS after regenning right?
  
  – Zypher
  Feb 5 '16 at 22:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yep, I've replaced it in WDS. I've removed the boot image in the WDS MMC console, and then readded it, and also tried stopping the WDS server, copying and replacing the Lite Touch wim from the DeploymentShare to RemoteInstall, neither made any noticeable difference. I'm supposed to upgrade the server to a new 2012 server, but I've been waiting since November for one of the admins to give me access to the 2012 server...
  
  – campj90
  Feb 5 '16 at 22:23
  
  
  

  
  
  
  

add a comment | 

0

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...

windows-server-2008 windows-10 mdt mdt-2013

share|improve this question

asked Feb 5 '16 at 19:38

campj90campj90

262

bumped to the homepage by Community♦ 11 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to make sure, did you update your deployment share after the 2013u2 install or just regen the image? Also do you have a logging target setup?
  
  – Zypher
  Feb 5 '16 at 19:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I updated the share and regenerated the boot images. I don't currently have logging set up but I'll configure it and try doing a PXE boot again.
  
  – campj90
  Feb 5 '16 at 20:52
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So I enabled logging and nothing populates in the shared log when I do a PXE boot. I was able to pull up the command prompt and that seemed to halt the reboot. I had seen that there is supposed to be a directory in X: called MININT, but I don't have that. So maybe something is really messed up with the boot image? In X:, I have Deploy, Program Files, Program Files (x86), sources, Users, Windows, and the unattend.xml file.
  
  – campj90
  Feb 5 '16 at 21:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  hmm, I'd try a full regen again sounds like something went wrong. The other thing I can think of is it is relying on something in 2012+. Also, another check - you've replaced the boot image in WDS after regenning right?
  
  – Zypher
  Feb 5 '16 at 22:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yep, I've replaced it in WDS. I've removed the boot image in the WDS MMC console, and then readded it, and also tried stopping the WDS server, copying and replacing the Lite Touch wim from the DeploymentShare to RemoteInstall, neither made any noticeable difference. I'm supposed to upgrade the server to a new 2012 server, but I've been waiting since November for one of the admins to give me access to the 2012 server...
  
  – campj90
  Feb 5 '16 at 22:23
  
  
  

  
  
  
  

add a comment | 

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...

windows-server-2008 windows-10 mdt mdt-2013

share|improve this question

asked Feb 5 '16 at 19:38

campj90campj90

262

share|improve this question

asked Feb 5 '16 at 19:38

campj90campj90

262

share|improve this question

asked Feb 5 '16 at 19:38

campj90campj90

262

asked Feb 5 '16 at 19:38

campj90campj90

262

asked Feb 5 '16 at 19:38

campj90campj90

262

1 Answer
1

active

oldest

votes

0

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...

share|improve this answer

answered Feb 5 '16 at 23:49

campj90campj90

262

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Try having MDT building the test images with no MDT components. Load those into WDS and see if you have the same issues. @campj90
  
  – Elliot Labs
  Feb 7 '16 at 13:31
  
  
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f754329%2fmdt-reboots-before-deployment-wizard%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

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...

share|improve this answer

answered Feb 5 '16 at 23:49

campj90campj90

262

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Try having MDT building the test images with no MDT components. Load those into WDS and see if you have the same issues. @campj90
  
  – Elliot Labs
  Feb 7 '16 at 13:31
  
  
  

  
  
  
  

add a comment | 

0

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...

share|improve this answer

answered Feb 5 '16 at 23:49

campj90campj90

262

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Try having MDT building the test images with no MDT components. Load those into WDS and see if you have the same issues. @campj90
  
  – Elliot Labs
  Feb 7 '16 at 13:31
  
  
  

  
  
  
  

add a comment | 

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...

share|improve this answer

answered Feb 5 '16 at 23:49

campj90campj90

262

share|improve this answer

answered Feb 5 '16 at 23:49

campj90campj90

262

answered Feb 5 '16 at 23:49

campj90campj90

262

answered Feb 5 '16 at 23:49

campj90campj90

262