Escolar Documentos
Profissional Documentos
Cultura Documentos
Windows Deployment Services Getting Started Guide for Windows Server 2012
Updated: August 28, 2012 Applies To: Windows Server 2012 This guide contains step-by-step guidance for how to use the Windows Deployment Services role in Windows Server 2012. This guide focuses on the functionality of the complete installation of Windows Deployment Services.
In this guide
Contents In this guide What is Windows Deployment Services? What is Windows Deployment Services? Whats new in Windows Deployment Services? Who should use this guide? Benefits of Windows Deployment Services Installing Windows Deployment Services Configuring Windows Deployment Services Installing Windows Deployment Services integrated with Active Directory Steps for adding images Creating custom install images Creating discover images Performing an unattended installation Creating a multicast transmission Additional References
1/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Reference Installing Windows Deployment Services Configuring Windows Deployment Services Installing an install image
Configure the server and add the default images (Install.wim and Boot.wim) that are included on the installation media (in the \Sources folder).
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Installing Windows Deployment Services Prerequisites for installing Windows Deployment Services
The following are requirements for installing this role, depending on whether you choose the default installation (both Deployment Server and Transport Server), or only the Transport Server role service.
Deployment Server and Transport Server (integrated with Active Directory) AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services.
Transport Server
DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment The only prerequisite is that Services uses PXE, which relies on DHCP for IP addressing. you must be a member of the Local Administrators group on DNS. You must have a working DNS server on the network the server to install Transport before you can run Windows Deployment Services. Server. 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.
Deployment Server and Transport Server (Standalone mode, no dependency on Active Directory) NTFS volume. The server running Windows Deployment Services requires an NTFS file system volume for the image store. DNS. You must have a working DNS server on the network before you can run Windows Deployment Services.
Transport Server
The only prerequisite is that you must be a member of the Local Administrators DHCP. You must have a working DHCP server with group on the server to install Transport an active scope on the network because Windows Server.
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx 3/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Deployment Services uses PXE, which relies on DHCP for IP addressing. Credentials. To install the role, you must be a member of the Local Administrators group on the server.
Installation Methods
You can install Windows Deployment Services by using Server Manager, or using Windows PowerShell.
Windows PowerShell equivalent commands The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx
12/30/12
In Windows PowerShell, unlike in the Add Roles and Features Wizard, management tools and snapins for a role are not included by default. To include management tools as part of a role installation, add the - n l d M n g m n T o s parameter to the cmdlet. If you are installing roles Icueaaeetol and features on a server that is running the Server Core installation option of Windows Server 2012, and you add a roles management tools to an installation, you are prompted to change the installation option to a minimal-shell option that allows the management tools to run. Otherwise, management tools and snap-ins cannot be installed on servers that are running the Server Core installation option of Windows Server.
IsalWnosetr aeWS-optrae<optrnm>-nldMngmnTo ntl-idwFaue Nm D CmueNm cmue_ae Icueaaeetol s 3. To view a list of available and installed roles and features on the local server, type GetWindowsFeature and then press Enter. The results of the cmdlet contain the command names of roles and features that have been added to this computer. Note In Windows PowerShell 3.0, there is no need to import the Server Manager cmdlet module into the Windows PowerShell session before running cmdlets that are part of the module. A module is automatically imported the first time you run a cmdlet that is part of the module. Also, Windows PowerShell cmdlets are not case-sensitive.
4. When the installation is finished, verify installation by running G t W n o s e t r . If you e-idwFaue installed WDS remotely, include the ComputerName parameter (Get-WindowsFeature ComputerName <computer_name>) to view a list of roles and features that are installed on the server. Note This will install both the Deployment Server and the Transport Server roles. The previous command line tool, Servermanagercmd.exe, is deprecated in Windows Server 2012. It is recommended that you use the Windows PowerShell cmdlets.
5/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Install Windows Deployment Services To install the Windows Deployment Services role
1. Sign in to the server as a member of the local Administrators group. 2. Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager. 3. Click Manage. 4. Click Add roles and features, click Next. 5. On the Before you begin page of the Add Roles and Features Wizard, click Next. 6. On the Select installation type page, click Role-based or feature-based installation, and then click Next. 7. On the Select destination server page, select the appropriate server, and then click Next. The local server is selected by default. 8. On the Select server roles page, scroll down and then select the Windows Deployment Services check box. Click Next. 9. Remote Server Administration Tools are required to manage this feature. Select Include management tools (if applicable). Click Add Features. Click Next. 10. On the Select features page, click Next. 11. On the Select role services page, select the role services to install for Windows Deployment Services. If you wish to install both the Deployment Server and Transport Server, leave these role services selected. Click Next. 12. On the Confirm installation selections page, click Install. 13. Windows Deployment Services will now be added to the server. Installation progress will now be illustrated in the Add Roles and Features Wizard. Note For an Active Directory integrated installation, the Deployment Server requires that Active Directory Domain Services, DHCP, and DNS services are available on your network. Transport Server does not require any additional roles or services. Both of these services require an NTFS partition for the file store.
Note Before you begin, you need to configure Windows Deployment Services by running either the Windows Deployment Services Configuration Wizard or WDSUtil.exe. You will also need to add at least one boot image and one install image to the image store.
Note
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx 6/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
To install Windows operating systems from a Windows Deployment Services server, either the client computers must be PXE-enabled, or you must use the latest version of the Windows PreInstallation Environment (Windows PE). See Windows Assessment and Deployment Kit (ADK) for Windows 8 in Additional References.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
9. On the PXE Server Initial Settings page, choose desired option to define which client computers this server will respond to. Click Next. This will complete the configuration of Windows Deployment Services. 10. When the configuration is completed clear the Add images to server now check box, and then click Finish. 11. If you want to modify any of the settings of the server, right-click the server in the MMCsnap in, and click Properties. Now that you have configured the server, you will need to add images. These images include a boot image (which is the bootable environment that you initially boot the computer into, and the install images (which are the actual images that you deploy). For instructions, see Steps for adding images.
Deployment Server and Transport Server AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services.
Transport Server
DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment The only prerequisite is that Services uses PXE, which relies on DHCP for IP addressing. you must be a member of the Local Administrators group on DNS. You must have a working DNS server on the network the server to install Transport before you can run Windows Deployment Services. Server. 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.
8/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Steps for configuring Windows Deployment Services integrated with Active Directory
To configure the Windows Deployment Services server role integrated with Active Directory, use the following procedure.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
The following instructions use Windows 7 installation media as an example for creating an install image that can be deployed with Windows Deployment Services. You can also use the same instructions for server installation media. To add the default images, use the following procedures.
To add the default boot image included on the product installation media
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 installation media, located in the \Sources folder. 3. Click Open, and then click Next. 4. On the Image Metadata page, enter the desired image name and description. Click Next. 5. On the Summary page, click Next. Repeat this procedure to add any additional boot images.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
only have one operating system to install, choose that and click Next. 7. If prompted at the Where do you want to install Windows page, select the partition you wish to install the operating system on. Click Next. 8. When the installation is completed, the computer will restart and Setup will continue.
Steps for configuring the boot menu To configure menu order for boot images
1. Open the Windows Deployment Services MMC snap-in. 2. Click the Boot Images node. You will see your boot images appear in the right hand side of your Windows Deployment Services MMC snap-in. 3. Right-click your desired boot image from the right-hand side of your Windows Deployment Services MMC snap-in. Click Properties. 4. In the Image Properties dialog, on the General tab, enter in your desired priority into the Priority text box. The items that appear first on your install image menu are the ones with the lowest value. 5. Click OK.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
7. Enter the location of the Windows Image file that contains the images. Click Next. 8. Enter your Image Name and Image Description. Click Next. 9. On the Summary page, click Next. 10. Click Finish. After you have created the capture image, follow the instructions in the next section to boot a computer into the capture image and capture the operating system.
13/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
9. Click Browse next to Name and location and browse to a local folder where you want to store the captured install image. Type a name for the image, using the .wim file name extension, and then click Save. Note that this location can be a mapped network drive. 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.
10. Select the Upload Image to a Windows Deployment Services check box. 11. Click Connect. If prompted for credentials, provide a user name and password for an account with permissions to connect to the Windows Deployment Services server. 12. Select your Image Group Name. Click Next. The wizard will now complete and create a custom installation image and store it in the Windows Deployment Services store. 13. Click Finish. When this process is complete, you can PXE boot a client computer to install this image. The image will be listed in the installation option.
14/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
3. Click Create Discover Image. 4. In the Metadata and Locations page, enter your Image Name and Image Description. In the location and file name, click Browse and select the location for storing your discover boot image. Enter the name of your discover image. Optionally, enter the name of your Windows Deployment Services server that you want to respond when you boot a computer into this image. Click Next. 5. Click Finish. Use the following procedure to create media that contains the image. This following example details how to create media that contains a discovery image. However, it is an example only; you can substitute any values you require. For example, different architecture and folder names and locations.
CpP x6 oyE 8
c\YiPFle. :MWnEodr
5. To copy the discover image that you created in the preceding procedure, type:
cp / c\icvrwmC\YiPFle\ei\ore oy y :dsoe.i :MWnEodrmdasucs 6. To change back to the Windows PE tools folder, type:
c C\rga Fls(8)WnosKt\.\sesetadDpomn KtDpomn T d :Porm ie x6\idw is80Assmn n elyet i\elyet ol\8\sdm osx6Ocig 7. To create the bootable .iso image, type:
ocig-":PormFls(8)WnosKt\.\sesetadDpomn KtDp sdm nC\rga ie x6\idw is80Assmn n elyet i\el omn Tosx6Ocigetbo.o"C\YiPFle\ei\ore c\icvrio yet ol\8\sdm\fsotcm :MWnEodrmdasucs :dsoe.s 8. Use a utility that can create a CD or DVD to transfer the .iso image to the appropriate media. Note Using the Windows copy command to copy the image to media will not create a
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx 15/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
bootable disk.
9. 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.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
the Windows 8, Windows 7, Windows Vista, Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012 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.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
options for creating a transmission: Right-click the Multicast Transmission node, and then click Create Multicast Transmission. Right-click an image, and then click Create Multicast Transmission. 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.
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
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.
Additional References Understanding the Windows Assessment and Deployment Kit (ADK) for Windows 8
Download the Windows Assessment and Deployment Kit for Windows 85. Features available in the Windows Assessment and Deployment Kit (ADK) include: Application Compatibility Toolkit (ACT) The Application Compatibility Toolkit (ACT) helps IT Professionals understand potential application compatibility issues by identifying which applications are or are not compatible with the new versions of the Windows operating system. ACT helps to lower costs for application compatibility evaluation by providing an accurate inventory of the applications in your organization. ACT helps you to deploy Windows more quickly by helping to prioritize, test, and detect compatibility issues with your apps. By using ACT, you can become involved in the ACT Community and share your risk assessment with other ACT users. You can also test your web applications and web sites for compatibility with new releases of Internet Explorer. For more information, see Application Compatibility Toolkit 6. Deployment Tools Deployment tools enable you to customize, manage, and deploy Windows images. Deployment tools can be used to automate Windows deployments, removing the need for user interaction during Windows setup. Tools included with this feature are Deployment Imaging Servicing and Management (DISM) command line tool, DISM PowerShell cmdlets, DISM API, Windows System Image Manager (Windows SIM), and OSCDIMG. For more information, see Deployment and Imaging Tools Technical Reference7. User State Migration Tool (USMT) USMT is a scriptable command line tool that IT Professionals can use to migrate user data from a previous Windows installation to a new Windows installation. By using USMT, you can create a customized migration framework that copies the user data you select and excludes any data that does not need to be migrated. Tools included with the feature are ScanState, Loadstate, and USMTUtils command line tools. For more information, see User State Migration Tool Technical Reference8. Volume Activation Management Tool (VAMT) The Volume Activation Management Tool (VAMT) enables IT professionals to automate and centrally manage the activation of Windows, Windows Server, Windows ThinPC, Windows POSReady 7, select add-on product keys, and Office for computers in their organization. VAMT can manage volume activation using retail keys (or single activation keys), multiple activation keys (MAKs), or Windows Key Management Service (KMS) keys. For more information, see Volume Activation Management Tool Technical Reference9. Windows Performance Toolkit (WPT)
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx 19/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
Windows Performance Toolkit includes tools to record system events and analyze performance data in a graphical user interface. Tools available in this toolkit include Windows Performance Recorder, Windows Performance Analyzer, and Xperf. Windows Assessment Toolkit Tools to discover and run assessments on a single computer. Assessments are tasks that simulate user activity and examine the state of the computer. Assessments produce metrics for various aspects of the system, and provide recommendations for making improvements. Windows Assessment Services Tools to remotely manage settings, computers, images, and assessments in a lab environment where Windows Assessment Services is installed. This application can run on any computer with access to the server that is running Windows Assessment Services. Windows Preinstallation Environment (Windows PE) Minimal operating system designed to prepare a computer for installation and servicing of Windows.
Links Table
1http://technet.microsoft.com/en-us/library/hh974416 2http://www.microsoft.com/download/details.aspx?id=29929 3http://go.microsoft.com/fwlink/?LinkId=115301 4http://go.microsoft.com/fwlink/?LinkID=115298 5http://www.microsoft.com/en-us/download/details.aspx?id=29929 6http://msdn.microsoft.com/library/windows/desktop/dd562082(v=vs.85).aspx 7http://go.microsoft.com/fwlink/?LinkId=214548 8http://go.microsoft.com/fwlink/?LinkId=214547 9http://go.microsoft.com/fwlink/?LinkId=214550
Community Content
10/27/2012
technet.microsof t.com/en-us/library /jj648426(d=printer).aspx
10/27/2012
20/21
Windows Deploy ment Serv ices Getting Started Guide f or Windows Serv er 2012 12/30/12
MorisM
MorisM
Is this an error?
Can someone please check the info about copying the discover image to the PE image folder.... It says to copy the discover image AS IS to the media\sources folder. Shouldn't it overwrite the boot.wim that already resides there?
Also, the path seems to be wrong. Shouldn't the entire media folder be included in the ISO?
Someone seriously needs to proof-read these steps. These same mistakes seems like they've been copied and pasted from the Windows Server 2008 info.
21/21