I am trying to set up a basic MDT solution. I have set one up in the past at a previous job and it worked flawlessly, however here I'm running into a problem and am having no luck getting around it.
I've installed Windows Server 2012 and MDT 2013, along with adding on the WDS role. I haven't configured much outside of the defaults for WDS, basically just set PXE response to respond to all clients (and unchecked admin approval). This machine does not run a DHCP server. I looked on the DHCP scope of our DHCP server, it shows options 66/67 checked and the server name of the WDS server is in there as well. I didn't add this but I assume it was put on during the install process (I believe I had to manually make some adjustments at my old job for this).
The PC I have is a Dell Optiplex 755. I have enabled the onbard NIC w/PXE boot option in BIOS and attempted to boot. I get a "TFTP…." error but nothing offering out a DHCP address like I'm used to. In my previous job it pretty much worked right out of the box. I've verified that PortFast is enabled on the port and I've tried a couple different PCs (but both are the same model, only model I have to work with). No matter what, I get the same error.
The subnet the PC is in is a different subnet than where the WDS server is sitting, but there are IP helper statements on the switch and the PCs can get regular DHCP addresses just fine from the DHCP server, just doesn't seem to get offered out a PXE boot option.
I don't know if the problem is a configuration with the server or the PC itself…but after a few days of Googling I'm running out of ideas. Does anyone have a good idea of something it may be?
Best Answer
Well, I ended up figuring out what the problem was (but now on to a new problem, will post a new question). It turns out the Admin before me attempted to setup MDT in the past apparently, and there was a name stuck in DHCP/DNS exactly as I named the new server. So once I deleted it, it boots to PXE just fine!
Thanks you all for your help! I'll be posting a new question shortly on problems accessing the DeploymentShare$. It's frustrating that there are so many hurdles, previously it was a piece of cake to setup!
Thanks again.