Each time a deployment share is updated in MDT the drivers and settings contained within that share are added to a boot WIM and a boot ISO that is used to connect to the MDT server. The good thing is that MDT has a provision for creating it’s boot sources built-in. ![]() This is where the focus of this post will reside. MDT USB keys are copies of Windows PE, designed to connect to MDT and pull an image from the server. Pre-execution Environment (PXE) requires the use of a Windows Server configured with the Windows Deployment Services (WDS) role. MDT uses two ways to connect to the server over the network, USB key, and PXE. 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. Networking between the MDT/WDS server and the target clients must be clear and working. The crucial point to all of this is the network. To do this, MDT uses a series of steps in a task sequence that perform the necessary operations to facilitate installation. ![]() The main point of MDT and WDS is to place Windows on a computer’s disk drive.
0 Comments
Leave a Reply. |