Escolar Documentos
Profissional Documentos
Cultura Documentos
Microsoft Corporation Published: March 2008 Author: Trina Gorman Editor: Katie Cumming
Abstract
This guide provides an introduction to Windows Deployment Services in Windows Server 2008. It includes an overview of features and procedures to follow to setup 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 Step-by-Step Guide......................................................................1 Abstract....................................................................................................................................1 Copyright Information......................................................................................................................2 Contents..........................................................................................................................................3 Step-by-Step Guide for Windows Deployment Services in Windows Server 2008.........................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 Upgrading from a server running RIS on Windows Server 2003 SP1 or SP2..............................7 Installing Windows Deployment Services....................................................................................9 Prerequisites for installing Windows Deployment Services......................................................9 Steps for installing Windows Deployment Services................................................................10 Configuring Windows Deployment Services..............................................................................11 Known issues with configuring Windows Deployment Services.............................................11 Steps for configuring Windows Deployment Services............................................................12 Steps for adding images.........................................................................................................12 Configuring the boot menu........................................................................................................13 Known issues with configuring the boot menu........................................................................14 Steps for configuring the boot menu.......................................................................................14 Creating custom install images..................................................................................................15 Prerequisites for creating custom install images....................................................................15 Known issues when creating custom install images...............................................................15 Steps for creating a capture image.........................................................................................16 Steps for creating an install image.........................................................................................17 Creating discover images..........................................................................................................18 Prerequisites for creating discover images.............................................................................18 Steps for creating discover images........................................................................................18 Installing an install image...........................................................................................................20 Prerequisites for installing an install image............................................................................20 Steps for installing an install image........................................................................................20 Performing an unattended installation.......................................................................................21 Prerequisites for performing an unattended installation.........................................................21 Known issues with unattended installations...........................................................................21 Steps for performing an unattended installation.....................................................................21 Configuring an unattended installation for Windows Deployment Services........................21
Configuring an unattended installation for Windows Setup.................................................22 Creating a multicast transmission..............................................................................................23 Prerequisites for creating a multicast transmission................................................................23 Known issues in creating a multicast transmission.................................................................24 Steps for creating a multicast transmission............................................................................24 Using the Windows interface...............................................................................................25 Using WDSUTIL..................................................................................................................26 Using the Transport Server role service.....................................................................................27 Uninstalling or uninitializing Windows Deployment Services.....................................................28 Additional references.................................................................................................................28
In this guide
What is Windows Deployment Services? Upgrading from a server running RIS on Windows Server 2003 SP1 or SP2 Installing Windows Deployment Services Configuring Windows Deployment Services Configuring the boot menu Creating custom install images Creating discover images Installing an install image Performing an unattended installation Creating a multicast transmission Using the Transport Server role service Uninstalling or uninitializing Windows Deployment Services Additional references
system directly from a CD or DVD. The components of Windows Deployment Services are organized into the following three categories: Server components. These components include a Pre-Boot Execution Environment (PXE) server and Trivial File Transfer Protocol (TFTP) server for network booting a client to load and install an operating system. Also included is a shared folder and image repository that contains boot images, install images, and files that you need specifically for network booting. There is also a networking layer, a multicast component, and a diagnostics component. 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.
The ability to deploy Windows Vista and Windows Server 2008. Windows PE is the boot operating system. Image-based installation, using the Windows image (.wim) file. The ability to transmit data and images using multicast functionality. The ability to transmit data and images using by multicast functionality on a standalone server (when you install Transport Server). An extensible and higher-performing PXE server component. A new graphical user interface on the client that you can use to select images. The Windows Deployment Services Microsoft Management Console (MMC) snap-in on the server, which enables you to
The ability to transmit data and images by using multicast functionality. The ability to transmit data and images using multicast functionality on a standalone server (when you install Transport Server). No support for RISETUP images or OSChooser screens. An enhanced TFTP server. Support for network boots of x64-based computers with Extensible Firmware Interface (EFI). Metric reporting for installations.
Deployment specialists interested in deploying images to computers that do not have operating systems installed
Upgrading from a server running RIS on Windows Server 2003 SP1 or SP2
There are two methods for moving an existing RIS infrastructure to Windows Deployment Services. This section outlines method 1.
With this method, you install Windows Deployment Services on your existing RIS servers. The three server modes and the ability to convert RIPREP images enable you to transition seamlessly from RIS to Windows Deployment Services. This is the recommended method of moving RIS infrastructure to Windows Deployment Services.
With this method, you install Windows Deployment Services on new servers in your environment while continuing to maintain the existing RIS servers. Eventually, after completely transitioning to Windows Deployment Services, the RIS servers are retired. This method is not recommended because it requires additional hardware and administrative overhead. Hardware. Each new Windows Deployment Services instance is running on a server separate from RIS. Administrative overhead. Having two PXE servers that are configured differently on the same network segment can lead to unpredictable results. Generally, for this scenario to be predictable, you must prestage each computer and specify whether or not the client should be answered by the Windows Deployment Services server or the RIS server.
There are three modes of operation for Windows Deployment Services in Windows Server 2003: Legacy, Mixed, and Native. Your server must be in Native mode to upgrade to Windows Server 2008. Your upgrade will be blocked if RIS is configured, or if your server is in Legacy or Mixed mode. To determine which operating mode the server is currently in, run the command WDSUTIL /get-server /show:config. Specifically, consider which of the following scenarios applies to you: If RIS is currently running on the server but you do not have Windows Deployment Services installed, you must install it before upgrading. Windows Deployment Services is included in the Windows AIK and Windows Server 2003 Service Pack 2. For more information about how to install and configure Windows Deployment Services, see the Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=94643). Then use the following procedures to switch from Legacy mode (the default setting) to Native mode. If RIS was installed on the server when you installed Windows Deployment Services, it will be in either Legacy or Mixed mode; you 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. Use one of the following procedures to change the server mode to Legacy. To change the server mode from Legacy to Mixed 1. Initialize the server by doing one of the following: Using the MMC snap-in. On the Start menu, click Administrative Tools, and then click Windows Deployment Services. Right-click the server, and then select Initialize Server. Using WDSUTIL. Run the command WDSUTIL /Initialize-Server /RemInst:C:\RemoteInstall (assuming that C:\RemoteInstall is the location of your REMINST shared folder). 2. When the process is completed, use the following procedure to change the server mode from Mixed to Native. To change the server mode from Mixed to Native 1. Retire your RISETUP and RIPREP images, or convert them to .wim format. To retire them, just delete the images. If you want to convert them, you have two options: Convert them offline (for RIPREP images only). For more information, see the "Converting RIPREP Images" section in the Creating Images topic. For instructions on how to do this, see How to Manage Images. Deploy and recapture them by using the image capture wizard (for RIPREP or RISETUP images). For more information, see Creating custom install images later in this guide. 2. Run the command WDSUTIL /Set-Server /ForceNative. 3. When the process is completed, the server is ready to be upgraded to Windows Server 2008.
AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller
Credentials. To install the role service, you must be a member of the Local Administrators group on the server 9
Deployment Server
Transport Server
for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services. DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. DNS. You must have a working DNS server on the network before you can run Windows Deployment Services. NTFS volume. The server running Windows Deployment Services requires an NTFS file system volume for the image store. Credentials. To install the role, you must be a member of the Local Administrators group on the server. To initialize the server, you must be a member of the Domain Users group. For more information about this, see the Required Permissions [role] topic.
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 in the Transport Server topic. 10
Transport Server. To install this option, clear the Deployment Server check box 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 images) from a standalone server. You should use this option if you want to transmit data by using multicasting, but you do not want to incorporate all of Windows Deployment Services. For more information, see Transport Server. 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 reimage computers. Note that Deployment Server is dependent on the core parts of Transport Server. Note If you want to manage Windows Deployment Services on a remote server that is runnning Windows Server 2008, you can install the Remote Server Administration Tools. To do this, open Server Manager, right-click the Features node, click Add Features, and locate Remote Server Administration Tools. This will install WDSUTIL and the Windows Deployment Services MMC snap-in on the server.
(Recommended) Configure your IP Helper tables. All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic, not broadcasts, to the server). Add DHCP options 66 and 67. For more information, see the Managing Network Boot Programs topic.
To add the default boot image included on the product installation DVD 1. In the left pane of the Windows Deployment Services MMC snap-in, right-click the Boot Images node, and then click Add Boot Image. 2. Browse to choose the default boot image (Boot.wim) on the Windows Server 2008 DVD, located in the \Sources folder. 3. Click Open and then click Next. 4. Follow the instructions in the wizard to add the image. To add the default install image included on the product installation DVD 1. In the Windows Deployment Services MMC snap-in, right-click the Install Images node, and then click Add Install Image. 2. Specify a name for the image group, and then click Next. 3. Browse to select the default install image (Install.wim) on the Windows Vista or Windows Server 2008 DVD, located in the \Sources folder, and then click Open. 4. To add a subset of the images included in the Install.wim file, clear the check boxes for the images that you do not want to add to the server. You should add only the images for which you have licenses. 5. Follow the instructions in the wizard to add the images. 6. Now that you have a boot image and an install image on the server, you can perform a PXE boot on a client computer to install an operating system.
menu on x86-based computers will display only 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 setting, run the command WDSUTIL /Set-Server /Defaultx86x64ImageType:{x86|x64|both}. For detailed information, see the Managing the Boot Menu[role] topic.
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 architecture or a different one. WDSUTIL /Add-Image /ImageFile:<bootimage> /ImageType:boot 3. When you have completed this procedure and you perform a PXE boot on a client computer, a boot menu will appear that shows both images (if both apply to that computer). Note Help for WDSUTIL is available by running the WDSUTIL /? command at a command prompt; it's also available online at WDSUTIL. You can now make additional changes to the boot menu, using the Bcdedit.exe tool to edit the Default.bcd file located at %REMINST%\boot\<architecture>. For more information, see the section "How to Use Bcdedit to Modify the BCD File" in the Managing the Boot Menu[role] in the topic.
If you add an x64 boot image and make a capture image from it, you will be able to boot only x64-based computers to it (not 32-bit computers).
3. Type the following command, 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; it's also available online at WDSUTIL. 4. After you have created the capture image, follow the instructions in the Installing an install image section to boot a client computer into the capture image and capture the operating system.
install image. Important You must enter a local location to save the new image; otherwise, you will not be able to capture the image. This requirement is enforced to avoid image corruption if there is a network malfunction. 9. Type a name for the image, using the .wim file name extension, and then click Save. Important You must use the .wim file name extension when specifying the name; otherwise, the operation will fail with an error. 10. Select Upload image to WDS server. 11. Type the name of the Windows Deployment Services server, and then click Connect. 12. If prompted for credentials, provide a user name and password for an account with sufficient permissions to connect to the Windows Deployment Services server. 13. In the Image Group list, select the image group in which you want to store the image. 14. Click Finish.
18
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. This must be the Boot.wim file from the Windows Server 2008 media. 3. Click Create Discover Boot Image. 4. Follow the instructions in the wizard, and when it is completed, 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. Open an elevated Command Prompt window. 2. Type the following command, 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 file where to save the discover image: WDSUTIL /New-DiscoverImage /Image:<bootimage> /Architecture:x86 /Filepath:<discoverimage> 3. If you want to add the discover image back to the image store, type the following command, where <discoverimage> is the file path and file name of the discover image: WDSUTIL /Add-Image /ImageFile:<discoverimage> /ImageType:boot To create media that contains the discover image 1. Download and install the Windows AIK (http://go.microsoft.com/fwlink/? LinkId=81030). 2. Open a Command Prompt window, and then type the following command to switch to the PETools folder: Cd C:\Program Files\Windows AIK\Tools\PETools 3. To create a Windows PE build environment, type: CopyPE <architecture> C:\Winpe 4. To copy the discover image that you created in the preceding procedure, type: Copy /y c:\boot.wim c:\Winpe\ISO\Sources 5. To change back to the PETools folder, type: Cd C:\Program Files\Windows AIK\Tools\PETools 6. To create the bootable .iso image, type: Oscdimg -n -bc:\winpe\ISO\boot\etfsboot.com c:\winpe\ISO c:\winpe.iso 7. Use a utility that can create a CD or DVD to transfer the .iso image to the appropriate media. 19
Note Using the Windows copy command to copy the image to media will not create a bootable disk. 8. Boot the client computer to the media. You may need to change the boot order in the client BIOS to do this. When the client boots to the media, your experience will be exactly the same as if you had booted to the network.
The client computer must have at least 512 MB of RAM, which is the minimum amount of RAM for using Windows PE. The client must meet the system requirements for the operating system of the install image.
20
To associate a client unattend file by architecture, using the Windows interface 1. Create a Unattend.xml file with settings applicable to Windows Deployment Services. For examples, see the Sample Unattend Files topic. 2. Copy the client unattend file to a folder in the RemoteInstall folder. For example: RemoteInstal\WDSClientUnattend. 3. Open the Windows Deployment Services MMC snap-in, right-click the server that contains the Windows Vista or Windows Server 2008 image that you want to associate the unattend file with, and then click Properties. 4. On the Client tab, select Enable unattended installation, browse to the appropriate unattend file, and then click Open. 5. Click OK to close the Properties page. To associate a client unattend file by using the command line 1. Create a Unattend.xml file with settings applicable to Windows Deployment Services. For examples, see the Sample Unattend Files topic. 2. Copy the client unattend file to a folder in the RemoteInstall folder. For example: RemoteInstal\WDSClientUnattend 3. Click Start, right-click Command Prompt, and then click Run as administrator. 4. Do one of the following: To associate the file for an architecture, type the following, where <filepath> is the path name and file name of the client unattend file: WDSUTIL /Set-Server /WDSUnattend /Policy:enabled /File:<filepath> /Architecture:[x86|x64] To associate the file for a computer, type the following, where <relative path>is the path from the C:\RemoteInstall shared folder to the folder that contains the client unattend file: WDSUTIL /Set-Device /Device:<computername> /ID:<GUID or MAC address> /WDSClientUnattend:<relative path>
locate and use the Sysprep.inf file. Save Unattend. xml files. Save Unattend.xml files to any location, and then associate the file with an image. To do this, open the MMC snap-in, right-click the image that you want to associate with the unattend file, and then click Properties. On the General tab, click Allow image to install in unattend mode, click Select File, browse to select the unattend file, and then click OK twice. Note The Unattend.xml file will be saved to the following location: \RemoteInstall\Images\<imagegroup>\<imagename>\Unattend\ImageUnatte nd.xml. To associate an image unattend file at a command prompt 1. Create an Unattend.xml file (for Windows Vista) or Sysprep.inf file (for earlier versions of Windows). For examples, see the Sample Unattend Files topic. 2. The next steps depend on which file you create: Save Sysprep.inf files. Save these files to the $OEM$ structure of the image (for example, D:\RemoteInstall\Images\Windows XP\winxpsp2\$OEM$\ $1\sysprep\sysprep.inf). Now when you deploy the image, Setup will automatically locate and use the Sysprep.inf file. Save Unattend. xml files. Save Unattend.xml files to any location, and then associate the file with an image. To do this, open an elevated Command Prompt window and then type the following command, where <unattendfile> is the path and file name of the unattend file you want to associate with the image: WDSUTIL /Set-Image /Image:<imagename> /ImageType:install /ImageGroup:<imagegroupname> /UnattendFile:<unattendfile> Note The Unattend.xml will be saved to the following location: \RemoteInstall\Images\<imagegroup>\<imagename>\Unattend\ImageUnatte nd.xml.
Routers that support multicasting. In particular, your network infrastructure needs to support the Internet Group Management Protocol (IGMP) to properly forward multicast traffic. Without the IGMP, multicast packets are treated as broadcast packets, which can lead to network flooding. 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).
Internet Group Membership Protocol (IGMP) snooping should be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device in the subnet.
Selecting multicast type There are two types of multicast transmissions: 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, the transmission will not start until you manually start it. Note that in addition to these criteria, you can start a transmission manually at any time by right-clicking it and then 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), data will not be sent over the network. Configuring transmissions After a transmission has been created, you can perform any of the following actions: Start the transmission. If the transmission is the Scheduled-Cast type, there is at least one client, and the transmission has not started yet, you can right-click the transmission and then click Start. 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 transmission. 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 then 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 completed, the transmission will be deleted. If there are no clients when you click this option, the transmission will be deleted instantly. View the transmission's properties. To view the properties, right-click the transmission and then 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 it and then recreate it. 25
Refresh the transmissions and data. To do this, right-click a transmission and then click Refresh. You can also refresh the data by pressing F5. Configuring clients in a transmission After you have created the transmission, client computers can join it by selecting the image in the Windows Deployment Services user interface. Client computers can also join a transmission by using Wdsmcast.exe, a command-line tool included in the Windows AIK. When there are clients in a transmission, you can do any of the following: 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 percentage complete) are shown in the right pane. Stop a client installation. To stop the installation completely, right-click a client and then click Disconnect. You should use this option with caution because the installation will fail and the computer could be left in an unusable state. Disconnect a client from a multicast transmission. To discontinue the transmission for a particular client but continue to transfer the image through unicasting, right-click the client, and then click Bypass multicast.
Using WDSUTIL
Creating a multicast transmission for an install image You have two options for transmission type: Auto-Cast and Scheduled-Cast. You must run all WDSUTIL commands from an elevated Command Prompt window. To create an Auto-Cast transmission Syntax: WDSUTIL /New-MulticastTransmission /Image:<image name> /FriendlyName:<friendly name> /ImageType:Install /ImageGroup:<Image group name> /TransmissionType:AutoCast To create a Scheduled-Cast transmission Syntax: WDSUTIL /New-MulticastTransmission /Image:<image name> /FriendlyName:<friendly name> /ImageType:Install /ImageGroup:<Image group name> /TransmissionType:ScheduledCast [/Time:<yyyy/mm/dd:hh:mm>][/Clients:<no of clients>] Configuring transmissions After a transmission is created, you can start it, delete it, deactivate it, and view its properties. To start the transmission Syntax: WDSUTIL /Start-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> Note You can start the transmission only if it is the Scheduled-Cast type, there is at least one client, and the transmission is not already started. To delete the transmission 26
Syntax: WDSUTIL /Remove-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> /Force To deactivate the transmission Syntax: WDSUTIL /Remove-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> To view the transmission's properties Syntax: WDSUTIL /Get-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> Configuring clients in a transmission After you have created the transmission, client computers can join it by selecting the image in the Windows Deployment Services user interface. Client computers can also join a transmission through Wdsmcast.exe a command-line tool that is included in the Windows AIK. When there are clients in a transmission, you can perform any of the following actions: To view clients and see progress Syntax: WDSUTIL /Get-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> /show:clients To stop a client installation completely Syntax: WDSUTIL /Disconnect-Client /ClientID:<id> /Force. Note You should use this option with caution because the installation will fail and the computer could be left in an unusable state. To disconnect a client from a multicast transmission but continue to transfer the image by using unicasting Syntax: WDSUTIL /Disconnect-Client /ClientID:<id> To view the client <id> for each transmission Syntax: WDSUTIL /Get-MulticastTransmission /Image:<image name> /ImageType:Install /ImageGroup:<image group name> /show:clients
27
Additional references
For detailed documentation for Windows Deployment Services, see http://go.microsoft.com/fwlink/?LinkId=88439. For a newsgroup about Windows Deployment Services, see Setup and Deployment (http://go.microsoft.com/fwlink/?LinkId=87628). See the Windows AIK (http://go.microsoft.com/fwlink/?LinkID=54863). See the Windows AIK documentation (http://go.microsoft.com/fwlink/?LinkId=96016). See the Sysprep Technical Reference (http://go.microsoft.com/fwlink/?LinkId=87732).
For more information about the Windows Deployment Services Update for Windows Server 2003, see the following resources: Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=66145) Deploying and Managing the Windows Deployment Services Update on Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=81031)
28