Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My colleague and I are experimenting with replacing Ghost with WDS (Server 2008 R2 SE) and MDT 2010. I intially built the virtual machine and added the WDS service but at the time I also imported images directly. My colleague has since added (WAIK and) MDT but now we keep getting various errors trying to deploy images.

It started to get untidy (and we've found a lot more helpful resources since we originally started) so we blew away the VM and have just installed the OS for a fresh start. Before we do anything else though I was just wondering if there are any changes the last install would have made to DNS, DHCP, AD or any other services running in our domain that we should undo before we start again?

share|improve this question
up vote 0 down vote accepted

Do you have DHCP running on the same server? If you do then you will obviously have to deal with the DHCP, but also just make sure that Option 60 is set to PXEClient. If the WDS Server was not on a DHCP server then the two DHCP options (and really its only 1) that you will want to take a look at is Option 66 and Option 67. Option 66 is probably the only one you will have to change as its value should be the Boot Server Host Name. Option 67 is for the Bootfile Name, which avoids making the client having to select what they should boot into.

I'm farily certain nothing is added into AD that would need to be changed as my understanding of how WDS uses AD is to determine whether or not the computer is "Known" (GUID exists in AD) or "Unknown" (GUID does not exist).

share|improve this answer
Thanks for that help. And no, it's a separate DHCP server. The main reason I asked is that something I read recently said MDT makes changes to DNS for you... Found it… (slide 2) – Matthew Jul 7 '11 at 3:50
Our main concern was DNS but it turns out it wasn't a problem. – Matthew Jul 31 '11 at 23:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.