1. Deployment Services (WDS) in
Windows Server 2008
Microsoft® Virtual Labs

2. Deployment Services (WDS) in Windows Server 2008
Table of Contents
Deployment Services (WDS) in Windows Server 2008 ............................................................. 1
Exercise 1 Configuring the Windows Deployment Services.........................................................................................2
Exercise 2 PXE Booting a Client to Install Windows ...................................................................................................7

3. Deployment Services (WDS) in Windows Server 2008
Page 1 of 8
Deployment Services (WDS) in Windows
Server 2008
Objectives
After completing this lab, you will be better able to:
Configure Windows Deployment Services
Configure the boot menu
PXE boot a client to install Windows
Prerequisites
In Windows Server 2008 Beta 2, you can install the Windows Deployment
Services server role through the following means:
• From the Initial Configuration Tasks page
• From Server Manager
Estimated Time to
Complete This Lab
45 Minutes
Computer used in this Lab
NYC-DC-1

4. Deployment Services (WDS) in Windows Server 2008
Page 2 of 8
Exercise 1
Configuring the Windows Deployment Services
Scenario
Windows Deployment Services configuration is accomplished using the Windows Deployment Services
Configuration Wizard or by using WDSUTIL at the command prompt. We will have you click through the wizard.
Most of the command prompts are just for your information. Windows Deployment Services configuration involves
the following actions:
• Creating a shared folder that will contain the files necessary for PXE boot, the files for booting
Windows PE into RAMDISK, Windows PE boot images, and installation images for Windows Vista or
Windows Server 2008.
• Uploading a boot operating system image of the Windows Server 2008 version of Windows PE in WIM
format.
• Uploading an installation operating system image of Windows Vista, Windows Server 2008 Beta 2,
Windows Server 2003 or Windows XP in WIM format.
• Authorizing the PXE server listener in DHCP (optional).
• Configuring the answer settings of the PXE listener. This controls whether the server will service incoming
client boot requests.
Tasks Detailed Steps
Complete the following 5
tasks on:
NYC-DC-1
1. Windows
Deployment Services
Setup Wizard
Note: During the configuration process, the following steps occur:
o Windows Deployment Services creates a shared folder with the name specified on
the Windows Deployment Services folder location page (the default is
c:RemoteInstall). The shared folder is named REMINST.
o Windows Deployment Services creates a directory structure under the REMINST
share to hold the appropriate files. The Boot directory contains the files necessary
to boot the client computer. This includes files related to the PXE boot as well as
files necessary to RAMDISK boot Windows PE. The Images directory contains the
installation images. The Tmp directory contains working files for the Windows
Deployment Services PXE server, such as the generated BCD files that will be
passed to the booting client in order to display the boot menu. After the directory
is created, relevant files will be copied from the %Windir%System32Reminst
directory (where they were placed when the Windows Deployment Services server
role was installed) to their appropriate place in the directory structure.
o The boot image architecture is read from the WIM metadata. After the boot
architecture type is determined, the Boot.wim file containing the Windows PE boot
image is copied to the appropriate Boot<arch>Images subdirectory.
o A folder that is specified on the Windows Installation Image Folder Name page is
created under the Images directory. The installation image, Install.wim, is then
copied from the Windows installation medium. After the file is copied, the image
name and image description values are modified, if necessary, according to the
data entered on the Image Name and Description page.
o Windows Deployment Services changes the startup type for WDSPXE and
TFTPD Services from Manual to Automatic.

