Microsoft Windows Deployment Services

Posted on |

You have decided to deploy OS images over the network but you want to test it out or you want to create a small deployment lab. Building a standalone deployment server is the way to go. Windows Deployment Service (WDS) and Microsoft Deployment Toolkit (MDT) are an easy way to accomplish that. In this standalone setup the server is not part of a domain and has DNS (Domain Name System) and DHCP (Dynamic Host Configuration Protocol) on the same system as WDS and MDT.

In order to keep up with the demand of deploying workstation images to hundreds and thousands of systems quickly you need to have a deployment mechanism in place. There are plenty of products out there that can deploy images. But let's say you don't have those products. How can you do it? Well MDT and WDS do a great job together, also they are free (as long as you have a Windows Server license for WDS).

  • The Microsoft Deployment Toolkit (MDT) is a free tool for automating Windows and Windows Server operating system deployment, leveraging the Windows Assessment and Deployment Kit (ADK) for Windows 10. Version 8456 was released on January 25th 2019 and is the latest current version.
  • The primary developer audience of the WDS API is for groups that develop custom tools and processes for IT and other computer administration groups. In environments where the standard Windows Deployment Services (WDS) solution cannot be used, the WDS API enables programmatic access to some WDS components.

Windows Server is fully installed on the system without any outstanding issues. A basic understanding of Windows Server administration. The IP address range has already been determined. A user account on the server has been created with read access to the deployment share.

DNS

Installation

  1. Open Server Manager
  2. Click Manage
  3. Click Add Roles and Features
  4. The Add Roles and Features Wizard window will appear
    1. On the Before you begin screen click Next
    2. On the Select installation type window click Role-based or feature-based installation and click Next.
    3. On the Server destination server window select
      1. Select a server from the server pool
      2. Under Server Pool select the server name

Mar 01, 2014  Windows Deployment Services (WDS) Windows Deployment Services is a server role that gives administrators the ability to deploy Windows operating systems remotely. WDS can be used for network-based installations to set up new computers so administrators do not have to directly install each operating system (OS).

On the Select server roles screen select Windows Deployment Services. On the pop-up window click Add Features; Click Next; On the Select features screen click Next; On the WDS screen click Next; On the Select role services screen select both Deployment Server and Transport Server, click Next. Get the most out of Windows Server Windows Server 2019 is the operating system that bridges on-premises environments with Azure, adding additional layers of security while helping you modernize your applications and infrastructure.

  • Click Next
  1. On the Select server roles screen select DNS
    1. On the pop-up window click Add Features
    2. Click Next
  2. On the Select features screen click Next
  3. On the DNS Server screen click Next
  4. On the Confirm installationselections screen clickRestart the detitanation server automatically if required. Click Yes to the pop-up then click Install
  5. Wait for the installation to complete.
  6. Once the installation is complete click the Close

Configuration

  1. Click Start -> Windows Administrative Tools -> DNS.
  2. In the DNS Manager window click on the server name.
  3. In the right pane, right-click Forward Lookup Zones and then click New Zone…
  4. In the New Zone Wizard on the Welcome screen click Next.
  5. On the Zone Type screen select Primary zone and click Next.
  6. On the Zone Name screen enter the name of the Zone and click Next
  7. On the Zone File screen leave the default selections and click Next.
  8. On the Dynamic Update screen select Allow both nonsecure and secure dynamic updates and click Next.
  9. On the Complete the New Zone Wizard screen click Finish.

DHCP

Installation

  1. Open Server Manager
  2. Click Manage
  3. Click Add Roles and Features
  4. The Add Roles and Features Wizard window will appear
    1. On the Before you begin screen click Next
    2. On the Select installation type window click Role-based or feature-based installation and click Next.
    3. On the Server destination server window select
      1. Select a server from the server pool
      2. Under Server Pool select the server name
  • Click Next
  1. On the Select server roles screen select DHCP
    1. On the pop-up window click Add Features
    2. Click Next
  2. On the Select features screen click Next
  3. On the DHCP Server screen click Next
  4. On the Confirm installationselections screen clickRestart the detitanation server automatically if required. Click Yes to the pop-up then click Install
  5. Wait for the installation to complete.
  6. Once the installation is complete click the Close
  1. On the Server Manager window click the Warning icon at the top and then click Complete DHCP Configuration.
  2. The DHCP Post-Install configuration wizard opens up.
    1. On the Description screen click Commit.
    2. On the Summary screen click Close.

