For WDS, the WIM file, created by updating the MDT deployment share, and placed in the “Boot” folder, along with the Windows PE ISOs, must be copied to the WDS server (if WDS, and MDT are on different computers), and used to “replace”, or create the WDS boot volume.
Other details can be set on the Windows PE tab, though the defaults are usually sufficient.For example, I change the wallpaper Windows PE uses to display a message on the screen, while the computer is imaging.I’ve been using a legacy 512MB USB key for my 64-bit MDT Windows PE, which has to be over ten years old by now. Use whatever method is best suited to place the ISO on the USB key as a bootable volume.I like to use a piece of freeware, called “Rufus“, but again use whatever works for you.Selection profiles are found under the “Advanced Configuration” folder, under task sequences.
Simply, right-click the folder to create a new selection profile and drill-down the driver list to select only the Windows PE drivers.
The main point of MDT and WDS is to place Windows on a computer’s disk drive.
To do this, MDT uses a series of steps in a task sequence that perform the necessary operations to facilitate installation. Networking between the MDT/WDS server and the target clients must be clear and working.
Simply booting a PC to that disc or key, and with DHCP working, the PC will connect to the MDT server.
MDT does support the use of static IP addresses at the welcome screen, but DHCP is better and essential if PXE booting is desired. Drivers are the biggest issue with regards to MDT’s Windows PE boot volume.
Pre-execution Environment (PXE) requires the use of a Windows Server configured with the Windows Deployment Services (WDS) role.