Documente Academic
Documente Profesional
Documente Cultură
Abstract
This guide provides an introduction to Windows Deployment Services in Windows Server 2008.
It includes an overview of features, tasks you can use to test Windows Deployment Services, and
details about the technology.
Copyright Information
This document supports a preliminary release of a software product that may be changed
substantially prior to final commercial release, and is the confidential and proprietary information
of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the
recipient and Microsoft. This document is provided for informational purposes only and Microsoft
makes no warranties, either express or implied, in this document. Information in this document,
including URL and other Internet Web site references, is subject to change without notice. The
entire risk of the use or the results from the use of this document remains with the user. Unless
otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places, and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place,
or event is intended or should be inferred. Complying with all applicable copyright laws is the
responsibility of the user. Without limiting the rights under copyright, no part of this document
may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or
by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any
purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
2007 Microsoft Corporation. All rights reserved.
Active Directory, Microsoft, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT, Active
Directory, and Windows Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
This product contains graphics filter software; this software is based, in part, on the work of the
Independent JPEG Group.
All other trademarks are property of their respective owners.
Contents
Windows Deployment Services Role Step-by-Step Guide..............................................................5
In this guide................................................................................................................................. 5
What is Windows Deployment Services?....................................................................................5
Whats new in Windows Deployment Services?.......................................................................6
Who should use this guide?..................................................................................................... 7
Benefits of Windows Deployment Services..............................................................................7
Installing Windows Deployment Services....................................................................................7
Prerequisites for installing Windows Deployment Services......................................................7
Steps for installing Windows Deployment Services..................................................................8
Upgrading from a server running Windows Server 2003 with SP1 or SP2..................................9
Configuring Windows Deployment Services..............................................................................10
Known issues with configuring Windows Deployment Services.............................................10
Steps for configuring Windows Deployment Services............................................................11
Using the Windows interface............................................................................................... 11
Using WDSUTIL at a command prompt..............................................................................12
Configuring the boot menu........................................................................................................ 13
Known issues with configuring the boot menu.......................................................................13
Steps for configuring the boot menu......................................................................................13
Creating and modifying boot and install images........................................................................15
Prerequisites for creating and modifying images....................................................................15
Known issues with creating images.......................................................................................16
Capture image.................................................................................................................... 16
Discover image................................................................................................................... 17
Steps for creating install images............................................................................................ 19
Installing an operating system................................................................................................... 20
Prerequisites for installing an operating system.....................................................................20
Steps for installing an operating system.................................................................................20
Using unattend files................................................................................................................... 21
Prerequisites for using unattend files.....................................................................................21
Known issues with using unattend files..................................................................................21
Steps for using unattend files................................................................................................. 21
Configuring unattended installation for the Windows Deployment Services client..............21
Configuring unattend installation for Windows Setup..........................................................22
Creating a multicast transmission.............................................................................................. 23
Prerequisites for creating a multicast transmission................................................................23
Known issues in creating a multicast transmission................................................................23
Steps for creating a multicast transmission............................................................................24
Using the Windows interface..............................................................................................24
Using WDSUTIL................................................................................................................. 25
Transport Server........................................................................................................................ 27
Additional references................................................................................................................. 27
In this guide
Upgrading from a server running Windows Server 2003 with SP1 or SP2
Transport Server
Additional references
Client components. These components include a graphical user interface that runs within
the Windows Pre-Installation Environment (Windows PE). When a user selects an operating
system image, the client components communicate with the server components to install the
image.
Management components. These components are a set of tools that you use to manage
the server, operating system images, and client computer accounts.
Reduces the complexity of deployments and the cost associated with inefficient manual
installation processes.
Supports mixed environments that include Windows Vista, Windows Server 2008, Microsoft
Windows XP and Microsoft Windows Server 2003.
Provides an end-to-end solution for the deployment of Windows operating systems to client
computers and servers.
Built on standard Windows Server 2008 setup technologies including Windows PE, .wim files,
and image-based setup.
Transport Server
Deployment Server
Transport Server
To start the installation using the Initial Configuration Wizard, click Add roles on the Initial
Configuration Tasks startup screen. Click Next and then select Windows Deployment
Services.
To start the installation using Server Manager, click Add roles which is located within the
Roles Summary pane. Click Next and then select Windows Deployment Services.
During the installation, you have the following two role services to choose from. For a detailed
comparison of these options, see the Comparison of Deployment Server and Transport Server
chart at http://go.microsoft.com/fwlink/?LinkId=89222.
Transport Server. To install this option, deselect Deployment Server on the second
installation wizard screen. This option provides a subset of the functionality of Windows
Deployment Services. It contains only the core networking parts. You can use Transport
Server to create multicast namespaces that transmit data (including operating system
8
images) from a standalone server. You should use this option if you want to transmit data
using multicasting, but do not want to incorporate all of Windows Deployment Services.
Deployment Server. To install this option, ensure that both Deployment Server and
Transport Server are selected on the second installation wizard screen. This option provides
the full functionality of Windows Deployment Services, which you can use to configure and
remotely install Windows operating systems. With Windows Deployment Services, you can
create and customize images and then use them to re-image computers. Deployment Server
is dependent on the core parts of Transport Server.
If RIS is currently running on the server but you do not have Windows Deployment Services
installed, then you must install it before upgrading. Windows Deployment Services is included
in the Windows Automated Installation Kit (Windows AIK) and Windows Server 2003 Service
Pack 2. For more information about how to install and configure, see the Windows
Deployment Services Update Step-by-Step Guide for Windows Server 2003
(http://go.microsoft.com/fwlink/?LinkId=94643). Then use the instructions below to change
from Legacy mode (default) to Native mode.
If RIS was installed on the server when you installed Windows Deployment Services, it will be
in Legacy or Mixed modeyou will need to change it to Native mode before upgrading.
If RIS was not installed on the server when you installed Windows Deployment Services, the
server will be in Native mode and therefore ready to be upgraded to Windows Server 2008.
Using the MMC snap-in. On the Start menu, click Administrative Tools, and then
click Windows Deployment Services. Right-click the server and select Initialize
Server.
2. When the process completes, use the following procedure to change the server mode to
Native.
For more information about these options, download the guide located at
(http://go.microsoft.com/fwlink/?LinkId=81031) and see "Chapter 7: Working With
Images".
2. Run WDSUTIL /Set-Server /ForceNative.
3. When the process completes, the server is ready to be upgraded to Windows
Server 2008.
Creates a shared folder that contains the files necessary for PXE boot, the files for booting
Windows PE into RAMDISK, Windows PE boot images, and install images.
Configures the answer settings of the PXE listener to control whether and how the server
services incoming client boot requests.
Adds DHCP option tag 60, with the PXE client setting selected, 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.
Selects the Do not Listen on port 67 option. This is necessary so that booting clients
can find the DHCP server on the network.
Internet Protocol version 6 (IPv6) is not supported for this version of Windows Deployment
Services. Even though the management utilities show that you can specify the IPv6 address
range, these options do nothing in this version of Windows Deployment Services.
If you are using the standard boot images (boot.wim) from the media, it must match (or be
newer than) the operating system of the install image. For example, if you are installing
Windows Server 2008, you must use the Boot.wim from the Windows Server 2008 media
you cannot use the Boot.wim from the Windows Vista media.
10
If you are running Windows Deployment Services and a non-Microsoft DHCP server on the
same computer, in addition to configuring the server to not listen on port 67, you will need to
use your DHCP tools to add Option 60 to their DHCP scopes.
If DHCP is installed on a server that is located in a different subnet, then you will need to do
one of the following:
(recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67
by client computers should be forwarded directly to both the DHCP server and the
Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the
client computers to the Windows Deployment Services PXE server should be routed
appropriately (these requests direct traffic to the server, not broadcasts).
Add DHCP options 66 and 67. For more information, see the PXE Boot chapter at
http://go.microsoft.com/fwlink/?LinkId=88439.
Follow the instructions in Creating and modifying images if you would like to create a
custom install image.
/ImageGroup:<name>
Note
Help for WDSUTIL is available by typing WDSUTIL /? at a command prompt.
The boot menu can contain no more than 13 boot images. This is because of a limitation
in the number of characters displayed from within the operating system loader boot menu.
The name of the .wim file that contains the boot image cannot contain any spaces. This
file can contain only letters or numbers.
The boot image must match the operating system. If you are using the standard boot
images (boot.wim) from the media, it must match (or be newer than) the operating system of
the install image. For example, if you are installing Windows Server 2008, you must use the
Boot.wim from the Windows Server 2008 mediayou cannot use the Boot.wim from the
Windows Vista media.
Double-byte character sets used as image names might not display properly in the
boot menu. This issue pertains to localized strings. Limitations within the BIOS character
sets do not allow the characters to display properly.
Reformat the hard disks to support BitLocker Drive Encryption (using unattend) and then
install Windows.
Contain the Windows Recovery Environment (Windows RE) that you want to use when a
computer fails to start.
Contain the Windows Deployment Services Image Capture Wizard, which creates an install
image from the client computer's operating system.
13
Includes a Windows PE image for administrators who want perform other operations from
within Windows PE.
In addition, x64-based computers can run x86-based or x64-based Windows PE boot images.
Therefore, for each of these tasks, you could have two boot imagesone for x86 and one for
x64. In this case, the boot menu on x86-based computers will only display the x86 boot images
(because x86-based computers cannot run x64 boot images).
Note
The default behavior is for x64-based computers to display both x86-based and x64based boot images when both are available. To change this default, run WDSUTIL /SetServer /Defaultx86x64ImageType:{x86|x64|both}.
The following procedures outline how to add more boot images to the boot menu. To view help for
WDSUTIL, type WDSUTIL /? at a command prompt.
To complete this task, ensure that you are a member of the Local Administrators group on the
Windows Deployment Services server.
To add an additional boot image by using the Windows interface
1. In the left-hand pane of the Windows Deployment Services MMC snap-in, click to expand
the server list, and then choose the server to which you want to add the boot image.
2. Right-click the Boot Images node, and then click Add Boot Image.
3. Click Browse to locate the boot image that you want to add. The boot image must be
located on the server and it can be the same or different architecture.
4. Follow the instructions in the wizard to add an additional boot image.
5. When you have completed this procedure and you PXE boot a client computer, a boot
menu will appear that shows both boot images.
To add an additional boot image at a command prompt
1. Click Start, right-click Command Prompt, and then click Run as administrator.
2. Run the following command to add an additional boot image, where <bootimage> is the
full path to the boot image on the server. The image can be the same or a different
architecture.
WDSUTIL /Add-Image /ImageFile:<bootimage> /ImageType:boot
3. When you have completed this procedure and you PXE boot a client computer, a boot
menu will appear that shows both boot images.
Note
Help for WDSUTIL is available by typing WDSUTIL /? at a command prompt.
To make any additional changes to the boot menu, use Bcdedit.exe to edit the default.bcd file
located at %REMINST%\boot\<architecture>. You can run bcdedit /? at a command prompt to
see the command line options.
14
For more information about Bcdedit, see Boot Configuration Data Editor Frequently Asked
Questions (http://go.microsoft.com/fwlink/?LinkID=65818).
Boot images. Boot images are the images that you boot a client computer into to perform an
operating system installation.
Install images. Install images are the operating system images that you deploy to the client
computer.
You can modify images to add files or drivers without having to create a new image using the
tools in the Windows AIK. The processes are similar for a boot or install image, however the tool
sets and syntax vary between image types. For more information, see the Working with Images
chapter at http://go.microsoft.com/fwlink/?LinkId=88439.
In this section:
Ensure that there is enough disk space to create and store the new images.
Be a member of the Local Administrators group on the Windows Deployment Services server.
Match the version of Sysprep.exe with the version of the operating system that you want to
capture.
Install the Windows AIK if you are creating bootable ISO images
(http://go.microsoft.com/fwlink/?LinkId=81030).
Have a writeable CD or DVD and a disk-burning utility (if you are burning an image to media
for example a discover image),
need to add drivers to the image), you will not need to modify this file.You can create the following
types of boot images using Windows Deployment Services:
Capture images. Boot images that you boot a client computer into in order to capture the
operating system into a .wim file.
Discover images. Boot images that you can use to install an operating system onto a
computer that is not PXE enabled.
Capture image
Capture images are boot images that launch the Windows Deployment Services Capture
Utility instead of Setup. When you boot a reference computer (that has been
prepared with Sysprep) into a capture image, a wizard creates an install image
of the reference computer and saves it as a .wim file.
You can also create media (CD, DVD, USB drive, and so on) that contains a capture image, and
then boot a computer from the media. After you create the install image, you can add the image
to the server for deployment. These images provide an alternative to the command-line utility,
ImageX.exe.
To create a capture image using the Windows interface
1. In the Windows Deployment Services MMC snap-in, expand the Boot Images node.
2. Right-click the image to use it as a capture image.
3. Click Create Capture Boot Image.
4. Type a name, description, and the location to save a local copy of the file. You must
specify a location in case there is a problem with the network when you deploy the
capture image.
5. Continue to follow the instructions in the wizard, and when it is complete, click Finish.
6. Right-click the boot image folder.
7. Click Add Boot Image.
8. Browse and select the new capture image, and then click Next.
9. Follow the instructions in the Windows Deployment Services Capture Utility.
10. Once you have created the capture image, follow the instructions in the Install Image
section to boot a client computer into the capture image and capture the operating
system.
To create a capture image at a command prompt
1. Click Start, right-click Command Prompt, and then click Run as administrator.
2. Type the following where <bootimage> is the name of the boot image you want to use to
create the capture image, and <captureimage> is the file path and file name of the new
capture image:
WDSUTIL /New-CaptureImage /Image:<bootimage> /Architecture:x86
/Filepath:<captureimage>
16
3. Type the following where <captureimage> is the file path and file name of the capture
image you want to add to the image store:
WDSUTIL /Add-Image /Imagefile:<captureimage> /ImageType:boot
Note
Help for WDSUTIL is available by typing WDSUTIL /? at a command prompt.
4. Once you have created the capture image, follow the instructions in the Install Image
section to boot a client computer into the capture image and capture the operating
system.
Discover image
Discover images are boot images that force Setup.exe to launch in Windows Deployment
Services mode and then discover a Windows Deployment Services server.
These images are typically used to deploy images to computers that are not
PXE enabled or that are on networks that do not allow PXE. When you create a
discover image and save it to media (CD, DVD, USB drive, and so on), you can
then boot a computer to the media. The discover image on the media locates a
Windows Deployment Services server, and the server deploys the install image
to the computer.
Note
You can configure discover images to target a specific Windows Deployment Services
server. This means that if you have multiple servers in your environment, you can create
a discover image for each, and then name them based on the name of the server.
To create a discover image by using the Windows interface
1. In the Windows Deployment Services MMC snap-in, expand the Boot images node.
2. Right-click the image you want to use as a discover image.
3. Click Create Discover Boot Image.
4. Follow the instructions in the wizard, and when it is complete, click Finish.
5. Right-click the boot image folder.
6. Click Add Boot Image.
7. Browse and select the new discover image, and then click Next.
8. Follow the instructions in the wizard.
To create a discover image at a command prompt
1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and
then click Run as administrator.
2. Type the following where <bootimage> is the name of the boot image that you want to
use to create the discover image, and <discoverimage> is the file path and file name of
the new discover image:
17
19
The client computer must have 512 MB of RAM, which is required to use Windows PE).
Windows Deployment Services client unattend file. This file uses the Unattend.xml format
and is stored on the Windows Deployment Services server in the \WDSClientUnattend folder.
It is used to automate the Windows Deployment Services client user interface screens (such
as entering credentials, choosing an install image, and configuring the disk).
Image unattend file. This file uses the Unattend.xml or Sysprep.inf format, depending upon
the version of the operating system in the image. It is stored in a subfolder (either $OEM$
structure or \Unattend) in the per-image folder. It is used to automate the remaining phases of
setup (for example, offline servicing, Sysprep specialize, and mini-setup).
To see examples, see "Sample Unattend Files" in the unattend installation chapter at
http://go.microsoft.com/fwlink/?LinkId=88439.
20
Ensure that you are a member of the Local Administrators group on the Windows Deployment
Services server.
21
Note
Help for WDSUTIL is available by typing WDSUTIL /? at a command prompt.
To associate a client unattend file per computer at a command prompt
1. Click Start, right-click Command Prompt, and then click Run as administrator.
2. Type the following where <relative path>is the path from the REMINST share to the folder
that contains client unattend file:
WDSUTIL /Set-Device /Device:<computername> /ID:<GUID or MAC address>
/WDSClientUnattend:<relative path>
<imagename> is the name of the image with which to associate the unattend file.
<imagegroupname> is the name of the image group containing the image file.
<unattendfile> is the path and file name of the unattend file to associate with the
image.
22
Note
For information about using multicast functionality with Transport Server, see the
Transport Server section.
At least one install image (that you want to transmit) on the server.
The boot.wim file from the Windows Server 2008 media (located in the \Sources folder).
The boot.wim from the Windows Vista DVD will not work with multicast transmission. You
must use the boot.wim from the Windows Server 2008 media. If you use the Windows Vista
file, you will be able to create the transmission, but people who boot into it will not be able to
join a transmission.
After you configure Windows Deployment Services server, if you modify the Multicast IP
Address, the UDP Port Range, or the RPC port number (by running wdsutil /set-server
/rpcport:<portnum>), you must restart the service before the changes will take effect. If you
do not restart the service, the server will use the old values and may not answer clients. To
restart the service, you can either 1) right-click Windows Deployment Services in the MMC
snap-in and click Restart or 2) run net stop wdsserver and then run net start wdsserver
from the command line.
Using WDSUTIL
23
Right-click the Multicast Transmission node, and then click Create Multicast
Transmission.
Auto-Cast. This option indicates that as soon as an applicable client requests an install
image, a multicast transmission of the selected image begins. Then, as other clients request
the same image, they too are joined to the transmission that is already started.
Scheduled-Cast. This option sets the start criteria for the transmission based on the number
of clients that are requesting an image and/or a specific day and time. If you do not select
either of these check boxes, then the transmission will not start until you manually start the
transmission. Note that in addition to these criteria, you can start a transmission manually at
any time by right-clicking the transmission and clicking Start.
Note
Content is transferred over the network only if clients request data. If no clients are
connected (that is, the transmission is idle), then data will not be sent over the
network.
Configuring transmissions
After a transmission is created, you can do the following:
Delete the transmission. If you right-click the transmission and click Delete, the multicast
transmission stops and each client installation will fall back to using unicast. That is, the client
installations will not be deleted or stopped, but they will not use the multicast transmission to
complete the installation.
Deactivate the transmission. If you right-click and click Deactivate, each client that is
currently installing will continue, but no new clients will be joined to the transmission. After
each current client installation is complete, the transmission will be deleted. If there are no
clients when you click this option, then it will be deleted instantly.
View properties. To view the properties, right-click the transmission, and click Properties.
Note that you cannot edit the properties of a transmission after it is created. To make a
change after you have created a transmission, you need to delete and recreate it.
Refresh the transmissions and data. To do this, right-click a transmission and click
Refresh. You can also refresh the data by pressing F5.
24
using Wdsmcast.exea command line tool included in the Windows AIK. When there are clients
in a transmission, you can:
Viewclients and see progress. To view any connected clients, expand the Multicast
Transmissions node, and click the image. The connected clients (including the current
installation time and the percent complete) are shown in the right pane.
Stop a client installation. To stop the installation completely, right-click a client and click
Disconnect. You should use this option with caution because the installation will fail and the
computer could be left in an unusable state.
Using WDSUTIL
Creating a multicast transmission for an install image
You have two options for transmission type: Auto-Cast and Scheduled-Cast.
Configuring transmissions
After a transmission is created, you can start it, delete it, deactivate it, and view its properties.
To view properties
25
To disconnect a client from a multicast transmission but continue to transfer the image
by using unicasting
Syntax: WDSUTIL /Disconnect-Client /ClientID:<id>
Transport Server
During installation, you can choose to install only Transport Server. This option provides a subset
of the functionality of Windows Deployment Services. It contains only the core networking parts.
You can use Transport Server to create multicast namespaces that transmit data (including
operating system images) from a standalone server. The standalone server does not need Active
Directory, DHCP or DNS. You can use Transport Server in advanced scenarios as a part of a
custom deployment solution. For information about using the Transport Server, see the Transport
Server chapter at http://go.microsoft.com/fwlink/?LinkId=88439.
Additional references
For a newsgroup about Windows Deployment Services, see Setup and Deployment
(http://go.microsoft.com/fwlink/?LinkId=87628)
Sysprep (http://go.microsoft.com/fwlink/?LinkId=87732)
For more information about the Windows Deployment Services Update for Windows
Server 2003, see the following:
Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003
(http://go.microsoft.com/fwlink/?LinkId=66145)
27