Configuration

  1. Click Start -> Windows Administrative Tools -> DHCP.
  2. In DHCP window expand the server in the left pane.
  3. Right-click IPv4 and click New Scope…
  4. The New Scope Wizard window appears.
    1. Click Next.
    2. On the Scope Name screen enter a name and description for the scope and click Next.
    3. On the IP Address Range screen enter the Start IP address and End IP address Verify that the Subnet mask is correct and then click Next.
    4. On the Add Exclusions and Delay screen do not enter any information, click Next.
    5. On the Lease Duration screen change the Days to 1, click Next.
    6. On the Configure DHCP Options screen select Yes and click Next.
    7. On the Router (Default Gateway) screen do not enter an IP address, click Next.
    8. On the Domain Name and DNS Servers screen enter the IP address of the server and click Add, then click Next.
    9. On the WINS Servers screen do not enter any IP address, click Next.
    10. On the Activate Scope screen select Yes and then click Next.
    11. On the Completing the New Scope Wizard screen click Finish.
  5. Reboot the server.

MDT

Installation

  1. Install ADK
    1. Go to Windows ADK website and download the latest Windows ADK for Windows 10.
    2. Run exe
    3. The Windows Assessment and Deployment Kit – Windows 10 window opens.
    4. On the Specify Location screen
      1. select the Download the Windows Assessment and Deployment Kit – Windows 10 for installation on a separate computer radio button.
      2. Browse to the desired download path to save the files.
  • Click Next
  1. On the Windows Kits Privacy screen select No and then click Next.
  2. On the License Agreement screen click Accept.
  3. On the Download is complete screen click Close.
  4. Copy the files to the server if needed.
  5. Open the folder with the downloaded files.
  6. Run adksetup.exe
  7. The Windows Assessment and Deployment Kit – Windows 10 window opens.
  8. On the Specify Location screen browse to the desired install path and click Next.
  9. On the Windows Kits Privacy screen select No and then click Next.
  10. On the License Agreement screen click Accept.
  11. On the Select the features you want to install screen select the following items and then click Install
    1. Deployment Tools
    2. Windows Preinstallation Environment (Windows PE)
  • User State Migration Tool (USMT)
  1. Wait for the installation to complete.
  2. Uncheck Learn more about the Windows Assessment and Deployment Kit and then click Close.
Microsoft deployment toolkit vs windows deployment services
  1. Install MDT
    1. Go to the Microsoft Deployment Toolkit site and download the latest version of MDT.
    2. Run the MDT setup.
    3. On the Welcome screen click Next.
    4. On the End-User License Agreement screen select I accept the terms in the License Agreement and click Next.
    5. On the Custom Setup screen select the desired installation location and click Next
    6. On the Customer Experience Improvement Program screen select I don’t want to join the program at this time and click Next.
    7. On the Ready to install screen click Install.
    8. When the installation completes click Finish.

Configuration

Adding Deployment Share

  1. Click Start-> Microsoft Deployment Toolkit -> Deployment Workbench.
  2. The Deployment Workbench window opens.
  3. An existing deployment share can be added or a new one can be created.
    1. Opening an existing deployment share.
      1. Right-click Deployment Shares and click Open Deployment Share.
      2. The Open Deployment Share Wizard appears.
  • On the Path screen browse to the deployment share and click Next.
  1. On the Summary screen click Next.
  2. When the operation completes click Finish on the Confirmation screen.
  1. Creating a new deployment share.
    1. Right-click DeploymentShares and click NewDeploymentShare.
    2. The New Deployment Share Wizard appears.
  • On the Path screen browse to the desired location for the new deployment share and then click Next.
  1. On the Share screen type in the desired name of the share or leave the default and then click Next.
  2. On the DescriptiveName screen type in a description for the share and then click Next.
  3. On the Options screen select the options you would like to have the deployment perform and then click Next. Note: these can be changed later.
  • On the Summary screen review the selections and then click Next.
  • Once complete click Finish on the Confirmation screen.

Update username and password for Deployment Share

