Windows Deployment Services 2012

Windows Server 2012
Server Roles and Technologies
Windows Deployment Services
What’s New for Windows Deployment Services
Windows Deployment Services Getting Started Guide

Windows Deployment Services Getting Started Guide for Windows Server

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’s 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

Quick start checklist
To get up and running quickly, perform the following steps. Then you can use the instructions in the rest of this guide to perform more advanced tasks such as creating your own install images, creating discover images, or configuring an unattended installation.
 
Task Reference
Install Windows Deployment Services.
Installing Windows Deployment Services
Configure the server and add the default images (Install.wim and Boot.wim) that are included on the installation media (in the \Sources folder).
Configuring Windows Deployment Services
Install an operating system.
Installing an install image
What is Windows Deployment Services?
Windows Deployment Services enables you to deploy Windows operating systems. You can use it to set up new computers by using a network-based installation. This means that you do not have to install each operating system directly from installation media, for example a DVD or USB drive.
What’s new in Windows Deployment Services?
Windows Deployment Services has evolved as each version is released. You can read about the new features and improvements in Windows Deployment Services in What’s New in Windows Deployment Services.
Who should use this guide?
Windows Deployment Services is intended for deployment specialists who are responsible for the deployment of Windows operating systems. This guide assumes that you have a working knowledge of common desktop deployment technologies, as well as networking components such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory Domain Services (AD DS). The target audiences are:
IT planners or analysts evaluating Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012.

Enterprise IT planners or designers.

Deployment specialists interested in deploying images to computers.

Benefits of Windows Deployment Services
Windows Deployment Services provides the following benefits:
Allows network-based installation of Windows operating systems, including Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012. It reduces the complexity and cost when compared to manual installations.

Deploys Windows images to computers without operating systems.

Supports mixed environments that include Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows XP, and Windows Server 2003.

Uses standard Windows Server setup technologies, including Windows PE, .wim files, and image-based setup.

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

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.

The only prerequisite is that you must be a member of the Local Administrators group on the server to install Transport Server.
 
Deployment Server and Transport Server (Standalone mode, no dependency on Active Directory) Transport Server
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.

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.

Credentials. To install the role, you must be a member of the Local Administrators group on the server.

The only prerequisite is that you must be a member of the Local Administrators group on the server to install Transport Server.
Installation Methods
You can install Windows Deployment Services by using Server Manager, or using Windows PowerShell.
To install using Server Manager
In Server Manager, click Manage.
Click Add roles and features.
Select Role-based or feature-based installation and choose the server to deploy WDS.
On the Select server roles page select the Windows Deployment Services check box.
Click Next and follow the wizard to completion.
During installation, on the Select role services page, the wizard presents the option to select role services to be installed in Windows Deployment Services. You can choose to install the Deployment Server and Transport Server, or leave both roles selected.
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. You can also use it if you want to have a PXE server that allows clients to PXE boot and download your own custom setup application. You should use this option if you want to use either of these scenarios , but you do not want to incorporate all of Windows Deployment Services.

Deployment Server. This option provides the full functionality of Windows Deployment Services, which you can use to configure and remotely install Windows operating systems. Note that Deployment Server is dependent on the core parts of Transport Server.

Note
When you install Windows Deployment Services, it will automatically provide the option (selected by default) to install the Remote Server Administration Tools.
You can also add this feature by using the Add Roles and Features Wizard and checking Remote Server Administration Tools on the Select feature page.
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.
In Windows PowerShell, unlike in the Add Roles and Features Wizard, management tools and snap-ins for a role are not included by default. To include management tools as part of a role installation, add the -IncludeManagementTools parameter to the cmdlet. If you are installing roles and features on a server that is running the Server Core installation option of Windows Server 2012, and you add a role’s 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.
To install using Windows PowerShell
Do one of the following to open a Windows PowerShell session with elevated user rights.
On the Windows desktop, right-click Windows PowerShell on the taskbar, and then click Run as Administrator.

On the Windows Start page, type any part of the name Windows PowerShell. Right-click the shortcut for Windows PowerShell when it is displayed on the Start page in the Apps results, click Advanced, and then click Run as Administrator. To pin the Windows PowerShell shortcut to the Start page, right-click the shortcut, and then click Pin to Start.

Type the following, and then press Enter, where computer_name represents a remote computer on which you want to install Hyper-V. To install WDS directly from a console session, do not include -ComputerName in the command.





Install-WindowsFeature –Name WDS -ComputerName -IncludeManagementTools





To view a list of available and installed roles and features on the local server, type Get-WindowsFeature and then press Enter. The results of the cmdlet contain the command namesof 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.





When the installation is finished, verify installation by running Get-WindowsFeature. If you installed WDS remotely, include the ComputerName parameter (Get-WindowsFeature -ComputerName ) 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.





Install Windows Deployment Services





To install the Windows Deployment Services role





Sign in to the server as a member of the local Administrators group.





Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.





Click Manage.





Click Add roles and features, click Next.





On the Before you begin page of the Add Roles and Features Wizard, click Next.





On the Select installation type page, click Role-based or feature-based installation, and then click Next.





On the Select destination server page, select the appropriate server, and then click Next. The local server is selected by default.





On the Select server roles page, scroll down and then select the Windows Deployment Services check box. Click Next.





Remote Server Administration Tools are required to manage this feature. Select Include management tools (if applicable). Click Add Features. Click Next.





On the Select features page, click Next.





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, leavethese role services selected. Click Next.





On the Confirm installation selections page, click Install.





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 addat least one boot image and one install image to the image store.





Note





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 Pre-Installation Environment (Windows PE). See Windows Assessment and Deployment Kit (ADK) for Windows 8 in Additional References.





Configuring Windows Deployment Services





After you install the Windows Deployment Service role, you must configure the server. Once you have used the instructions in this section to configure the server, add a boot image,and an install image, you will be ready to deploy images. Then, you can use the instructions in the rest of this guide to perform more advanced tasks like creating your own install images, creating discover images, or configuring an unattended installation.





Prerequisites for configuring Windows Deployment Services





If Windows Deployment Services is integrated with Active Directory, the server must be a member of an Active Directory Domain Services (AD DS) domain, or a domain controller for anAD DS domain. If Windows Deployment Services is installed in Standalone mode, it can be configured without having a dependency on Active Directory.

There is an active DHCP server on the on Windows Deployment Services uses Pre-Execution Environment (PXE), which relies on DHCP for IP addressing.

There is an active DNS server on the network.

The server has an NTFS file system partition on which to store images.

Steps for configuring Windows Deployment Services for Standalone Server
There are two configuration options for Windows Deployment Services. It can be configured to integrate with Active Directory or be configured as a standalone server.
To configure the server role in Standalone mode, use the following procedure. Then see the following section to add images to the server.
To configure Windows Deployment Services in Standalone mode
Log on to the server as a member of the local Administrators group.
Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
Click Tools, and then click Windows Deployment Services to launch the Windows Deployment Services MMC-snap (or console).
In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.
Right-click the desired server, click Configure Server.
On the Before you begin page, click Next.
On the Install options page, choose Standalone server.
On the Remote Installation Folder Locations page, choose the default path or enter your own path to the remote installation folder. Click Next.
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.
When the configuration is completed clear the Add images to server now check box, and then click Finish.
If you want to modify any of the settings of the server, right-click the server in the MMC-snap 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.
Installing Windows Deployment Services integrated with Active Directory
This section describes installing Windows Deployment Services integrated with Active Directory. You may skip this if you have chosen to install Standalone mode, and proceed to Steps for adding images.
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.
To install Windows Deployment Services integrated with Active Directory, the following prerequisites are required.
 
Deployment Server and Transport Server
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.

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.

The only prerequisite is that you must be a member of the Local Administrators group on the server to install Transport Server.
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.
To configure Windows Deployment Services integrated with Active Directory
Log on to the server as a member of the local Administrators group.
Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
Click Tools, and then click Windows Deployment Services to launch the Windows Deployment Services MMC-snap (or console).
In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.
Right-click the desired server, click Configure Server.
On the Before you begin page, click Next.
On the Install options page, choose Integrated with Active Directory.
On the Remote Installation Folder Locations page, choose the default path or enter your own path to the remote installation folder. Click Next.
If your server is running as a DHCP Server, you will see the Proxy DHCP Server page. Select Do not listen on DHCP and DHCPv6 ports and Configure DHCP options for Proxy DHCP. Click Next.
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.
When the configuration is completed, click Finish.
If you want to modify any of the settings of the server, right-click the server in the MMC-snap in, and click Properties.
Now that you have configured the server integrated with Active Directory, you will need to add your 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 the next section, Steps for adding images.
Steps for adding images
You must add at least one boot image and one install image before you will be able to boot to the Windows Deployment Services server and install an image.
Boot images. Boot images are Windows PE images that you boot a client computer into to perform an operating system installation. In most scenarios, you should use the Boot.wim file from the installation media (in the \Sources folder). The Boot.wim file contains Windows PE and the Windows Deployment Services client.

Install images. Install images are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the installation media (in the \Sources folder), or you can create your own install image by using the steps in Creating custom install images later in this guide.

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
In the left pane of the Windows Deployment Services MMC snap-in, right-click the Boot Images node, and then click Add Boot Image.
Browse to choose the default boot image (Boot.wim) on the Windows installation media, located in the \Sources folder.
Click Open, and then click Next.
On the Image Metadata page, enter the desired image name and description. Click Next.
On the Summary page, click Next.
Repeat this procedure to add any additional boot images.
Installing an install image
After you have at least one boot and one install image on the server, you can deploy an install image.
Prerequisites for installing an install image
The client computer must be capable of performing a PXE boot.

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.

A local user account must be a created on the Windows Deployment Services server.

Steps for installing an install image
To perform a PXE boot on a computer to install an image, use the following procedure.
To install an operating system
Configure the BIOS of the computer to enable PXE booting, and set the boot order so that it is booting from the network first.
Restart the computer, and when prompted, press F12 to start the network boot.
Select the appropriate boot image from the boot menu. (This boot image selection menu will be available only if you have two or more boot images on the server.
At the Install Windows page, choose your Locale and Keyboard or Input Method. Click Next.
At the Connect to Your WDS Server authentication dialog, enter your local user account and password. Click OK.
At the Install Windows dialog box, select the operating system you wish to install. If you only have one operating system to install, choose that and click Next.
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.
When the installation is completed, the computer will restart and Setup will continue.
Boot Image and Install Image Priorities
When you have multiple boot or install images available to client computers, clients will be presented with a boot and an install menu that displays the selection of images to choose from.
Windows Deployment Services in Windows Server 2012 allows you to set priorities to control the order that both boot and install image listings are presented to clients. This ability is integrated directly into Windows Deployment Services.
Steps for configuring the boot menu
To configure menu order for boot images
Open the Windows Deployment Services MMC snap-in.
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.
Right-click your desired boot image from the right-hand side of your Windows Deployment Services MMC snap-in. Click Properties.
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.
Click OK.
To configure menu order for install images
Open the Windows Deployment Services MMC snap-in.
Double-click the Install Images node. You will see your image group (or image groups) appear as a sub menu item. They will also appear in the right hand side of your Windows Deployment Services MMC snap-in.
Click your desired Image Group.
Right-click your desired image within your image group from the right-hand side of your Windows Deployment Services MMC snap-in. Click Properties.
On the Image Properties dialog, in 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.
Click OK.
When you have completed this procedure and you perform a PXE boot on a client computer, a boot or install menu with the menu order you set using priorities will appear. (if those images apply to that computer).
Priorities are pre-populated with a default value that lets you place images higher or lower on the list. The items that appear first on the list are the ones with the lowest value.
Creating custom install images
Optionally, you can create custom install images for Windows 8, Windows 7 and Windows Vista. You can also do this for older operating systems like Windows XP. To do this, use the instructions in this section to create a capture boot image, prepare a reference computer using Sysprep, and then capture the operating system using the Image Capture Wizard.
Note that images that are older than Windows Vista are hardware abstraction layer (HAL)-specific so you cannot deploy an image of one HAL-type to a computer with a different HAL. However, Windows Vista and Windows 7 images are not HAL-specific so you only need one image for each architecture.
Prerequisites for creating custom install images
You must ensure that there is enough disk space to create and store the new images.

You must be a member of the Local Administrators group on the Windows Deployment Services server.

Known issues when creating custom install images
When you boot into the capture image, the Image Capture Wizard will start. Note the following points about this wizard:
You will only see drives that contain operating systems prepared with Sysprep.

If you do not run Sysprep on the computer before you boot into the image, you will not see any drives to capture.

You must enter a local location to save the new install image; otherwise, you will not be able to capture the image. This location can be a mapped network drive but we recommend that you use a local location to avoid image corruption in the event of a network malfunction.
Steps for creating a capture image
To create an install image, you must first create a capture image. Capture images are boot images that you boot a client computer into to capture the operating system into a .wim file. You can also create media (a CD, DVD, USB drive, or other type of media) that contains a capture image, and then boot a computer from the media. These images provide an alternative to the command-line utility, ImageX.exe. Except in advanced scenarios, you can create a capture image by using the Boot.wim file from the Windows installation media.
To create a capture image
In the Windows Deployment Services MMC snap-in, expand the Boot Images node.
Right-click the image to use it as a capture image. In most cases, you can just use the Boot.wim file from the installation media.
Click Create Capture Image.
Type in your Image Name, Image Description, and the location and file name where you want 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. Click Next.
Allow the Create Capture Image Wizard to complete.
Tick Add Image to the Windows Deployment Server now. Click Next
Enter the location of the Windows Image file that contains the images. Click Next.
Enter your Image Name and Image Description. Click Next.
On the Summary page, click Next.
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.
Steps for creating an install image
Now that you have a capture image, you need to prepare a reference computer and then create the install image. The reference computer can be a computer with a standard Windows installation or a Windows installation that has been configured for your environment. First, you boot a computer (which has been prepared with Sysprep) into the capture image. Then a wizard creates an install image of the reference computer and saves it as a .wim file. After that, you can deploy the .wim file to a computer.
To create a custom install image
Create a reference computer (install the operating system, applications, and make any other changes that you want).
Ensure that you have the correct version of Sysprep.exe on the computer.
At a command prompt on the reference computer, change folders to \Windows\System32\Sysprep or the folder that contains Sysprep.exe and Setupcl.exe.
Type one of the following:
On computers running Windows 8, Windows 7, Windows Vista and Windows Server 2012, Windows Server 2008 R2 and Windows Server 2008, run the command sysprep /oobe /generalize /reboot. If you prefer, you can also use the Sysprep graphical user interface by double-clicking Sysprep.exe.

On computers running Windows XP, run sysprep -mini –reseal -reboot.

When the computer restarts, perform a network boot on the computer by pressing F12.
In the boot menu, select the capture boot image that you created in the preceding procedure, and then press ENTER.
You will be presented with the Windows Deployment Services Image Capture Wizard. Click Next.
On the Directory to Capture page, select Volume to capture, enter your Image name and Image description. Click Next.
Important
Referring to Volume to capture, you will see only drive

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s