In this part of the course, we will take role configuration one step further.
In the first chapter, we’ll set up a deployment service, so let’s prepare the infrastructure for this particular role. With this deployment service, you’ll take control of your IT equipment in a whole new way by deploying a Windows 10 Pro image.
Discover the Windows Deployment Service
Windows Deployment Services (WDS) bring together the features you’ll need for booting a client computer via the network and sending it a customized operating system. After a brief history lesson, you’ll see how to configure the deployment service.
A Bit of History
It was previously called RIS (Remote Installation Service) and allowed the BOOTP protocol (including DHCP) to be used to provide a boot image via the network. In addition, clients needed PXE options (Preboot eXecution Environment) to use the BOOTP protocol. Since Service Pack 2 from Windows 2003, WDS replaced the RIS and is now in charge of Vista, 2003, 2008, and Windows XP.
Configure the WDS Role
Now that you have a little bit of context, let’s see how to use the service. First, add the Window Deployment Services (WDS) role (you know how to do that by now!) and go to the management console:
You can set up the server part relatively easily using the wizard! All of the servers that have this role are listed under Servers. Here, it’s just the first WDS server in Chicago (SRVWDSCHI01):
Configure your server by right-clicking on its name and selecting Configure:
The wizard will guide you through the process, telling you the prerequisites for achieving a functional service. Follow this advice closely to get a deployment service that works perfectly.
Here are the prerequisites:
The server must be a member of an AD DS domain or a domain controller (this is not recommended – stick with 1 server = 1 role). It is possible to configure WDS without AD in the architecture. In this case, you’ll need to tick the Standalone Server box.
You must have an active DHCP server on the network.
You must have an active DNS server on the network.
NTFS partition (required) is available to store images.
Once you’ve met these requirements, you can confirm this stage. You’ll need to choose between an AD-integrated installation (practical for managing equipment from A to Z) or a standalone server.
Once you’ve chosen your architecture, state your image location (I’ve chosen E:\RemoteInstall so that I don’t pollute my partition system). Finally, you’ll get to the important bit:
You’ll have to select your response mode. For example, it might be better to respond only to known computers, giving you greater control over PC installation. You could also select the approval option: you let WDS respond to all clients, but you have to approve them before continuing. And that’s the first stage of configuring this service!
Now that your role is configured, you need to add the install and boot images.
The install image could be an image from existing media.
The boot image enables your server to boot a client computer after responding to the BOOTP requests.
Right-clicking on Boot Images will add the boot images while verifying the integrity. It can take some time, depending on the available server resources. Finally, the wizard will check that the boot image is valid.
You’ll get the following result:
You’ll have noticed that various options have now been added to your deployment services:
The advantage here is that you can add drivers to your images, manage different image groups, and optimize your network bandwidth utilization using multicast.
As you can see from the options available for a boot image, you can also create capture and discover images.
What are these types of images used for?
Imagine you’ve just started working as a systems and network administrator or an IT technician at Gift Ltd. Your managers tell you they plan to increase the workforce significantly. You’ve been conscientious and have lots of client computers. You also run checks and tests for your current equipment. Why not reuse one of these images to prepare the hundreds of computers you’ll need to get ready for new employees?
This is what a capture image is for. You’ll be able to boot using your image and capture the system, drivers, and configuration for an existing computer to then rebroadcast this image via WDS.
The discover image lets you manage clients who cannot fully use PXE. You can create a CD/DVD/USB image to boot their non-PXE computers and “hook” them to your WDS!
Boot a Client in WDS Mode
Now that you have DHCP, DNS, potentially an AD, and WDS configured - and your DHCP has the BOOTP options activated (option dhcp 60 PXEClient), you can boot a client in WDS mode. To do this, select the network interface in your BIOS manager when booting client computers. You’ll get the following information:
Stage one: an IP configuration will be provided (which makes sense as you have your DHCP), and the boot image will be retrieved on the WDS server.
Stage two: if you have several images, you’ll get to a menu with different options (a WDS server can host different install or capture images). Then you’ll get to a standard Windows installation interface. If you’ve chosen a “zero-touch” installation, the deployment can happen in a few minutes.
And that’s it! You have a system capable of responding to requests from clients wanting a new operating system.
Additional Resources
Windows deployment services overview from Microsoft.
Let’s Recap!
Windows Server lets you manage the deployment of operating system images through the WDS role.
It is possible to boot a client computer via the network and install a system without needing a CD or a USB drive.
It is possible to set up a master computer that will then be ingested into WDS so that the image from its operating system (checked and configured) will be redeployed across a host of machines.
WDS also manages systems that don’t have PXE (network booting), using discover images to hook a computer to a WDS server after booting using a removable medium (CD/DVD/USB).
Let’s now see what you can do with operating system images. See you in the next chapter!