A username and password are required for the boot image from MDT to access the MDT share.

  1. Create Deployment service account
    1. Click Start -> WindowsAdministrativeTools -> ComputerManagement.
    2. Expand SystemTools -> LocalUsersandGroups.
    3. Right-click Users and click NewUser…
    4. On the New User window enter the information for the MDT Deployment service account and then click Create.
    5. Close the ComputerManagement window
  2. Set Share and Security Permissions
    1. Open File Explorer.
    2. Navigate to the deployment share.
    3. Right-click on the deployment share and click Properties.
    4. Set the following permissions for the Deployment service account on the Deployment share.
      1. Share permissions – Read
      2. Security permissions – Read & Execute, List Folder Contents, Read
    5. Add Deployment service account to the Bootstrap.ini file.
      1. Open the MDT Deployment Workbench.
      2. Right-click the deployment share and then click Properties.
      3. Click the Rules tab and then click Editini in the lower right of the Properties windows.
      4. The Bootstrap.ini file will open in Notepad.
      5. Under the [Default] section of the Bootstrap.ini file enter the following information.
        1. UserID=Deployment service account name
        2. UserDomain=Name of the deployment server
  • UserPassword=Password for the deployment service account
  1. Save and close the Bootstrap.ini file.
  2. Close the deployment share Properties window.
  3. Right-click on the Deployment share and click Update Deployment Share.
  4. On Options screen of the Update Deployment Share Wizard select Completely regenerate the boot images and then click Next.
  5. Click Next on the Summary
  6. Click Finish on the Confirmation

Windows Deployment Services (WDS)

WDS facilitates the Preboot Execution Environment (PXE) portion of the network deployment of the Windows 10 image to the laptops. PXE facilitates the network booting of a computer to be able to pull down a bootable image file.

Installation

  1. Open Server Manager
  2. Click Manage
  3. Click Add Roles and Features
  4. The Add Roles and Features Wizard window will appear
    1. On the Before you begin screen click Next
    2. On the Select installation type window click Role-based or feature-based installation and click Next.
    3. On the Server destination server window select
      1. Select a server from the server pool
      2. Under Server Pool select the server name
  • Click Next
  1. On the Select server roles screen select Windows Deployment Services
    1. On the pop-up window click Add Features
    2. Click Next
  2. On the Select features screen click Next
  3. On the WDS screen click Next
  4. On the Select role services screen select both Deployment Server and Transport Server, click Next
  5. On the Confirm installationselections screen clickRestart the detitanation server automatically if required. Click Yes to the pop-up then click Install
  6. Wait for the installation to complete.
  7. Once the installation is complete click the Close

Configuration

Microsoft Windows Deployment Services
  1. Click Start -> Windows Administrative Tools -> Windows Deployment Services.
  2. The Windows Deployment Services window opens.
  3. In the left pane expand Servers
  4. Right-click on the server and click Configure Server
  5. The Windows Deployment Service Configuration Wizard
    1. On the Before You Begin screen click Next
    2. On the Install Options screen select Standalone server, click Next
    3. On the Remote Installation Folder Location screen select the location path and then click Next.
    4. On the Proxy DHCP Server screen select both options and then click Next
    5. On the PXE Server Initial Settings screen select Respond to all client computers (known and unknown), click Next.
    6. On the Task Progress screen, click Finish when it completes.
  6. If the WDS server did not start, right-click the server and select All Tasks -> Start.
  7. Right-click on the server and click Properties.
  8. On the server properties page go to the Boot tab.
    1. Under the PXE Boot Policy section select Continue the PXE boot unless the user presses the ESC key for both Known and Unknown clients.
    2. Click OK
  9. Under the server right-click Boot Images and click Add Boot Image…
  10. The Add Image Wizard window appears.
    1. On the ImageFile screen browse to the file location of the MDT boot image (it is in the boot folder in the deployment share) and then click Next.
    2. On the ImageMetadata screen type in the name and description for the image and then click Next.
    3. On the Summary screen review the information and then click Next.
    4. On the TaskProgress screen click Finish when complete.

Note: If you receive and Access Denied error make sure that the share permissions on the RemoteInstall have the user account that is being used listed and have at least Read and Change permissions.

Finished

The server is now configured to answer PXE requests and deploy an image that is configured in MDT. An imaged must be developed in MDT before it can be deployed.

Windows Deployment Services is a server technology from Microsoft for network-based installation of Windows operating systems. It is the successor to Remote Installation Services.[1] WDS is intended to be used for remotely deploying Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2012 and Windows Server 2016, but also supports other operating systems because unlike its predecessor RIS, which was a method of automating the installation process, WDS uses disk imaging, in particular the Windows Imaging Format (WIM). WDS is included as a Server Role in all 32-bit and 64-bit versions of Windows Server 2008, and is included as an optionally installable component with Windows Server 2003 Service Pack 2.

  • 1Automated image capture and apply

Automated image capture and apply[edit]

WDS functions in conjunction with the Preboot Execution Environment (PXE) to load a miniature edition of Windows known as Windows PE for installation and maintenance tasks. WDS functions as both a storage repository for the PXE network boot images as well as a repository for the actual operating system images to be installed on the target computer.

When multiple boot images are available, PXE booting via WDS will present the end-user with a boot menu to select the image to load.

Windows PE automation using WAIK[edit]

To simplify the tasks of capturing and applying images, two special scripted Windows PE boot images can be created which automate these tasks. These scripted Windows PE boot images are created using the Windows Automated Installation Kit, in combination with Windows 7 installation media containing the source WIM images, and then added to the WDS server's boot image repository. The Windows PE boot images may be either 32- or 64-bit, but 32-bit tends to be more universally compatible across all potential hardware types.

Microsoft Windows Deployment Services Download

A difficulty of Windows PE booting is that it needs to include network drivers and disk controller drivers intended to work with the target hardware to be imaged. The process of adding drivers to the Windows PE boot image can be automated using the WDS server console:

  1. Select the source WIM image, which may be either a new one created from original Windows 7 installation DVDs (32- or 64-bit), or a previously configured WIM.
  2. Select the drivers to install into the WIM
  3. WDS mounts the WIM to a virtual path, adds drivers to the virtual path, and generates a new WIM
  4. The updated WIM image is added to the boot image section of the WDS repository

This process can be repeated at a later time when a new system type needs to be captured but the current Windows PE Capture boot image does not include network drivers for it. The boot image is updated with the additional drivers using the WDS interface and automatically re-added to the WDS boot image collection to replace the original.

Microsoft Deployment Toolkit Vs Windows Deployment Services

For specialty one-off systems this WIM driver update process is not necessary if the hard drive of the target system to be captured is removed from the source system after sysprepping, and is either installed in a computer with supported network drivers, or attached to the supported system using an external 'USB to hard drive' adapter.

Automated apply process[edit]

Applying a captured image involves running a second Windows PE 'Apply' boot image on the target system to receive the image. This boot image also needs the appropriate network and disk controller drivers as with the Windows PE Capture boot image.

  1. The system is booted using PXE network booting and the Windows PE Apply image is loaded.
  2. The operator logs on to the domain, and selects the boot image to apply.
  3. A disk partitioning screen appears and the location for the target image is selected. If the target storage is unformatted, a default partition set is created. For Vista and Windows 7, a small 100 megabyte boot partition is created for storing bootloader data separate from the rest of the system partition. This boot partition is normally hidden from the Windows Vista/7 user.
  4. The image data is applied to the selected partition, and the system reboots, either running the Sysprep manual mini-setup process or following the script created during the initial Sysprepping.

The WDS image creator may optionally select a separate WAIK / Sysprep installation script to be applied to the image during the first boot. This alternate script is selected within WDS by viewing the properties of each uploaded system image.

Manual image capture and deploy[edit]

It is technically possible to create scripts that manually perform the imaging, capture, and apply processes, using command line tools provided by Microsoft. However, the methods for doing this are complex and difficult.

In general, the tools involved are:

  • dism - Deployment Image Service and Management Tool, used to add drivers to Windows PE boot images.
  • imagex - used to capture and apply images. Creates either a single WIM structure, or can deduplicate data using a second shared resource WIM. Does not require a Windows Deployment Server to capture or apply images, and can work solely with a logged-on network share or mapped drive letter.
  • wdsutil - used to manage the WDS server without the graphical user interface, and to add captured images to the repository.

Using imagex to manually create a WIM does not require the source operating system to be sysprepped or for the source partition to contain a Windows operating system. Any type of Windows-accessible file system can be imaged, including MSDOS, but the source system either needs to be able to run Windows PE or the source system's hard drive is moved into a newer system that supports Windows PE.

Microsoft generally requires Windows 2000, XP, Vista, and Windows 7 to be sysprepped before imaging, due to certain security-related disk data that Microsoft requires to be unique across duplicated system images. Sysprep randomizes this data when the image is applied to a new system.

Microsoft Windows Deployment Services 2016

Imagex does not have any disk formatting and partitioning capabilities. Separate Windows command line tools such as diskpart are needed to define partitions on the target system for imagex to use.

References[edit]

  1. ^'Windows Deployment Services'. Retrieved 2015-08-28.

External links[edit]

4101 Error Microsoft-windows-deployment-services-diagnostics

See also[edit]

Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Deployment_Services&oldid=908980793'