5. Deployment Services (WDS) in Windows Server 2008
Page 3 of 8
Tasks Detailed Steps
o A key is written to the registry at: HKLMSoftwareMicrosoftWDS
SetupComplete and its value is set to 1 to indicate that Windows Deployment
Services configuration has completed successfully.
o To restore the server to a the state it was in prior to configuration, change the
value of SetupComplete to 0, remove the REMINST share and delete the folder
previously shared as REMINST.
o The WDSServer and TFTPD services start.
o If Microsoft DHCP is installed on the same physical computer as Windows
Deployment Services, the Windows Deployment Services Configuration Wizard
will add DHCP option tag 60, set to PXE client, to all DHCP scopes (as a DHCP
global option). This is necessary so that a booting PXE client can be notified that
there is a listening PXE server on the network. The default (assumed) installation
of Windows Deployment Services is that the Microsoft DHCP server and Windows
Deployment Services PXE server are on separate physical computers. When the
Windows Deployment Services PXE server and DHCP server exist on the same
computer, the Windows Deployment Services PXE server is not able to listen on
port 67 for the initial incoming PXE boot requests. This is because that port is
already in use by DHCP. In order for the client computer to know that there is a
PXE server listening on the network, it must be notified in the DHCP "Offer"
packet through the existence of DHCP option tag 60. The DHCP server is
responsible for sending this tag to the client if Windows Deployment Services and
DHCP exist on the same physical computer. If Microsoft DHCP and Windows
Deployment Services are on the same computer, the Windows Deployment
Services management tools adjust the value of UseDHCPPorts at
HKLMSystemCurrentControlSetServicesWDSServerProvidersWDSPXE to a
value of 0. It does this to indicate that the PXE service itself should not try to listen
on port 67. This ensures that the DHCP server will always be able to listen on port
67, regardless of the services startup order on the computer.
a. On the Master Status pane click and select HOL305-NYC-DC-1
b. Perform the following steps on the NYC-DC-1 virtual machine.
c. Ensure you are logged in as WOODGROVEBANKAdministrator with a
password of pass@word1.
d. On the Start menu, click Administrative Tools, and then click Windows
Deployment Services.
e. In the left-hand pane of the WdsMgmt MMC, click to expand Windows
Deployment Services.
f. Right click the Servers node and then click Add Server.
g. In the Add Server dialog box, the local server is selected by default. Click OK to
continue.
h. Expand the tree. Right click the server, NYC-DC-1.WOODGROVEBANK.com
and click Configure Server.
i. At the Welcome page, ensure that you have met the following minimum
requirements for completing the Windows Deployment Services Setup Wizard:
o This computer must be a member of an Active Directory domain
o An active DHCP server on your network
o An active DNS server on your network
o An NTFS partition on the Windows Deployment Server for storing
images
j. Click Next to continue.

6. Deployment Services (WDS) in Windows Server 2008
Page 4 of 8
Tasks Detailed Steps
k. In the path field, leave the default path C:RemoteInstall
Note: Remote Installation Folder Location
The RemoteInstall folder will eventually contain a directory tree that houses the
installation images, Windows PE boot images, and the network boot files that are
necessary to PXE boot a client computer. Therefore, you should place the
RemoteInstall folder on a volume that contains enough disk space to house all of the
images you plan to upload to the server. The folder specified here becomes the
Reminst share.
l. Click Next to continue.
Note: System Volume Warning
m. Click Yes to continue.
Note: DHCP Option 60
This screen appears when the Microsoft DHCP service is found on the server being
configured as a Windows Deployment Services server. Microsoft DHCP and Windows
Deployment Services both listen for the client discover signal on port 67. The default
setting for this screen sets Windows Deployment Services to not listen on port 67.
Additionally, DHCP Option 60 is set to PXEClient by default when you first see this
page.
n. Click the checkbox Do not listen on port 67.
o. Click the checkbox Configure DHCP Option 60 to ‘PXEClient’.
p. Click Next to continue.
q. Select the radio button Respond to all (known and unknown) client computers.
Note: PXE Server initial Settings
The default is to not respond to any client computer. However, you can adjust the
settings at this point in the configuration process so that when this wizard completes,
the server will be operational and servicing clients. The following options on this page
for client support dictate whether the Windows Deployment Services PXE server will
answer incoming client PXE requests, and, if so, whether the client must be "known."
o Do not respond to any client computer. If you accept the Default PXE server
answer policy, the Windows Deployment Services PXE server will not service any
client PXE boot requests following initial configuration of the server.
o Respond only to known client computers. Choosing this option requires all
computer accounts to be created in Active Directory before they will be serviced
by Windows Deployment Services. This process is called prestaging devices. Those
devices that have been prestaged to Active Directory become "known" devices to
Windows Deployment Services. Devices that have not been prestaged in Active
Directory will be "unknown" devices. This option further restricts the Windows
Deployment Services PXE server answering capability to only those devices
prestaged in Active Directory. For more information about how to prestage client

