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.

• Windows Deployment Services Update
• Adding Drivers To Windows Deployment Services Boot Images
• Windows Deployment Services Download

A while back, I posted an article on building a SharePoint development environment in Hyper-V, which included a part on automating deployment of the host machine. Although we've now moved to VMware Workstation, we still use this approach for automating deployment of our standard Windows 7 builds. For Windows Deployment Services, I had downloaded all the drivers needed and dumped them in the driver repository (in their own group). Fired up a laptop applicable to those drivers and installed. All drivers installed but 3. So I go into the drivers folder where the actual drivers are and inspect one of the 3. No inf file anywhere.

• 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.

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.

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.

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]

See also[edit]

But while variations can and will exist, the degree to which they affect your deployment plan can be exponentially reduced by standardizing rollouts for new and existing devices, as well as the OSes that will be supported, along with their respective drivers and pre-installed applications.

SEE: How to create a Windows-based USB installer

Naturally, Microsoft's Windows Deployment Services (WDS) handles this with relative ease. Part PXE server, part TFTP server, WDS acts as both a repository and transport mechanism of the Windows boot and install files. WIM, short for Windows Imaging File Format, is a disk-based file type used by Microsoft to install Windows or boot devices to their Windows Preinstallation Environment (WinPE) as a means of facilitating a granular level of control over computers before, during, and after the installation phase.

Before getting started, there are a few requirements that are necessary for WDS to run smoothly. Let's have a look.

Requirements

• Server running Windows Server 2003 SP1 (Windows Server 2008 or newer highly recommended)
• DHCP services running on the network
• DNS services running on the network
• Storage drive(s) formatted with NTFS for storing deployment images
• Active Directory Domain Services (Optional, Standalone mode may be used unless choosing to run WDS in Integrated mode, which does require being a member of the domain or DC)
• Administrative credentials

With the requirements out of the way, let's delve into the installation process, shall we?

Installing WDS

Log on to the server with an account delegated admin rights. Launch the Server Manager application and select Local Server Tasks Add Roles and Features (Figure A).

Figure A

The Before You Begin page will load; if you are experienced at adding/removing roles, check the Skip This Page By Default check box and click Next to continue with the wizard (Figure B).

Figure B

Select the Role-Based Or Feature-Based Installation radio button (Figure C) and click Next to proceed.

Figure C

On the next page, you'll select the server that the service will be installed on. Click on the hostname of your server (Figure D) and click Next.

Figure D

In the Server Roles section, you must scroll and drill down to Remote Server Administration Tools Role Administration Tools Windows Deployment Services Tools. Select the Include Management Tools (If Applicable) check box and click the Add Features button (Figure E).

Figure E

In the Features section, ensure that the Remote Server Administration Tools check box is selected (Figure F) and click Next.

Windows Deployment Services Update

Figure F

The WDS role includes a few notes about the services it provides on the following page (Figure G); click Next to continue to Role Services.

Figure G

If this is your one and only WDS server, select both the Deployment Server and Transport Server check boxes ((Figure H). This will be required to deploy images successfully. If you would like to divide the services among several servers, select only the check box next to the service that particular server will be used for. Most users, at least initially, will be better served by selecting both check boxes. Click Next to confirm.

Figure H

At the confirmation page, if everything appears correct, click the Install button to proceed with the service(s) installation. WDS does not require restarting the server upon completion. But if you will be deploying multiple WDS servers within your environment, clicking the Export Configuration Settings link will export these settings to an XML file that can be used later to configure the installation of the service(s) on other servers, automating much of the process (Figure I).

Figure I

Once WDS has been installed, you must configured prior to first use. Follow along below to configure Windows Deployment Services.

SEE: Windows Server 2016 TP5: Feature-complete and on track for RTM (Tech Pro Research)

Configuring WDS

Launch the WDS snap-in either by locating it in the Administrative Tools folder, using the MMC, or executing the command wdsmgmt.msc to load the console for the first time.

Within the nested hierarchy under Servers, you'll notice a small yellow exclamation mark symbol next to your server's hostname (Figure J). This indicates your server is not configured for WDS. Right-click the server name and select Configure Server from the context menu Figure K).

Figure J

Figure K

A wizard will guide you through the configuration process (Figure L). Click Next after verifying that the requirements have been met.

Figure L

Decision time. WDS allows for configuring a Standalone mode, which operates independently of Active Directory (AD), or an Integrated mode, which works with AD (Figure M). The one you choose will slightly affect how WDS works and more important, how much access you'll have to manage your WDS server. Integrated mode will allow for seamless integration with AD; however, the caveat is that certain changes will require Domain Administrator-level credentials. If you do not have this, you'll effectively be locked out of certain features. Conversely, Standalone mode will allow the most freedom when managing your WDS server, regardless of Domain Admin credentials. But it does so at the expense of not being tied in with AD. Choose wisely, as once Integrated mode is selected, it can't be downgraded to Standalone—although Standalone mode can always be upgraded to Integrated. Click Next to proceed.

Figure M

WDS will create a shared folder where the installation and boot WIMs will be stored and served to clients on the network. Select the default path or enter a custom path to store these directories (Figure N) and click Next.

Adding Drivers To Windows Deployment Services Boot Images

Figure N

When selecting a drive that is also home to the system volume, a warning message will be displayed asking if you wish to continue with your selection or select another location (Figure O). This is ensure that performance isn't negatively affected. Once you're satisfied with your selection, click Yes to continue.

Figure O

The PXE Server settings will be configured on the following page (Figure P). These settings dictate how PXE behaves while receiving a boot request from a client. Known clients are defined as computers whose accounts (or objects in AD) have been prestaged; unknown clients refer to any computers that do not have matching AD accounts. By default, selecting Respond To All Client Computers (Known And Unknown) works well. For additional security, select the Require Administrator Approval For Unknown Computers check box. This will force the computer to await explicit authorization before it will be processed by the PXE server. Click Next to continue.

Figure P

The configuration process for WDS takes several minutes, depending on the speed of the server being used (Figure Q).

Figure Q

Once WDS has been successfully configured, it'll be ready to use, except it does not have any media -boot or install WIMs—to deploy. These may be added post-WDS configuration by selecting the Add images To The Server Now check box or it can be deferred until a later time (Figure R). Click the Finish button to complete the configuration.

Figure R

Windows Deployment Services will require boot images to respond to client requests and install images to actually deploy Windows onto these client systems. By right-clicking and selecting Add Images from the Install Images and Boot Images nodes in the console (Figure S and Figure T), you'll be able to take the boot.wim and install.wim directly from a Windows DVD media disk or ISO and import them into WDS for deployment. This will allow for specified OSes to be installed by default on client computers in a straightforward manner.

Figure S

Figure T

Also read...

Windows Deployment Services Download

Your take

Has WDS simplified your Windows deployment tasks? Share your experiences and advice with fellow TechRepublic members.