Windows Deployment Services (WDS) Installation and Configuration

Institutions need to manage their technology infrastructure quickly and efficiently. In this context, Windows Deployment Services (WDS)is a vital tool for automating the installation of operating systems on multiple computers over a network. In this article, Windows Deployment ServicesWe will take you through the installation process step by step.

  • The article content progresses according to the installation order for Windows Deployment Services, all necessary pre-installations are available.

What is Windows Deployment Services (WDS)?

Windows Deployment Services (WDS), Microsoft is a network-based deployment solution offered by This service makes it easy to deploy and install operating systems on target computers from a central server. WDS, allows for the rapid installation of new computers or reconfiguration of existing computers, especially in large organizations.

PXE (Preboot Execution Environment) It allows computers to initiate operating system loads over the network using the boot protocol.

WDS, also has a flexible structure that allows customization and management of operating system images. System administrators can create various images according to different hardware and user needs and distribute these images according to groups.

Key Requirements for Windows Deployment Services (WDS)

Windows Deployment Services (WDS) Before performing the installation, the prerequisites necessary for successful installation and operation must be provided.

  • OS: WDSis supported on Windows Server 2008 and later versions.
  • Active Directory: WDS'S Active Directory Integration with is required. The WDS server must be a member of the domain.
  • DHCP Server: WDS, so that PXE clients can be started over the network DHCP requires a server. DHCP ve WDS can run on the same server or on different servers.
  • DNS Server: So that devices on the network can find each other by name DNS configuration is required and DNS The service must be healthy.
  • Network Configuration: Sufficient network infrastructure and bandwidth, especially if multiple clients are to be served simultaneously. WDS is an important requirement for.

Windows Deployment Services (WDS) Role Setup

Here WDS We talked about its definition and requirements, now let's look at our environment. Windows Deployment Services (WDS) We can continue by installing the role.

Windows Deployment Services Role installation is a standard process and there is no difference during the Role installation process.

We follow the steps of Server Manager – Add roles and features.

  • before you begin Next We can continue with the button.
  • Select installation type on your page Role-based or feature-based installation After selecting the option Next We can continue with.

Server Manager If there is no other server we have added on it,Select destination serverBy marking our own server in the " section Next It is enough to continue with .

SelectServer My roles name is "Windows Deployment Services” option, this gives us the basic Windows Deployment Services role will perform the installation.

WDS Role for installation Role Services When we come to the section, we are greeted by two options;

  • Deployment Server:

Deployment Server is known as the main component of WDS and contains most of the operating system deployment functions. This component provides:

  • PXE (Pre-Boot Execution Environment) Boot: Deployment Server, operating systems of computers launched over the network PXE boot This makes it possible to install an operating system on computers without any local media (for example, without a CD, DVD, or USB drive).
  • Multicast Transmission: Supports multicast broadcasts to send operating systems to multiple computers simultaneously.
  • Image Storage and Management: Deployment Serverstores and manages operating system images. These images can be customized for various computer configurations and deployed as needed.
  • Transport Server:

Transport Server, a lighter WDS component and its main focus is to perform data movement operations over the network. This component includes the following features:

  • Multicast Data Transfers: Transport Servermanages data transfers over the network via multicast streams. This is an ideal solution for situations where large files or images need to be distributed to multiple destinations simultaneously.
  • Stand alone Mode: Transport Server, Deployment ServerIt can work independently of . This WDSUseful for simpler deployment scenarios that don't need the full feature set of .

Generally, it is preferable to enable both for full deployment functionality. In this article, we will perform the installation by activating both options.

Restart the destination server automatically if required After selecting the option, we need to continue with the Next button.

Our installation process is complete, now Server Manager from the screen Windows Deployment Services we can open our console. WDS On console Servers located under WDS Right click on our server and select "Configure Server" We need to come to the step.

Windows Deployment Services Configuration Wizard The window opens and warns us about the necessary requirements. We can continue by clicking Next in this step.

In this step, we are presented with two options;

Integrated with Active Directory: Active Directory The term “Integrated with” means a server or service, Microsoft Active Directory This integration simplifies user management, increases security and ensures consistency in access to various resources.

