In this article, I will be discussing how to configure Windows Deployment Services -WDS on Windows Server 2019. With the current rise in Windows devices in organisations, the number of physical and virtual machines have increased and because of this, windows (OS) deployment takes a longer time to complete. With WDS, the service delivery process can be automated.
Microsoft offers this solution for an organization that doesn’t have money to purchase any third party software or purchase SCCM, the WDS server allows us to deploy images from a central location to any type of computer. WDS previously known as Remote Installation Service (RIS) and had no GUI. But WDS is way far better deployment tool.
WDS is a role in Active Directory. For more on roles and features, see the following article https://techdirectarchive.com/2020/04/27/windows-server-what-are-the-differences-between-roles-and-a-feature/
WDS allows you to deploy the Windows operating system to a PXE-enabled client(s). You can install a Windows operating system on a PXE-capable client without the need for physical media. With this, Administrators life becomes easier as everything Windows OS can now be automated.
The Preboot Execution Environment (PXE) is an industry standard client/server interface that allows networked computers that are not yet loaded with an operating system to be configured and booted remotely by an administrator.
Functions of Windows Deployment Services (WDS)
– Uses existing technology like Windows PE, Windows Image File (.wim) and virtual hard disk (.vhd and .vhdx) image files, and image-based deployment. For some examples on WDS deployment, see the links below.
1: How to setup a VM via PXE boot on a Generation 2 VM – Hyper-V, https://techdirectarchive.com/2020/01/19/how-to-setup-a-vm-via-pxe-boot-on-a-generation-2-vm-hyper-v/
2: How to setup a VM via PXE boot on a Generation 1 VM – Hyper-V, https://techdirectarchive.com/2020/01/19/how-to-setup-a-vm-via-pxe-boot-on-a-generation-1-vm-hyper-v/
– Provide end-to-end deployment solutions for clients and server computers.
– Facilitate the process of deployment.
– Supports deployment of computers without any installed operating system.
– Allows you to install a network-based operating system.
Other Deployment methods
– Autoattended.xml (WinPE) – setup tool (media) placed in a root directory for clients to use.
– Have the setup (bootable) media saved to a file server and have the clients connect (UNC) to the file server.
– SCCM (gives the highest level of automation and this gives a zero touch of the installation).
WDS Hardware Requirements
– RAM: minimum of 4GB
– Processor: 64-bit processor
– HDD: At least 10GB (This depend on the operating system ISO and Software’s Size).
Components, requirements and Prerequisites to Configure WDS Server
Before proceeding to configuring WDS, ensure the following requirements are met.
– Active Directory: Needs to register the the WDS servers in order to make it available to clients.
– A DHCP server in order to assign IP addresses.
– Ensure the required firewall rules are configured.
– Static IPs’ are configured for the server.
– The right Windows Server hostname is used.
WDS configurationWDS interacts closely with DHCP, PXE, DNS and Active Directory. As all of these functions are part of the Windows Server platform, it is cost-effective to use them. DHCP can also be offered by a non-Windows server. See the following links for more details on DHCP.
- Dynamic Host Configuration Protocol (DHCP), see https://techdirectarchive.com/2020/05/10/ip-assignment-dynamic-host-configuration-protocol-dhcp/
- How to install Dynamic Host Configuration Protocol on Windows Server 2019, https://techdirectarchive.com/2020/05/10/ip-assignment-dynamic-host-configuration-protocol-dhcp/
- Configuring DHCP: Post-deployment of Dynamic Host Configuration Protocol, see https://techdirectarchive.com/2020/05/10/configuring-dhcp-post-deployment-of-dynamic-host-configuration-protocol/
Follow the below Steps To Install and Configure WDS Server (Windows Deployment Services) On Windows Server 2018
Step 1. Open Server Manager and
– Click Add Role and Features.
Step 2. On the Before you begin page, click on next
– Choose Roll-based or Feature-based installation and click on Next.
If you have multiple servers, select the right server from the server pool. For me, I have just one server and it is automatically selected below.
– Next select the Windows Deployment Services as shown below.
Note: When WDS role is selected, this will proppt a popup as shown below.
– On the Add Roles and Features Wizard, click on Add Features
– Now that the features are added, click on Next to continue the installation process
Skip the Features windows by clicking on next as this is not a needed at the moment as non of the features
Step 4: On the WDS box, review the information presented, and then proceed with Next.
– On the Role Services page, the Deployment Server and Transport Server roles are checked by default. Click on Next (Leave the default selection of both deployment and transport server as shown below)
On the confirmation page, click on Install as shown below.
This shows WDS successful, click Close.
Now that the WDS installation is successful, you can now launch and configure WDS. Here is one of the ways to launch WDS.
– Click on WDS
– Under the servers, right click and select “Windows Deployment Services Management Console”
To configure WDS, see the following article https://techdirectarchive.com/2020/05/12/configuration-of-windows-deployment-services-wds/
If you are looking for the command-line or PowerShell installation of the WDS server, then use the below command.
– Open the PowerShell and run the command below with Administrative Privilege
ServerManager -install WDS
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.