I've been deploying Windows with wds 2012 to clients running in BIOS mode forever, using wds 2012 and dhcp in the same network, but on different boxes. clients are in a different network and on the DHCP server the dhcp-options 66 and 67 are in place. I tried to deploy to a client in UEFI mode: pxe-e16: No offer received
I removed the DHCP options and set up a ip helper address pointing to wds.
My uefi client started booting from LAN, it downloaded wdsmgfw.efi and started downloading the boot.wim, just perfect.
BUT This worked for some time, maybe a day, and then, suddenly: pxe-e16: No offer received.
Then I would put the dhcp options 66/67 in place again in order to be able to deploy again.
After some time, e.g 1 day, I would re-remove the dhcp-options and pxe boot with uefi clients would work again.
and on and on and on...

• Edited by woodrapp Friday, June 12, 2015 11:33 AM

Does not MDT rely on WDS in terms of PXE boot? Why should that work any better?

• Edited by woodrapp Monday, June 22, 2015 9:50 AM

Hi,

Microsoft has a slew of deployment tools to choose. Depending on the number of computers you need to deploy Or the current skill set of your IT pros, I've had people ask "Do I need to install ConfigMgr, Windows Deployment Services, the Microsoft Deployment Toolkit, and the Windows Automated Installation Kit (WAIK) for Windows 7. The answer is... well, it depends on your deployment needs.

Yes, you can integrate WDS with MDT for two features: the ability to PXE boot to begin a deployment and multicasting functionality for MDT images. Integrating MDT and WDS for PXE boot requires you to store the MDT generated Windows Preinstallation Environment (WinPE) to WDS's boot images. But the features of MDT is the way it compartmentalizes your entire deployment solution. This makes it a snap to manage your images, from adding/removing drivers to easily swapping out the operating system you would like to deploy. So it is a tool kit for deployment not just for WDS.

Regards,

D. Wu