7. Deployment Services (WDS) in Windows Server 2008
Page 5 of 8
Tasks Detailed Steps
computers, see "Prestage client computers" on the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=50166).
o Respond to all (known and unknown) client computers. Choosing this option
allows all PXE clients to be serviced by Windows Deployment Services without
further configuration or prestaging in the Active Directory.
Note: If prompted with a note The service did not respond to the start or control
request in a timely manner, before clicking Finish on the wizard, click Start, point to
Administrative Tools, and then select Services.
Note: Locate the service Windows Deployment Services Server and ensure the service
is Started and set to Automatic.
Note: If the service still fails to start, you may have to reboot the HOL305NYC-DC-1
virtual machine. This is very rare.
Note: Close the Services console.
Note: Back on the Windows Deployment Services Configuration Wizard, if seen,
uncheck the check box Add images on the Windows DS Server now and then click
Finish.
r. Click Finish
s. If prompted with an invalid pointer dialog box, click OK.
t. Uncheck Add images to the Windows Deployment Server now.
u. Click “Finish”
v. Ensure the wizard is now closed.
2. Adding Images Note: You can specify the location of the images to be uploaded. The location may be
a CD or DVD, or it may be a network share that contains the image files
Note: The boot operating system and installation operating system images initially
uploaded to the Windows Deployment Services server must come from the original
installation CD of Windows Server 2008 or Vista RTM. This is necessary in order to
ensure that the proper Windows PE boot image is available and put in place on the
server.
Note: You can specify the name of the image group that you want to contain the
installation image. The wizard creates the image group specified here under the
RemoteinstallImages directory on your Windows Deployment Services server. The
default image group is named "ImageGroup 1"
a. From the WdsMgmt console, expand NYC-DC-1.WOODGROVEBANK.com,
right-click Install Images and then click Add Install Image.
b. Create a new Image Group called ImageGroup1, click Next.
c. On the Image File screen click Browse.
d. Navigate to C:OriginalsWindows Server Longhorn Beta 3 and select
Install.wim, click Open, then click Next.
e. On the list of Available Images Uncheck All instances of 2008 with the exception
of Windows Longhorn Server Enterprise click Next.
f. On the Summary Screen review the settings and click Next.
g. When the operation completes click Finish.
Note: 2008 Server Enterprise
For this lab you unchecked the Enterprise version of Windows 2008 Server. This was
only to save time.
3. Configuring the Boot
Menu
Note: Upon PXE boot, prior to the operating system being loaded, the Windows
Deployment Services Client presents a boot menu. The boot menu allows Windows
Deployment Services to support separate boot architectures and a choice of boot
images for each architecture type. This mechanism uses the same BCD menu structure

8. Deployment Services (WDS) in Windows Server 2008
Page 6 of 8
Tasks Detailed Steps
that is used in Windows operating systems.
Note: With Windows Deployment Services, it is possible for you to have x64-based
computers and to boot x64-based boot images. For example, part of a server-building
process might require booting x64-based computers into an x64-based version of
Windows PE in order to test a 64-bit networking card driver prior to installation.
Although a 32-bit version of Windows PE would run on the 64-bit computer, it would
not be able validate the 64-bit network adapter driver
Note: The Windows Deployment Services boot menu is configured when more than
one boot image exists on the Windows Deployment Services server. The following
steps explain the process for adding images. The next procedure explains how to
create and add a capture image. A capture image basically allows you to ‘capture’ an
existing machine’s image and load it into the WDS server to be served to other clients.
4. Add an X86
Windows PE Boot
Image
a. Perform the following steps on the HOL305-NYC-DC-1 virtual machine.
b. Ensure you are logged in as WOODGROVEBANKAdministrator with a
password of pass@word1.
c. If the WdsMgmt MMC is not already open, on the Start menu, click
Administrative Tools, and then click Windows Deployment Services.
d. In the left hand pane of the WdsMgmt MMC, click to expand Windows
Deployment Services.
e. Click to expand the Servers list, and then click to expand the server to which to
add the image, NYC-DC-1.WOODGROVEBANK.com. (You may need to add
the local server again).
f. Right-click the Boot Images node and click Add Boot Image.
g. Click Browse and Navigate to C:OriginalsWindows Server Longhorn Beta
3Boot.wim, click Open, then click Next.
h. Leave the Image Metadata as the Default and click Next.
i. Click Next on the Summary screen.
j. When it has completed click Finish.
5. Create and Add a
Capture Image
a. If not already open, in the Start menu, select Administrative Tools, and click
Windows Deployment Services.
b. In the left hand pane of the WdsMgmt MMC, click to expand Windows
Deployment Services.
c. Click to expand the Servers list, and then click to expand the server to which to
add the image, NYC-DC-1.WOODGROVEBANK.com. (You may need to add
the local server again).expand NYC-DC-1.woodgrovebank.com
d. Select the Boot Image node.
e. In the right pane, right-click Microsoft Windows 2008 Setup (x86) and click
Create Capture Boot Image.
f. On the Capture Image Metadata screen, in the Image Name field, type
CaptureImage. In the Image Description field, type CaptureImage.
g. In the Enter Location and Filename field, click Browse.
h. Navigate to C:RemoteInstallBootx86Images. In the File name field, type
CaptureImage and then click Open. Click Next.
i. When the capture image has completed successfully, click Finish to exit the
Wizard.
j. Close the WdsMgmt window.
Note: Due to Technical Constraints. Exercise 2 Can Not Be Performed in the Virtual
Environment. The Exercise Steps are Left in The Manual Solely for References.

9. Deployment Services (WDS) in Windows Server 2008
Page 7 of 8
Exercise 2
PXE Booting a Client to Install Windows
Scenario
Windows Deployment Services relies on Pre-boot Execution Environment (PXE) technology to allow a client
computer to network boot and remotely connect over a TCP/IP network connection to a Windows Deployment
Services server in order to install an operating system. The client computers using this process must support remote
booting with a PXE ROM.
Prerequisites for PXE Booting a Client to Install Windows
The following requirements must be met to complete this task:
o The client computer must be capable of PXE boot.
o The environment must meet the requirements in the section "Configuring Windows Deployment Services."
o An appropriately configured Windows Deployment Services server must be available in the domain.
o Your user account must be a member of the Domain Users group.
Tasks Detailed Steps
Complete the following
task on:
NYC-DC-1
1. PXE-Booting a
Computer to Install
Windows
Note: Enabling a computer to PXE boot usually involves configuring the BIOS boot
order to enable booting from the network. You should configure the BIOS boot order
so that "boot from network" is first in the ordered list. This ensures that, in all cases,
the device will be able to PXE boot. Placing "boot from network" before "boot from
hard drive" allows the computer to PXE boot even after an operating system is
installed. In Virtual Server 2005 R2, the client should be set to PXE (F12) boot by
default.
Note: After pressing F12, the network boot program will use TFTP to download the
operating system loader. For computers that are x86-based or x64-based, this means
going back to the server to retrieve Bootmgr.exe. For Itanium-based, Extensible
Firmware Interface (EFI) systems, Bootmgfw.efi, which is already downloaded,
provides this functionality.
Note: Default boot programs by architecture are:
o x86-based: reminstbootx86Pxeboot.com
o Itanium-based: reminstbooti64Bootmgfw.efi
o x64-based: reminstbootx64Pxeboot.com
Note: Next, the operating system loader will download the correct BCD file based on
architecture. Windows Deployment Services generates these BCD files and places
them into the TMP directory on the remote installation shared folder. There is a BCD
file for each architecture, and a second BCD for x64-based computers, which will
show both x86-based and x64-based available boot images. x64-based computers are
capable of running both types of boot images.
a. Ensure the NYC-DC-1 is completely booted and you can see the Ctrl+Alt+Del
logon screen or ensure you are logged on.
b. On the Master Status pane click and select HOL305-NYC-PXE
c. Turn on or reboot the NYC-PXE virtual machine, to ensure a complete fresh boot
up showing the BIOS screen. (Click inside of the NYC-PXE virtual machine
window and press Right-Alt + Del if necessary).
d. Press F12 at the download prompt to start the PXE boot process. You will have to
press F12 as soon as you see the prompt.

10. Deployment Services (WDS) in Windows Server 2008
Page 8 of 8
Tasks Detailed Steps
Note: Because of the virtual machine environment, you may have to reboot (Right-
Alt+Del) several times in order to receive the proper F12 prompt. Try letting the
NYC-PXE virtual machine boot all of the way through, and reboot automatically the
first time, and then look for the F12 prompt. If it is still not working, back on the NYC-
DC-1 virtual machine, ensure your services, such as DHCP service, with option 060
PXEClient, and Windows Deployment Services service are running and had been
restarted (via a reboot) earlier when making changes. If you are still unable to obtain
a valid 192.168.1.x IP address and you have performed the reboot steps above, and
you still cannot get the F12 prompt to appear, if you have an IP address of 10.237.0.x
you need to disable the auto DHCP setting in Virtual Server the program on your host
OS by clicking the Master Status page, under Virtual Networks, select Configure and
then click Internal Network. Ensure that you DISABLE the Auto DHCP setting in
Virtual Server.
e. Select the appropriate Windows PE boot image from the available boot menu,
Microsoft Windows 2008 Setup (x86) and then press Enter to install a fresh
Operating System on the ‘bare metal’ client.
Note: CaptureImage
There is also the option to select the CaptureImage that you created earlier. This is
used when you want to take the OS image that is currently installed on the machine
you are on, and create or ‘capture’ that image so it is available for other end-users to
install on their machines. For the purposes of this lab, we will not be using the
CaptureImage boot image.
Note: Boot Menu Load Time
This may take a long time to load the Boot Menu files in a virtual environment,
depending on the speed of your host machine and configuration. End the lab here, as
the rest of the steps will simply load a fresh OS via a wizard.