Standalone Server: These servers can perform local data processing or resource sharing tasks that do not require direct integration with other devices or services on the network. Standalone servers manage access controls through local user accounts, without central management or authentication services.

Since our environment is an AD structure Integrated with Active Directory We need to continue with the option.

Remote Installation Folder Location In the section, it asks us to specify a folder path for the items to be deployed.


In this section, it is determined which of the devices connected by receiving an IP address via PXE will receive the operating system image. “Respond to all client computers” Checking the option means that the image will be deployed to all known and unknown devices. I prefer this option.

  • Do not respond to any client computers: Do not respond to any client computers.
  • Respond only to known client computers: Only respond to registered and recognized clients.
  • Respond to all client computers: Respond to all known and unknown clients.

A preview window appears and the configuration process begins with the Next button.

With this process, we complete the Windows Deployment Services installation and initial configuration processes.

What is Windows Assessment And Deployment Kit?

Windows Assessment and Deployment Kit (Windows ADK), Microsoft by Windows It is a free tool developed to support operating system installations, upgrades, and configurations. It is used by IT professionals to deploy Windows operating systems to new computers, evaluate system performance, and create customized Windows installations.

1. Windows PE (Windows Preinstallation Environment)

Windows PEis a lightweight system used to install new operating systems on computers, recover existing operating systems, or perform maintenance operations. This environment allows the computer to be started over the network or from external media such as a USB drive.

2. deployment tools

Windows ADK The deployment tools in it are used to create, edit, and deploy operating system images. These tools include ImageX, DISM (Deployment Image Servicing and Management), and Windows System Image Manager (SIM).

3. User State Migration Tool (USMT)

USMTis a tool used to transfer user data and settings from an old computer to a new computer. This helps preserve the user experience during large-scale computer upgrade projects.

4. Performance Toolkit

This toolkit, Windows used to evaluate and analyze the performance of operating systems.

5. Application Compatibility Toolkit

We can say that it is a set of tools used to test and evaluate application compatibility. This toolkit is a new Windows It analyzes the compatibility of existing applications during the transition to the latest version and identifies potential compatibility issues, facilitating the preparation of a detailed report.

Windows ADK, especially for large-scale businesses and organizations, Windows It provides a comprehensive solution for efficient deployment and management of operating systems. Current versions of ADK, Windows It is regularly updated and improved to match operating system versions.

How to Install Windows Assessment and Deployment Kit?

Windows Assessment and Deployment Kit Before starting the installation, you can download it from the link below.

https://support.microsoft.com/tr-tr/help/4027209/oems-adk-download-for-windows-10

Windows Assessment and Deployment Kit After the download is complete, we open the application we downloaded and Specify Location We select the Path section where the installation will be made.

Windows Kits Privacy We mark the section as “Yes” and Next Windows Assessment and Deployment Kit (ADK) We continue with the installation.


Some important components in the Features window can be described as follows: We have explained the components above, but it would be useful to make an additional explanation for the installation step.

Windows Preinstallation Environment (Windows PE): Windows It is a lightweight operating environment specifically designed for the installation and maintenance of operating systems. This environment allows computers to be started over a network or using external media, so that installation and recovery operations can be easily performed.

User State Migration Tool (USMT): A command-line tool designed to transfer user data from an old Windows installation to a new installation. This tool allows you to choose which data to move or not move, so that user profiles can be migrated without any problems.

Volume Activation Management Tool (VAMT): It is a tool that allows you to manage the activations of Windows operating systems and Office products from a central point. VAMT provides ease and management in licensing and allows you to control multiple activations from a single place.

Windows Performance Toolkit (WPT): An advanced toolkit used to monitor and analyze system performance. With features such as event monitoring and system logging, IT professionals can track system events in detail and identify and resolve performance issues.

Among these tools, especially for installation, “deployment tools” and ”User State Migration Tool (USMT)” components. After making our selection, we start the installation process by clicking the 'Install' button.

install with button Windows Assessment and Deployment Our installation process begins.

Thus, Windows Assessment and Deployment Kit (ADK) We have completed the What is it? and How to install it processes.

What is Microsoft Deployment Toolkit (MDT)

Microsoft Deployment Toolkit (MDT), organizations Windows operating systems and Microsoft Office It is an advanced tool that enables users to deploy their applications efficiently over the network. MDT supports three different deployment methods to suit users' needs.

Zero Touch Installation (ZTI)

ZTIis a fully automated deployment process that requires no user intervention. This method is ideal for large organizations because it saves time and resources by automating processes. To use ZTI effectively, your business System Center Configuration Manager (SCCM) or Microsoft Endpoint Manager (MEM) It must be equipped with a powerful configuration management system such as.

Zero Touch Installation (ZTI) Prerequisites

Components required for ZTI:

  • Microsoft System Center Configuration Manager
  • Microsoft SQL Server
  • Windows PowerShell

User-Driven Installation (UDI)

UDIrequires users to take an active role throughout the installation process. This method allows users to customize their machine name, language settings, and other preferences. UDI, offers a customized installation experience based on users' preferences. For this distribution type, SCCM or MEMIt is required to have .

Lite Touch Installation (LTI)

LTI, works with minimal user interaction and is suitable for small to medium-sized businesses. This method provides fast and efficient OS deployment with minimal infrastructure requirements. Users can use a USB flash drive, network share, or PXE You can easily install an operating system via . LTI, attracts attention with its flexibility and low-cost structure.

MDT, can work integrated with other Microsoft management tools. In particular, SCCM Integration with provides a powerful solution to automate deployment processes and centralize management in large-scale environments. In addition, Windows Assessment and Deployment Kit (ADK) Advanced performance tests and system preparations can be performed using .

How to Install Microsoft Deployment Toolkit (MDT)?

MDT After providing the necessary definitions for Microsoft Deployment Toolkit For installation, firstly follow the link below Microsoft Deployment Toolkit you can perform the download process.

Microsoft Deployment Toolkit It is a small application file so there are no additional options for installation, the application you downloaded Next You can install a standard application installation with the button.

DHCP Server Configuration for Windows Deployment Services

Windows Deployment Services (WDS) When talking about the requirements for DHCP Server We talked about the need, now Windows DHCP Server üzerinde WDS We will provide the necessary definitions for .

Server Manager over DHCP Server We open the console and there is Scope We will add additional rules on it.

  • In the Scope Options section, we activate the “066 – Boot Server Host Name” rule.
  • In the Data Entry section, we enter the IP address of our Windows Deployment Services (WDS) server.
  • We activate the O67 – Bootfile Name value.
  • We enter our value on CMD for Pxe boot as String Value.

Conclusion 060 We need to make changes to the rule, since we cannot do this via the console. DCM we need to do it through.

dhcp
server DHCP Sunucunuzdaki IP Adresini Giriyoruz
add optiondef 60 PXEClient String 0 comment=PXE support
set optionvalue 60 STRING PXEClient
exit

With this process DHCP Servers üzerinde WDS We have completed our configuration.

Windows PE add-on for the ADK Installation

You can download Windows PE Add-On for the ADK using the link below.

https://download.microsoft.com/download/3/c/2/3c2b23b2-96a0-452c-b9fd-6df72266e335/adkwinpeaddons/adkwinpesetup.exe

Since the Windows PE Add-On for the ADK installation has a standard installation process, you can perform the installation with Next – Next.

Image Deployment Process with Windows Deployment Services (WDS)

Deployment Workbench's role is also of great importance. Deployment Workbench, Microsoft Deployment Toolkit (MDT) It is a tool used to manage image creation, editing and deployment processes. This user-friendly interface makes it easy to integrate operating system images, drivers, applications and updates, and customize configuration settings. Deployment Workbench With , you can distribute pre-made images to various computers over the network and control this process from a central point.

  • WDS on the server we installed Deployment Workbench We open the console.
  • On the left menu Deployment Shares via the object New Deployment Share We can start our transactions with.

New Deployment Share Wizard First episode on Path It comes as, Deployment Share We need to specify the drive and folder path that we will use for .

The next step is the Share section, here we need to enter the folder name to be shared.

Options When we reach the tab, the system asks us to tick some options and move the process forward. Among these options, “Ask if a computer backup should be performed” and ”Ask if an image should be capturedWe mark the " options.

  • Ask if a computer backup should be performed: If a new (zero) installation is not being done, you will be asked whether a backup should be made for the existing system.
  • Ask for a product key: It is determined whether users will enter the product keys required for the installation of Windows or other applications.
  • Ask to set the local Administrator Password: After installation, the system will request that an account be defined as a local administrator and the relevant settings be configured.
  • Ask if an image should be captured: After the preparations are completed, the issue of whether the system should be re-imaged after the installation is evaluated.
  • Ask if Bitlocker should be enabled: After installation, you will be asked whether to enable Bitlocker feature on the system.

These options are used to make the installation process more interactive and allow users to make customizations during the installation.

With the Next button, we come to the Finish step and complete our first step for Deployment.

Windows ISO Deployment Step with Deployment Workbench

Deployment Workbench We have completed our first step with Windows ISO deployment We need to do this. I will perform the ISO Deployment process using Windows 10.

First of all, we need to mount the Windows 10 ISO file on our server. You can mount the relevant ISO file.

Later ESD We need to copy the file, for this process we first need to DCMWe need to run as administrator and run the commands below in order.

With this process, we will enter a folder that we have specified. WIM we can create the file.

cd C:\Users\Kullanıcı Adınız\Desktop\ESD
dism /Get-WimInfo /WimFile:D:\Sources\install.esd
dism /export-image /SourceImageFile:install.esd /SourceIndex:4 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity

Now that we have created our WIM file, we can continue with the Deployment process.

Deployment Workbench – Deployment Shares – MDT Deployment Share under Operating System Import Operating System we say.


"Full set of source files” option, all files contained in the Windows ISO or DVD Microsoft Deployment Toolkit (MDT) This contains a complete set of Windows installation files and is often preferred when a new operating system installation or an existing installation needs to be updated.

"custom image file” option is pre-created and WIM Used if you have a customized master (reference) image saved in the .xml format. This method is used to create images that contain customized settings, applications or drivers. MDTIdeal for inclusion in .

WE WIM since we made it into a file, custom image file We will continue with the option.

Image In the section we have created WIM We need to display the file.

  • Destination in the department Deployment We need to create a name for .

After these operations, the deployment process begins.

With this process Windows ISO Deployment We have completed the process. Now, Task Sequence we need to create.

Creating a Task Sequence using Deployment Workbench on Windows Deployment Services

For this process, we need to use the Deployment Workbench console.

Deployment Workbench – Deployment Shares – MDT Deployment Share – Task Sequence – New Task Sequence

Task sequence ID ve Task Sequence Name We fill in the sections as we wish.


Our next configuration screen “Select Template” is named. In this window, you can choose from various quest lines:Standard Client Task SequenceWe select the 'Next' option and continue with the 'Next' button.

The templates presented in this window and their intended uses are as follows:

  1. Sysprep and Capture: If you want to take a one-to-one image from an existing installed client and deploy it to other clients by performing a sysprep operation, you can use this template. This template is designed to reset the system to factory defaults and prepare it for deployment.
  2. Standard Client Task Sequence: This template can be used to install an operating system from scratch. It can also be used in scenarios where you are upgrading existing systems.
  3. Custom Task Sequence: This is a blank template that can be fully customized with personalized settings. It is an ideal option for creating custom task sequences.
  4. Standard Server Task Sequence: This template is used to install and deploy server operating systems. Suitable for server-based applications and configurations, this template allows IT professionals to manage server environments.
  • Select OS When we come to the section Deployment Tagged IMAGE files are displayed, we only have one for now Deployment Since we did this, only our W10 deployment file is visible.

"Specify Product Key" page, you can enter your license information for the operating system. Since I do not have a ready Windows 10 license, I cannot make any changes in this step.NextI proceed with the ' button.

The product key options and their uses that appear on this page can be listed as follows:

  1. Do not specify a product key this time: If you are installing a system with a KMS (Key Management Service) product key under Volume License, you should select this option. KMS is a method that facilitates the licensing of multiple devices over a network.
  2. Specify a Multiple Activation Key (MAK) for activating this operating system: If you are a Volume License holder but the key you will use is a MAK product key, you must select this option and enter your product key. The entered MAK key will be used on each computer where the installation is made and will provide activation.
  3. Specify the product key for this operating system: If you have a product key for a retail or boxed product and you will be installing a single operating system with that key, you should use this option.

In the OS Settings section, Full Name, Organization and you can make adjustments to the Internet Explorer Home Page sections.

The next step is “AdminPassword” section. At this stage, we need to determine the local administrator password of the system we are installing. If “Do not Specify an administrator password at this timeIf you select the ” option, the system will ask you to enter a local administrator password during installation. However, instead of leaving the password during the installation sequence, I prefer to set a secure password at this step.

  • Summary You can preview all the operations we have done in the section. After performing our final checks, you can start the configuration process.

Now is Windows Deployment Services a Deployment Workbench using Install Images We can configure the section.

We can follow the Windows Deployment Services – Install Images – Add Image step. Here we show the WIM file we created.


As a second step, we go to the “Boot Images” section in Windows Deployment Services (WDS), right-click and select the “Add Boot Image” option. This process opens the “Add Image Wizard” screen. Here, we need to specify the location of the boot image that will be used to start the system. When we previously updated Deployment Share, Microsoft Deployment Toolkit (MDT) automatically created the boot images. At this stage, we need to select the boot image file created by MDT.

The feature of the boot image file in MDT is that it contains all the necessary information (share name, IP address, Deployment Share name, access information, etc.) to ensure that the client successfully reaches MDT when it boots. The boot image is, by default, DeploymentShare\Boot\BootDosyasınınAdı.wim path. Under Deployment Share, separate boot images are available for both x86 and x64 architectures. Each of these files can be selected and used as appropriate, depending on the needs of the installation.

  • We can start the import process with the Next button.

Configuring Windows Deployment Services Boot

Windows Deployment Services via console via server Properties We are coming to your step.

On the Properties page, “Boat" We open the tab. Here, we make two important settings for the PXE boot process. "Known Client” for setting “Always continue the PXE boot" We select the option; this way, the system will direct previously known users directly to the installation. "Unknown Clients” for “Require the user to press the F12 key to continue the PXE bootThis setting requires unrecognized users to press F12 to initiate the PXE boot process, thus providing a checkpoint before authenticating users.

"Default boot imageIn the ” section, both “x64 architecture” and “ bothx64 (UEFI) architectureFor "LiteTouchPE_x64” image. This is especially suitable for devices that support 64-bit architecture, and these images contain various tools and drivers used in the installation and deployment process. With these settings, WDS Operating system installations can be managed more flexibly and in a controlled manner via your server.


After completing all the necessary configuration processes, you can now install Windows 10 by starting it over the network (network boot). During the installation process, the system will request your username and password. Depending on your institution's policies and environment structure, you can also use your domain user information if you wish.

Open the system you will be installing on and if your configurations are done correctly, it will automatically detect the image file you prepared over the network and start the installation process. This process will continue without requiring user intervention or with minimal interaction, depending on the settings and configurations you have selected.

At this stage, you can select your keyboard language and perform the relevant IP configurations if a domain structure is to be created. These configurations are important for the installation to be smooth and in accordance with the features you want. The keyboard layout should be compatible with the language and writing style you will use, and the IP configuration should be set to suit your network and domain configuration.

I, "Run the Deployment Wizard to install a new Operating System” I continue the installation process by selecting the option. This option starts the steps required for the installation of a new operating system and offers the user the opportunity to configure the operating system selection, disk partitioning, user accounts and other important installation settings

  • In the User Credentials section, we need to perform the LOGIN operation with the user we created in Active Directory.

In the next steps, we need to select the IMAGE files we are deploying.

When performing a clean installation, to avoid carrying over existing user data and settings,Do not move user data and settingsI prefer the ” option. This option ensures that old user data and settings are not overwritten when installing a new operating system, thus performing a clean installation.

  • We are performing our system language, time and date configurations.
  • In the last step, we can start the installation with the BEGIN button.

Result:

We have successfully completed our transactions. In this process, Windows Deployment Services (WDS) ve Microsoft Deployment Toolkit (MDT) We performed a Windows 10 operating system installation over the network using . During the installation, we performed a clean installation by choosing the option not to migrate user data and settings. This approach allowed us to start fresh on the system and eliminated any issues that could arise from potential legacy system remnants.

Comment