20411B-ENU-TrainerHandbook
.pdf
|
|
|
Administering Windows Server® 2012 1-9 |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Server component |
Deployment server |
Transport server |
|
MCT |
||
|
|
|
|
|
|
|
|
|
Management |
Both the WDSutil.exe command-line |
WDSutil.exe only |
|
|
|
|
|
|
tools and the Windows Deployment |
|
|
|
|
|
|
|
Services Microsoft® Management |
|
|
|
|
|
|
|
Console (MMC) snap-in |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Target computer |
Uses Windows Deployment Services |
Wdsmcast.exe only |
USE |
|||
|
|
client or the Wdsmcast.exe tool |
|
||||
|
|
|
|
|
|
|
|
Transport Server Functionality
You can use the Transport Server to provide the following functions:
• Boot from the network. The Transport Server provides only a PXE listener; this is the component that
listens and accepts incoming traffic. You must write a custom PXE provider to use a Transport Server |
|
to boot a computer from the network. |
|
• Multicasting. The multicast server in Windows Deployment Services consists of a multicast provider.ONLY |
|
and a content provider: |
STUDENT |
o Multicast provider. Transmits data over the network. |
|
|
|
o Content provider. Interprets the data and passes it to the multicast provider. This is installed with both the Transport Servers and Deployment Server, and can be used to transfer any file type, although it has specific knowledge about the .wim image file format.
•AD DS. Your Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain.
NTFS file system volume. The server running Windows Deployment Services requires an NTFS volumeUSEPROHIBITED for the image store. Windows Deployment Services accesses the image store within the context of the
logged on user. Therefore, deployment user accounts must have sufficient permissions on image files.
1-10 Deploying and Maintaining Server Images |
MCT |
|||
|
|
|
||
|
|
|
|
|
Installing and Configuring Windows Deployment Services |
|
|
|
|
Once your network infrastructure meets the |
|
|
USE |
|
|
|
|||
prerequisites, you can install the Windows |
|
|
||
Deployment Services server role. |
|
|
||
|
|
|
|
|
Installing the Windows Deployment |
|
|
|
|
Services Server Role |
|
|
|
|
Use the following high-level steps to provide |
|
|
.ONLY |
|
guidance on installing the role. |
|
|
||
|
|
|
|
|
1. Open Server Manager, and then add the |
|
|
|
|
Windows Deployment Services server role. |
|
|
|
|
2. Choose whether you want to install the |
|
|
|
|
|
|
|
|
|
Deployment Server role service (which |
|
|
|
|
includes the Transport Server role), or just the Transport Server role service. |
|
|
|
|
3. Complete the wizard to install the required role. |
|
|
|
|
1.Select your server in Windows Deployment Services the console, and launch the Configuration wizard.STUDENT
2.Specify a location to store images. This location: o Must be an NTFS partition.
o Must be large enough to accommodate the deployment images that you anticipate needing.
o Should be a separate physical disk from that on which the operating system is installed to help optimize performance.
3.If the DHCP server role is co-hosted on the Windows Deployment Services server, you must:
o Prevent the PXE server from listening on User Datagram Protocol (UDP) port 67; this port is used USE by DHCP.
o Configure DHCP option 60 to PXEClient; this enables the PXE client to locate the Windows Deployment Services server port.
Note: If you deploy Windows Deployment Services to a server that is already running the DHCP Server role, these changes are made automatically. If you subsequently add the DHCP Server role to a Windows Deployment Server, you must ensure that you make these changes.
4.Determine how you want the PXE server to respond to clients:
o The default is that the PXE server does not respond to any clients; this is useful when you are initially configuring Windows Deployment Services, as you do not yet have any images available for clients.
o Alternatively, you can choose to configure the PXE server to:
Respond to known client computers; these are computers that you have prestaged.
Respond to all client computers, whether you have prestaged them or not; if you select this option, you can additionally define that administrator approval is required for unknown computers. While awaiting approval, client computers are held in a pending queue.
PROHIBITED
|
|
|
Administering Windows Server® 2012 |
MCT |
||
|
|
|
1-11 |
|
||
|
|
Note: If necessary, you can reconfigure these settings after the initial configuration is |
|
|
||
|
|
|
|
|||
complete. |
USE |
|||||
Managing Deployments with Windows Deployment Services |
||||||
|
|
|||||
Once you install and configure Windows |
|
|
|
|||
|
|
|
||||
Deployment Services, you can then prepare |
.ONLY |
|||||
Windows Deployment Services to service client |
||||||
deployments; this involves the following |
||||||
procedures. |
||||||
Configuring Boot Settings |
||||||
You must complete several configuration tasks |
||||||
to configure boot settings on the server that is |
||||||
hosting Windows Deployment Services. |
||||||
•Add boot images. A boot image is a Windows
PE image that you use to boot a computer STUDENT and install the install image. Typically, you use the boot.wim file on the Windows Server 2012 product
DVD in the \sources folder. You may also decide to create a capture image, which is a specific type of boot image that you can use to capture a currently installed operating system on a reference computer.
•Configure the PXE boot policy for known and unknown clients. This policy determines the required installer behavior during the initial part of the deployment. By default, both known and unknown computer policies require the installer to press F12 to connect to the Windows Deployment Services image server. Failure to do so results in the computer using BIOS settings to determine an alternative boot method—for example, hard disk or CD ROM. Instead of this default, you can configure the following options:
o Always continue the PXE boot. This option ensures that the computer continues through the deployment process without any installer interaction. USE
o Continue the PXE boot unless the user pressed the Esc key. This option gives the installer the ability to cancel the deployment.
•Configure a default boot image. If you have multiple boot images—for example, to support multiple platforms—you can configure a default boot image for each of them. This image is selected after a
•timeout period on the PXE client computer. PROHIBITED Associate an answer file for setup. You can define an associated answer file for each client
architecture. This answer file provides information that is used during the initial setup phase, and enables the Windows Deployment Services image server to select the appropriate install image for the client, without installer intervention.
•Create discover images. Not all computers support PXE network boot. For those that do not, you can create a discover image based on a boot image and export it to a removable storage device. To create a discover image, specify:
o The image name and description.
o The boot image on which it is based.
o A filename with which to store the image.
o The name of the Windows Deployment Services server that will be used for deployment.
1-12 Deploying and Maintaining Server Images
Configuring Install Settings
You must configure additional install settings in Windows Deployment Services.
•Add install images. This is the operating system image that you use to install Windows Server. Typically, you start with the installation image install.wim, in the \sources folder on the Windows Server 2012 product DVD. Thereafter, you might choose to create custom images for groups of computers that have similar configurations.
USE MCT
Note: Before you can create install images, you must define an install image group in
•Associate an answer file with an install image. If you have created an answer file, for example by usingONLY Windows ADK, you can associate it with an install to provide the necessary information to complete deployment of the computer with no installer interaction.
•Configure a client naming policy. You can use the client naming policy to define computer names for. unknown computers during deployment. The policy uses a number of variables to create a unique STUDENT name:
a.%First. The installer’s first name. Placing a number after the % sign results in using only that many characters. For example, %3First uses the first three characters of the installer’s first name.
b.%Last. The installer’s last name. You can also define the number of characters to use.
c.%Username. The installer’s user name. Again, you can limit the number of characters by specifying a number after the % sign.
d.%MAC. The Media Access Control (MAC) address.
e.%[n]#. You can use this sequence to define a unique identifying sequential number to the computer name containing n digits. If you want to use a multiple-digit number, pad the variable
with leading zeros, after the % sign. For example, %2# results in the sequential numbers 1, 2, 3,
and so on. %02# results in 01, 02, and 03. USE
•Specify the AD DS location for computer accounts. The default is to use the same AD DS domain as the Windows Deployment Services server. Alternatively, you can select between:
oThe same domain as the user performing the deployment.
o The same organizational unit (OU) as the user who is performing the deployment. o A specified AD DS location.
Note: The Windows Deployment Services computer requires Create Computer object and Write All Properties permissions on the AD DS container that you specify.
PROHIBITED
Administering Windows Server® 2012 1-13
Configuring Transmission Settings |
|
|
Configure multicast transmissions. Unicast transmission is enabled by default; that is, you need do nothing |
||
further and you can deploy clients using unicast. However, to enable multicast transmission, specify: |
MCT |
|
USE |
||
• The multicast transmission name. |
||
• An install image with which the transmission is associated. |
||
• A method of multicast transmission. Choose between Autocast and Scheduled-Cast. If you choose |
||
Scheduled-Cast, you can define both a threshold minimum number of clients before transmission |
||
|
||
starts and the start date and time. |
|
|
Configuring Drivers
Windows Deployment Services in Windows Server 2012 enables you to add and configure driver packages |
|
on the server, and then deploy them to client computers during installations based on their hardware. |
|
Use the following high-level steps to configure drivers: |
|
1. |
Obtain the drivers that you need. These must be in the form of an .inf file rather than an .msi or .exe.ONLY |
|
file. |
2. |
Configure filters, if desired, on the driver group. These filters determine which computers receive the |
|
PROHIBITEDUSESTUDENT |
|
drivers based on the hardware characteristics of the client computers. For example, you can create a |
|
filter that applies the drivers only to computers that have a BIOS manufactured by A. Datum. |
3. |
Add the drivers as a driver package. Driver packages must be associated with a driver group. If you |
|
associate the driver package with an unfiltered group, all computers receive the driver. |
1-14 Deploying and Maintaining Server Images
Lesson 3
Administering Windows Deployment Services
When you have completed the configuration of Windows Deployment Services, you must create and administer boot images, install images, and optionally capture and discover images. In addition, you must make these images available to client computers with the desired level of automation, using an appropriate transmission mechanism.
Lesson Objectives
After completing this lesson, you will be able to:
•Describe the common administration tasks.
•Explain how to add and configure boot, capture, discover, and install images.
•Explain how to automate deployments.
•Explain how to configure multicast transmission to deploy your images.
Common Administration Tasks
To configure Windows Deployment Services effectively, you must complete a number of common administration tasks. To help you complete these tasks, Windows Deployment Services provides a number of tools to help you. The administrative tasks that you must complete include the following:
•Configuring DHCP
•Creating and servicing images
•Managing the boot menu
•Prestaging client computers
•Automating deployment
•Configuring transmission
Configuring DHCP
Clients that boot using PXE require a dynamically allocated IPv4 configuration. You must create and configure an appropriate DHCP scope for this purpose. Additionally, if the DHCP and Windows
Deployment Services server roles are co-hosted, then you must configure how the PXE server listens for client requests; there is an inherent conflict as both DHCP and Windows Deployment Services use UDP port 67. To create and manage DHCP scopes, you can use the DHCP snap-in or the Netsh.exe commandline tool.
Creating and Servicing Images
You can create and service images with the Windows Deployment Services snap-in, Windows SIM, the WDSutil.exe command-line tool, or the Dism.exe command-line tool.
For example, to add a boot image, use the following command:
WDSUTIL /Verbose /Progress /Add-Image /ImageFile:<path> /ImageType:Boot
PROHIBITED USE STUDENT .ONLY USE MCT
|
Administering Windows Server® 2012 |
|
MCT |
||
|
1-15 |
|
|
||
|
To create a capture image, use the following command: |
|
|
|
|
|
|
|
|
|
|
|
WDSUTIL /New-CaptureImage /Image:<source boot image name> /Architecture:{x86|ia64|x64} |
|
|
|
|
|
/DestinationImage /FilePath:<file path> |
|
|
|
|
|
|
|
|
|
|
|
To add an install image, use the following two commands, pressing Enter after each line: |
|
USE |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
WDSUTIL /Add-ImageGroup /ImageGroup:<image group name> |
|
|
|
|
|
WDSUTIL /Verbose /Progress /Add-Image /ImageFile:<path to .wim file> /ImageType:Install |
|
|
|
|
|
|
|
|
|
|
|
|
|
.ONLY |
||
Note: You can also perform these management tasks using the Windows Deployment Service management console, found in Server Manager.
Managing the Boot Menu
The boot environment for Windows Server 2012 relies on the Boot Configuration Data (BCD) store. This store defines how the boot menu is configured. You can customize the store using Bcdedit.exe.
•Screen size. Only 13 images can be displayed on the menu. If you have more, the installer must scrollSTUDENT down to see them.
•Mouse. There is no mouse pointer.
•Keyboard. There is no support for alternate keyboards, other than what the BIOS supports.
•Localization. There is limited support for localization, other than what the BIOS supports. USE
•Accessibility. There is limited support for accessibility.
Windows Deployment Services supports deployment to unknown clients. You can exert some control over unknown clients by configuring administrator approval. This ensures that clients that are attempting to deploy with Windows Deployment Services are placed in a pending queue awaiting your approval. You can also configure the client computer’s name during approval.
However, if you want more specific control over deployments, you can prestage the computers in AD DS; this enables you to configure the client to:
• |
Start from a different Windows Deployment Services server. |
PROHIBITED |
|
||
• |
Use a different network boot program. |
|
1-16 Deploying and Maintaining Server Images
• Use a specific unattend file. |
MCT |
|
• Use a specific boot image. |
||
• Join a particular AD DS domain. |
USE |
|
You can use the following WDSutil.exe command-line tool to prestage computers: |
||
|
||
|
|
|
WDSUTIL /Add-Device /Device:<name> /ID:<GUIDorMACAddress> |
|
|
|
|
|
In this example, <GUIDorMACAddress> is the identifier of the new computer. |
.ONLY |
|
Automating Deployment |
||
|
||
You can automate Windows Deployment Services deployments from end-to-end. You can use the |
|
|
Windows Deployment Services snap-in and Windows SIM to complete these tasks. |
|
|
Configuring Transmission |
|
|
Multicasting enables you to deploy an image to a large number of client computers without consuming |
|
|
excessive network bandwidth. |
|
|
Consider enabling multicast transmissions if your organization: |
|
•Anticipates many concurrent deployments.
•Has routers that support the propagation of multicasts; that is support for the Internet Group Management Protocol (IGMP).
You can use the Windows Deployment Services snap-in or the WDSutil.exe command-line tool to manage multicast transmission. For example, to create a multicast transmission with Autocast, use the following command:
|
WDSUTIL /New-MulticastTransmission /Image:<image name> /FriendlyName:<friendly name> |
STUDENT |
|
|
/ImageType:Install /ImageGroup:<Image group name> /TransmissionType:AutoCast |
||
|
|
||
To create a Scheduled-Cast transmission, use the following command: |
|||
USE |
|||
|
|
||
|
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>] |
||
|
|
||
|
|
||
Demonstration: How to Administer Images |
PROHIBITED |
||
This demonstration shows how to administer images. In this demonstration, this process will be broken |
|||
down into the following four steps: |
|||
• Install and configure the Windows Deployment Services role. |
|||
• |
Add a boot image. |
||
|
|||
• Create a capture image.
• Add an install image.
Administering Windows Server® 2012
Demonstration Steps
Install and configure the Windows Deployment Services role
1.Switch to the LON-SVR1 computer.
2.Open Server Manager.
3.Install the Windows Deployment Services server role with both role services.
4.In the Windows Deployment Services console, right-click LON-SVR1.Adatum.com, and then click
Configure Server.
5.Use the following information to complete configuration:
o Integrate Windows Deployment Services with Active Directory.
o On the Remote Installation Folder Location page, accept the defaults. o Accept the System Volume Warning message.
oOn the PXE Server Initial Settings page, select the Respond to all (known and unknown) client computers option.
o When prompted, choose to not add images to the server.
Add a boot image
1.Switch to LON-SVR1.
2.If necessary, open the Windows Deployment Services console.
3.Add a new boot image using the following information to complete the process:
a.On the Image File page, use the file name: D:\sources\boot.wim.
b.Accept the defaults on the Image Metadata page.
c.Accept the defaults on the Summary page.
4.On the Task Progress page, click Finish.
1-MCT17 USEONLY
STUDENT .
1.If necessary, open Windows Deployment Services. USE
2.Add a new Image Group with the image group name of Windows Server 2012.
3.Use the Add Image Wizard to add a new install image to this group. Use the following information to complete the process: PROHIBITED
a.On the Image File page, use the following file name: D:\sources\install.wim.
b.On the Available Images page, clear all check boxes except Windows Server 2012 SERVERSTANDARDCORE.
c.Accept the defaults on the Summary page.
d.On the Task Progress page, click Finish.
4.Minimize the Windows Deployment Services window.
1-18 Deploying and Maintaining Server Images
Automating Deployments
There are four phases that you can automate during the Windows Deployment Services deployment process. These are:
•PXE Boot Policy. You can determine how the PXE server responds to clients, and whether the installer is required to press the F12 key to connect to the Windows Deployment Services server and select a boot image. For example, the Always continue the PXE boot option ensures that the computer continues through the deployment process without any installer interaction.
•The default boot image. If you configure a default boot image, the installer will not be prompted to make a selection.
•The Windows Deployment Services screens. When the client computer uses the TFTP protocol to connect to the Windows Deployment Services server and select a boot image, the installer must then provide credentials and select an operating system image to install. You can create an Unattend.xml answer file to automate this phase.
•Windows Setup. You can customize the setup program so that once the install image has been selected (either automatically or manually), the setup program will complete the installation process with no installer intervention. This is the same type of automation that you use to automate installations with the Windows ADKADK.
Use Windows SIM to create both types of answer files, and then use the Windows Deployment Services snap-in to associate the answer files with the required deployment phase.
Automate Client Unattend
Use the following procedure to associate an answer file for the client unattend deployment phase:
1.Create the Unattend.xml file in Windows ADK with settings appropriate to Windows Deployment Services.
2.Copy the file to the Windows Deployment Services server, and paste it into a folder under
\RemoteInstall.
3.Open Windows Deployment Services.
4.View the Properties dialog box for the Windows Deployment Services server in the Windows Deployment Services console.
5.On the Client tab, enable unattended installation, and then select the answer file that you created earlier.
PROHIBITED USE STUDENT .ONLY USE MCT