MCSA Guide to Administering Microsoft Windows Server 2012/R2, Exam 70-411

Chapter 1 Deploying Windows Server Objectives

• Describe the Windows Deployment Services process • Describe situations in which Windows Deployment Services is used • Install and configure the Windows Deployment Services role • Work with Windows Deployment Services images • Configure DHCP for Windows Deployment Services

MCSA Guide to Administering Microsoft Windows Server 2012/R2, 2 © Cengage Learning 2015 Exam 70-411 An Overview of Windows Deployment Services • Windows Deployment Services (WDS) - a server role that facilitates installing Windows OSs across a network – Configure many OS properties before deployment • Preboot eXecution Environment (PXE) - allows a computer to boot from an image stored on a network server rather than local storage • Image file - in WDS an image file is either a boot image or an install image – A boot image allows a client to access a WDS server to access an install image MCSA Guide to Administering Microsoft Windows Server 3 © Cengage Learning 2015 2012/R2, Exam 70-411 An Overview of Windows Deployment Services • Install image - contains the actual OS being deployed to the client computer • Discover image - can be used to boot a client computer that can’t use PXE • Capture image - a special boot image that creates an install image from a reference computer • Windows Imaging Format (WIM) files - most common image file type used by WDS – WIM files have the .wim extension

MCSA Guide to Administering Microsoft Windows Server 4 © Cengage Learning 2015 2012/R2, Exam 70-411 An Overview of Windows Deployment Services • Windows Preinstallation Environment (PE) - a minimal OS that has only the services needed to access the network, work with files, copy disk images, and jump-start a Windows installation • Multicasting - method for delivering data to multiple computers on a network simultaneously • Network book - boot from the network rather than local storage • wdsnbp.com - a bootstrap program that a WDS client downloads when performing a network boot

MCSA Guide to Administering Microsoft Windows Server 5 © Cengage Learning 2015 2012/R2, Exam 70-411 The WDS Process

MCSA Guide to Administering Microsoft Windows Server 6 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Requirements

• WDS requires several support technologies: – Windows Server 2012/R2 – Active Directory – DHCP Server – DNS Server – PXE-compatible NICs – Suitable storage

MCSA Guide to Administering Microsoft Windows Server 7 © Cengage Learning 2015 2012/R2, Exam 70-411 Windows Deployment Services Situations • WDS has many different implementation options: – Configure OS deployments that require user interaction – Configure OS deployments that are unattended installations – Install just the base OS – Install an OS that has applications installed • Following sections examine several situations in more detail

MCSA Guide to Administering Microsoft Windows Server 8 © Cengage Learning 2015 2012/R2, Exam 70-411 Attended Deployment of a Noncustomized Install Image • The simplest WDS implementation requires a user to attend the client computer – Advantage: do not need installation media • This type of deployment is suitable for installing an OS on 10 to 25 computers • The following images can be used straight from the Windows 8.1 DVD: – \sources\boot.wim – \sources\install.wim • Someone must attend the installation and respond to prompts MCSA Guide to Administering Microsoft Windows Server 9 © Cengage Learning 2015 2012/R2, Exam 70-411 Attended Deployment of a Customized Install Image • By creating a custom image, you can install applications and perform other configuration tasks on the OS before you deploy it • Reference computer - the one that has been configured with the OS and applications – Used to create an install image that can be deployed to other computers by using WDS • Reasonable for deploying up to 10 to 15 computers

MCSA Guide to Administering Microsoft Windows Server 10 © Cengage Learning 2015 2012/R2, Exam 70-411 Unattended Deployment of a Customized Install Image • Recommended when installing Windows on 15 or more computers • Requirement to do unattended installations: – An answer file which contains responses to the prompts and questions Windows asks during an OS installation • The answer file can be created with a text or XML editor – Preferred method is the System Image Manager (SIM) available as a free download from the Microsoft Download Center

MCSA Guide to Administering Microsoft Windows Server 11 © Cengage Learning 2015 2012/R2, Exam 70-411 Installing and Configuring the WDS Role • Use Server Manager or PowerShell to install WDS • Two role services will be selected to install by default: – Deployment Server – Transport Server • To install the WDS role with PowerShell, enter the following command: Install -WindowsFeature WDS

MCSA Guide to Administering Microsoft Windows Server 12 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Initial Configuration

• Before you can use WDS, you must perform initial configuration • Choose between an Active-Directory-integrated installation or stand-alone server installation – Active-Directory is the default and recommended • Prestaging - enables you to do a basic unattended installation – Prestage client computers by creating computer accounts for them in Active Directory • Do not use the System volume to store boot and install images

MCSA Guide to Administering Microsoft Windows Server 13 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Initial Configuration

MCSA Guide to Administering Microsoft Windows Server 14 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Initial Configuration

• If DHCP is installed on the server, you need to configure how DHCP works with WDS – Both options should be selected

