Deploy Windows 10 using PXE and Configuration Manager (Windows 10) – Windows Deployment

Deploy Windows 10 using PXE and Configuration Manager

In this article

Applies to:

  • Windows 10

In this article, you’ll learn how to deploy Windows 10 using Microsoft Configuration Manager deployment packages and task sequences. This article will walk you through the process of deploying the Windows 10 Enterprise image to a Unified Extensible Firmware Interface (UEFI) computer named PC0001. An existing Configuration Manager infrastructure that is integrated with MDT is used for the procedures in this article.

This article assumes that you’ve completed the following prerequisite procedures:

For the purposes of this guide, we’ll use a minimum of two server computers (DC01 and CM01) and one client computer (PC0001).

  • DC01 is a domain controller and DNS server for the contoso.com domain. DHCP services are also available and optionally installed on DC01 or another server. Note: DHCP services are required for the client (PC0001) to connect to the Windows Deployment Service (WDS).

  • CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.

    • CM01 is also running WDS that will be required to start PC0001 via PXE.

      Note

      Ensure that only CM01 is running WDS.

  • PC0001 is a client computer that is blank, or has an operating system that will be erased and replaced with Windows 10. The device must be configured to boot from the network.

Note

If desired, PC0001 can be a VM hosted on the server HV01, which is a Hyper-V host computer that we used previously to build a Windows 10 reference image. However, if PC0001 is a VM then you must ensure it has sufficient resources available to run the Configuration Manager OSD task sequence. 2GB of RAM or more is recommended.

All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.

All server and client computers referenced in this guide are on the same subnet. This connection isn’t required. But each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.

Note

No WDS console configuration is required for PXE to work. Everything is done with the Configuration Manager console.

Procedures

  1. Start the PC0001 computer. At the Pre-Boot Execution Environment (PXE) boot menu, press Enter to allow it to PXE boot.

  2. On the Welcome to the Task Sequence Wizard page, enter in the password pass@word1 and select Next.

  3. On the Select a task sequence to run page, select Windows 10 Enterprise x64 RTM and select Next.

  4. On the Edit Task Sequence Variables page, double-click the OSDComputerName variable, and in the Value field, enter PC0001 and select OK. Then select Next.

  5. The operating system deployment will take several minutes to complete.

  6. You can monitor the deployment on CM01 using the MDT Deployment Workbench. When you see the PC0001 entry, double-click PC0001, and then select DaRT Remote Control and review the Remote Control option. The task sequence will run and do the following steps:

    • Install the Windows 10 operating system.
    • Install the Configuration Manager client and the client hotfix.
    • Join the computer to the domain.
    • Install the application added to the task sequence.

    Note

    You also can use the built-in reports to get information about ongoing deployments. For example, a task sequence report gives you a quick overview of the task sequence progress.

    MDT monitoring.

    Monitoring the deployment with MDT.

  7. When the deployment is finished you’ll have a domain-joined Windows 10 computer with the Adobe Reader application installed as well as the applications that were included in the reference image, such as Office 365 Pro Plus.

Examples are provided below of various stages of deployment:

pc0001a.
pc0001b.
pc0001c.
pc0001d.
pc0001e.
pc0001f.
pc0001g.
pc0001h.
pc0001i.
pc0001j.
pc0001k.
pc0001l.
pc0001m.
pc0001n.

Next, see Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager.

Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
Create a custom Windows PE boot image with Configuration Manager
Add a Windows 10 operating system image using Configuration Manager
Create an application to deploy with Windows 10 using Configuration Manager
Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
Create a task sequence with Configuration Manager and MDT
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager