Windows Server

Deploy Windows 10 Using MDT and WDS, Part 3: Deploy Windows 10 from a PXE-Enabled Boot Client

Windows 10 Hero

In the second part of this series, I showed you how to customize a Windows 10 image in MDT using a task sequence, and configure WDS. In the third and final part, you’ll test a deployment of Windows 10 over the network on a PXE-enabled boot client.

 

 

Sponsored Content

Maximize Value from Microsoft Defender

In this ebook, you’ll learn why Red Canary’s platform and expertise bring you the highest possible value from your Microsoft Defender for Endpoint investment, deployment, or migration.

Install Windows 10 on a PXE-Boot Client

All that’s left to do is install Windows 10 on a client with a PXE-enabled network card. In this lab, I’m using a Hyper-V (gen 2) virtual machine to test this functionality. Let’s start by making sure that your device or VM is set to boot from the network card. The instructions below are for Hyper-V virtual machines. If you’re using another virtualization product or a physical device, refer to the provided instruction manual to modify the device’s BIOS/UEFI settings.

  • In Hyper-V Manager, right-click the VM in the list of virtual machines and select Settings from the menu.
  • In the Settings dialog box, click Firmware in the list of options on the left, and if Network Adapter is not at the top of the Boot order list, click Network Adapter in the list and use the Move Up button to move it to the top, and click OK.
Configure a Hyper-V VM to boot from the network card (Image Credit: Russell Smith)
Configure a Hyper-V VM to boot from the network card (Image Credit: Russell Smith)
  • Start the VM or physical device. Press F12 when prompted to boot the device from the WDS server.
  • The device will boot using the .wim image specified in the WDS server options. Click Run the Deployment Wizard to install a new Operating System on the Welcome screen of the Microsoft Deployment Toolkit window.
Install a new OS on the device (Image Credit: Russell Smith)
Install a new OS on the device (Image Credit: Russell Smith)
  • In the User Credentials dialog box, enter a domain username and password that has permission to connect to the deployment share on the MDT server, and click OK.
  • In the Windows Deployment Wizard, select the name of the task sequence you’d like to run, and click Next.
Choose the MDT task sequence to run (Image Credit: Russell Smith)
Choose the MDT task sequence to run (Image Credit: Russell Smith)
  • On the Computer Details screen, accept the default settings, and click Next. Alternatively, you can change the computer name, provide credentials to join the device to a domain or change the workgroup name.
Set the computer name, domain and workgroup options (Image Credit: Russell Smith)
Set the computer name, domain, and workgroup options (Image Credit: Russell Smith)
  • On the Move Data and Settings screen, check Do not move user data and settings, and then click Next.
  • On the User Data (Restore) screen, check Do not restore user data and settings, and click Next.
  • On the Product Key screen, check No product key is required, and click Next.
  • Modify the time and locale options on the Locale and Time screen if required, and click Next.
  • On the Ready screen, click Begin.
  • When the OS has finished installing, click Finish in the Success dialog box.
Windows 10 is now installed on the device (Image Credit: Russell Smith)
Windows 10 is now installed on the device (Image Credit: Russell Smith)

In this article, I showed you how to install Windows 10 over the network using MDT and WDS. In the section below, I’ve included some additional information about the process that you might find useful in your testing.

Notes from the Field

  • Images created using Microsoft’s online media creation tool cannot be used.
  • If DHCP and WDS are installed on the same server, then PXE DHCP options must be added manually.
  • WDS must be installed and running before PXE boot clients receive an IP address from DHCP.
  • WDS requires a partition formatted with NTDS that is not the system partition.
  • Active Directory is not required, but it adds security and management features that would otherwise be unavailable.
  • When adding a boot WIM image to WDS, it can be located remotely on a MDT deployment share.
  • The PC or VM must be assigned at least 800MB of memory during the Windows 10 install process.

Related Topics:

BECOME A PETRI MEMBER:

Don't have a login but want to join the conversation? Sign up for a Petri Account

Register
Comments (1)

One response to “Deploy Windows 10 Using MDT and WDS, Part 3: Deploy Windows 10 from a PXE-Enabled Boot Client”

  1. <p>I have a WDS and MDT installed on a Windows 2012 R2 server. I am unable to successfully install a Windows 10 pro v1803 using the services mentioned. I followed your instructions line by line. My Dell workstation reboots to a device not found, after receiving the Windows 10 v1803 deployment from my WDS and MDT environment. I would really like to master this concept; but I am having a difficult time do so. </p><p><br></p><p>I look within the BIOS\UEFI and I notice the Windows Boot Manager is not present. I feel like this is my issue and I assume the install did not load successfully. I am not getting the last prompt, indicating the operating system deployment completed successful. Can you assist? </p>

Leave a Reply

IT consultant, Contributing Editor @PetriFeed, and trainer @Pluralsight. All about Microsoft, Office 365, Azure, and Windows Server.
External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by:

 
Live Webinar: Active Directory Security: What Needs Immediate Priority!Live on Tuesday, October 12th at 1 PM ET

Attacks on Active Directory are at an all-time high. Companies that are not taking heed are being punished, both monetarily and with loss of production.

In this webinar, you will learn:

  • How to prioritize vulnerability management
  • What attackers are leveraging to breach organizations
  • Where Active Directory security needs immediate attention
  • Overall strategy to secure your environment and keep it secured

Sponsored by: