Optimize the boot image updating process completely regenerate the boot
Once the deployment share has been successfully updated and has generated the Windows PE volumes in the desired configurations, we need to get those onto the WDS server, or portable media.
Even with extreme customization, the ISO for the deployments share’s Windows PE volume is pretty small (by today’s standards).
Pre-execution Environment (PXE) requires the use of a Windows Server configured with the Windows Deployment Services (WDS) role.
MDT USB keys are copies of Windows PE, designed to connect to MDT and pull an image from the server. The good thing is that MDT has a provision for creating it’s boot sources built-in.
I rename the WIM description and the ISO file name to follow suit with the deployment share.
When everything is as-desired, the deployment share must be updated to generate/regenerate the Windows PE WIM and ISO files.
This process takes a few moments to complete, so grab a drink…
DHCP, DNS, and even WINS (if you’re feeling nostalgic) all must be working properly or else what could seemingly be an MDT/WDS problem, could actually be a network problem.
MDT uses two ways to connect to the server over the network, USB key, and PXE.