MCSA Guide to Administering Microsoft Windows Server 15 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Initial Configuration

• Use the next window to define which PXE clients the WDS server should respond to

MCSA Guide to Administering Microsoft Windows Server 16 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: General - displays computer name, location of the remote installation folder where images and WDS-related files are stored, and the mode in which WDS is running

MCSA Guide to Administering Microsoft Windows Server 17 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: PXE Response - defines which client computers the WDS server responds to • You can also adjust how quickly the WDS server responds to PXE clients – Should be set to the default value, 0

MCSA Guide to Administering Microsoft Windows Server 18 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: AD DS - defines the naming policy for unknown client computers – You can also specify where the computer account is created in Active Directory

MCSA Guide to Administering Microsoft Windows Server 19 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: Boot - specifies the PXE boot policy for both known and unknown clients – You can specify a default boot image – If no boot image is specified, client uses the boot images in the Boot Images folder of the WDS management console MCSA Guide to Administering Microsoft Windows Server 20 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: Client - use to enable unattended installations for client computers – You can specify that the computer should not join the domain after the installation is finished

MCSA Guide to Administering Microsoft Windows Server 21 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: DHCP - enables you to change how WDS and DHCP work together

MCSA Guide to Administering Microsoft Windows Server 22 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: TFTP - use to fine-tune TFTP, which is used to transfer image and other files between the client and WDS server – Variable Window Extension is a new feature that allows Windows to adjust the transfer window size

MCSA Guide to Administering Microsoft Windows Server 23 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: Network - enables you to change the UDP port policy – Allows you to change the range of UDP ports used by WDS

MCSA Guide to Administering Microsoft Windows Server 24 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: Advanced - is used to have WDS discover domain controllers dynamically or to set a specific domain controller and global catalog server manually

MCSA Guide to Administering Microsoft Windows Server 25 © Cengage Learning 2015 2012/R2, Exam 70-411 WDS Server Properties

• WDS Properties: Multicast - is used to specify whether multicast addresses should be assigned via DHCP or with a specific range of addresses

MCSA Guide to Administering Microsoft Windows Server 26 © Cengage Learning 2015 2012/R2, Exam 70-411 Working with WDS Images

• After installing and configuring WDS, you can work with WDS images • The following sections go into more detail on boot and install images

MCSA Guide to Administering Microsoft Windows Server 27 © Cengage Learning 2015 2012/R2, Exam 70-411 Working with Boot Images

• Main difference between using a WDS boot image and a Windows installation DVD: – The installation image is loaded across the network – Allows many installation to occur at the same time without requiring multiple copies of the installation medium • Client cannot boot from the network without a boot image, so adding a boot image is the first step in working with images – You can use the boot.wim file on the installation DVD

MCSA Guide to Administering Microsoft Windows Server 28 © Cengage Learning 2015 2012/R2, Exam 70-411 Booting from a Boot Image

MCSA Guide to Administering Microsoft Windows Server 29 © Cengage Learning 2015 2012/R2, Exam 70-411 Creating and Using a Capture Image

• Capture image - specialized boot image used to capture the state of an OS already installed and configured on a reference computer • A capture image is created in the WDS management console • Before you boot the reference computer with the capture image, it must be prepared with sysprep – Choose the following options in most cases: • Enter System Out-of-Box Experience • Generalize • Shutdown

MCSA Guide to Administering Microsoft Windows Server 30 © Cengage Learning 2015 2012/R2, Exam 70-411 Creating and Using a Capture Image

MCSA Guide to Administering Microsoft Windows Server 31 © Cengage Learning 2015 2012/R2, Exam 70-411 Working with Install Images

• Install images contain the data and instructions for installing an OS – The install.wim file on a Windows installation DVD might contain multiple installation images • Example: a Windows Server install.wim file might contain four images: – Standard and Datacenter editions in both the Server Core and GUI versions

MCSA Guide to Administering Microsoft Windows Server 32 © Cengage Learning 2015 2012/R2, Exam 70-411 Using a Stock Windows Install Image

• When you configure an install image in WDS, the image must be added to an image group – Image group is a container where you can organize images with common properties • Example: you can create an image group for Windows Server 2012 install images and one for Windows 8.1 install images

MCSA Guide to Administering Microsoft Windows Server 33 © Cengage Learning 2015 2012/R2, Exam 70-411 Image and Image Group Properties

• To set image group permissions: – Right-click the image group in WDS and click Security to open a permission dialog box • You can set different permissions for an image inside the image group: – Right-click the image and click Properties, then click the User Permissions tab • Users who authenticate to the WDS server to access an image must have at least read permissions to the image group

MCSA Guide to Administering Microsoft Windows Server 34 © Cengage Learning 2015 2012/R2, Exam 70-411 Creating Multicast Transmission

• Use multicast transmission to save bandwidth when sending a single image to multiple clients • Two types of multicast transmission options: – Auto-Cast - image transmission starts as soon as a client requests the image – Scheduled-Cast - image transmission begins when the minimum number of clients have joined the transmission or at a particular date and time • Multicast transmissions are configured in the Multicast tab of the WDS server’s Properties window

MCSA Guide to Administering Microsoft Windows Server 35 © Cengage Learning 2015 2012/R2, Exam 70-411 Creating Multicast Transmissions

MCSA Guide to Administering Microsoft Windows Server 36 © Cengage Learning 2015 2012/R2, Exam 70-411 Adding Drivers to WDS

• Driver management is built into the WDS console in the Drivers node – Add drivers to WDS by right-clicking the Drivers node in the WDS console and click Add Driver Package • After drivers are imported to WDS, you can create a driver group – A driver group is a collection of one or more driver packages you can restrict to specific client computers based on client hardware and software specifications

MCSA Guide to Administering Microsoft Windows Server 37 © Cengage Learning 2015 2012/R2, Exam 70-411 Creating Unattended Installations

• An unattended installation requires an answer file – Sometimes referred to as an “unattend answer file” or just “unattend file” • Two main ways to create an unattend file: – Use the System Image Manager tool that comes with ADK – Use the Active Directory Prestaged Devices option in WDS • You can also use a text editor or XML editor

MCSA Guide to Administering Microsoft Windows Server 38 © Cengage Learning 2015 2012/R2, Exam 70-411 Active Directory Prestaged Devices

• When you create an Active Directory prestaged device with WDS, a computer object is created in Active Directory • When the WDS client installs the image, the client is joined to the Windows domain

MCSA Guide to Administering Microsoft Windows Server 39 © Cengage Learning 2015 2012/R2, Exam 70-411 Using System Image Manager

• System Image Manager - a component of the Windows Assessment and Deployment Kit (ADK) – Automates the process of creating an unattend file • When you start the Windows ADK setup program, the default installation choices are adequate for most circumstances • For a fully unattended installation, you need two unattend files: – A client unattend file and an OS unattend file

MCSA Guide to Administering Microsoft Windows Server 40 © Cengage Learning 2015 2012/R2, Exam 70-411 Working with Discover Images

• Deployment Image Servicing and Management (dism.exe) - command-line tool that you can use to update an image with patches, drivers, hotfixes, and service packs • Can be used with offline or online images • Updates can be applied to computers that already installed an OS with WDS – May require a system restart • Two dism options for dealing with automatic restarts: – /preventpending – /norestart

MCSA Guide to Administering Microsoft Windows Server 42 © Cengage Learning 2015 2012/R2, Exam 70-411 Enabling and Disabling Features in Images • Use the dism.exe command to enable and disable features in an existing image – To enable a feature in an image, it must be taken offline and mounted first dism /image:c:\mount /enable-feature /featurename:dhcpserver dism /image:c:\mount /disable-feature /featurename:dhcpserver dism /image:c:\mount /get-features

MCSA Guide to Administering Microsoft Windows Server 43 © Cengage Learning 2015 2012/R2, Exam 70-411 Using PowerShell with WDS

MCSA Guide to Administering Microsoft Windows Server 44 © Cengage Learning 2015 2012/R2, Exam 70-411 Configuring DHCP for WDS

• If DHCP is on a different server or a different subnet, here are the most common setups: • DHCP is on a different server but the same subnet: – On the DHCP tab of the WDS Server’s Properties window, clear both check boxes to ensure that the WDS server is listening for PXE boot requests • DHCP is on a different server or a different subnet: – For Option 066, supply the IP address or server name – For Option 067, enter the boot file’s name and path in relation to the \RemoteInstall directory

MCSA Guide to Administering Microsoft Windows Server 45 © Cengage Learning 2015 2012/R2, Exam 70-411 Configuring DHCP for WDS

• If DHCP is on a different server or a different subnet, here are the most common setups (cont’d): • DHCP is installed on the same server as WDS but it’s not a Microsoft DHCP server – You need to add the 060 PXEClient option to the DHCP server manually – Make sure the option for not listening on DHCP ports is selected in the WDS server’s Properties window

• The WDS server role facilitates installing Windows OSs across a network • The WDS process starts with a client computer that has a PXE-compatible NIC • The WDS server role requires Active Directory, a DHCP server, DNS, clients with PXE-compatible NICs, and suitable storage for boot and install images • WDS is used in several situations, including attended deployments of a standard image, attended deployments of a customized image, and unattended deployments

• The WDS server role has two role services: Deployment Server and Transport Server • To use WDS, you need both boot and install images • An unattended installation requires an answer file or unattend file • If you have clients that can’t PXE-boot, you can create a discover image, which allows a client to boot from a CD/DVD and access a WDS server for the install image

• Install images can be updated with patches, hotfixes, and service packs by using the dism.exe command • You might need to make additional configurations to DHCP, depending on your environment