cc01DeployingAndManagingServerImages.indd01DeployingAndManagingServerImages.indd PPageage 1 11/23/13/23/13 110:270:27 PPMM ff-481-481 //208/WB00898/XXXXXXXXXXXX/ch02/text_s208/WB00898/XXXXXXXXXXXX/ch02/text_s Deploying and LESSON 1 Managing Server Images 70-411 EXAM OBJECTIVE Objective 1.1 – Deploy and manage server images. This objective may include but is not limited to: install the Windows Deployment Services (WDS) role; configure and manage boot, install, and discover images; update images with patches, hotfixes, and drivers; install features for offline images. LESSON HEADING EXAM OBJECTIVE Using Windows Deployment Services Installing the Windows Deployment Services Role Install the Windows Deployment Services (WDS) role Configuring the WDS Server Configuring and Managing Boot, Install, Configure and manage boot, install, and discover images and Discover Images Updating Images with Patches, Hotfixes, and Drivers Update images with patches, hotfixes, and drivers Installing Features for Offline Images Install features for offline images Deploying Driver Packages with an Image KEY TERMS answer files image group Windows Deployment boot image COPYRIGHTEDinstall image MATERIAL Services Capture Utility Deployment Image Servicing and multicasting Windows Deployment Services (WDS) Management (Dism.exe) preboot execution environment (PXE) Windows Imaging Deployment Server System Image Manager (SIM) Format (WIM) discover image System Preparation Utility (Sysprep.exe) Windows Preinstallation dynamic driver provisioning Transport Server Environment features Windows Assessment and (Windows PE) image file Deployment Kit (ADK) 1 cc01DeployingAndManagingServerImages.indd01DeployingAndManagingServerImages.indd PPageage 2 11/22/13/22/13 55:40:40 PPMM ff-481-481 //208/WB00898/XXXXXXXXXXXX/ch02/text_s208/WB00898/XXXXXXXXXXXX/ch02/text_s 2 | Lesson 1 Before beginning this course, you should have some experience installing Windows, including installing Windows Server 2012. In an enterprise environment, many adminis- trators will need to install Windows numerous times. In addition, administrators in many TAKE NOTE * enterprise environments will have a need to deploy servers to remote site. Therefore, as a server administrator, you must be familiar with the various methods to install and deploy Windows. ■ Using Windows Deployment Services In the 70-410 course, you learned how to install Windows from a Windows installation disk. It is not difficult to figure out that installing 100 computers using an installation disk is a daunting task. In these situations, rather than do a manual install on each computer, THE BOTTOM LINE you can use Windows Deployment Services to automatically deploy Windows to multiple computers. While Windows Deployment Services takes a little bit of work up front, it can save you a lot of work later. Windows Deployment Services (WDS) is a software platform and technology that allows you to perform automated network-based installations based on network-based boot and installation media. In other words, you can perform an installation over a network with no operating system or local boot device on it. The WDS server will store the installation files and help you manage the boot and operating system image files used in the network installa- tions. Although WDS is included with later versions of Windows Server, including Windows Server 2012, it can be used to deploy Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, and Windows Server 2012. An image file is basically a snapshot of a computer’s hard drive taken at a particular moment in time. The image file is sometimes referred to as an install image and is used to install an operating system. It contains the following: • All of the operating system files on the computer • Any updates and drives that have been applied • Any applications that have been installed • Any configuration changes that have been made For client computers to communicate with a WDS server without an operating system, the client computer must have support preboot execution environment (PXE), pronounced “pixie.” PXE is a technology that boots computers using the network interface without a data storage device, such as a hard drive or an installed operating system. For a computer to perform a PXE boot, you must configure the BIOS setup program to perform a network boot. Depending on your system, you must enable the PXE boot and/or change the boot order so that the PXE boot occurs before the system tries other boot devices to boot from. When PXE is used with WDS, the client computer downloads a boot image that loads Windows Preinstallation Environment (Windows PE). Windows PE is a minimal Windows operating system with limited services. Windows PE is then used to install the operating system using an operating system image file. Windows PE 4.0 is based on the Windows 8 operating system. Installing the Windows Deployment Services Role WDS is a server role that is included with Windows Server 2012. Therefore, before you can use WDS, you must install the WDS role and configure the services. Then you need to create and add the images that you want to deploy. cc01DeployingAndManagingServerImages.indd01DeployingAndManagingServerImages.indd PPageage 3 11/22/13/22/13 55:40:40 PPMM ff-481-481 //208/WB00898/XXXXXXXXXXXX/ch02/text_s208/WB00898/XXXXXXXXXXXX/ch02/text_s Deploying and Managing Server Images | 3 WDS is a standard server role that can be installed using the Server Manager console and CERTIFICATION READY Install the Windows includes the following two role services: Deployment Services • Deployment Server: Provides full functionality of WDS. It includes an image repository (WDS) role. (including boot images, install images, and other files necessary for remote installation Objective 1.1 over a network), PXE server for remote computers to boot, and a Trivial File Transfer Protocol (TFTP) server to transfer files over the network. TFTP is similar to FTP, but uses User Datagram Protocol (UDP) instead of Transmission Control Protocol (TCP) for less overhead (simpler packets that can be processed faster than TCP packets because UDP does not require the use of acknowledgments). In addition, the Deployment Server includes tools to create and customize images. • Transport Server: While required by the Deployment Server, the Transport Server role is a subset of WDS functionality, but can also be used for custom solutions. The Transport Server can also use multicasting, which allows one set of packets to be sent to multiple computers simultaneously. DEPLOY WDS GET READY. To deploy WDS on Windows Server 2012, perform the following steps: 1. Open Server Manager by clicking the Server Manager button on the task bar. The Server Manager opens. 2. At the top of Server Manager, click Manage and then click Add Roles and Features. The Add Roles and Feature Wizard opens. 3. On the Before you begin page, click Next. 4. Select Role-based or feature-based installation, and then click Next. 5. Click Select a server from the server pool, click the name of the server to install WDS to, and then click Next. 6. Scroll down and select Windows Deployment Services (see Figure 1-1). Figure 1-1 Selecting Windows Deployment Services cc01DeployingAndManagingServerImages.indd01DeployingAndManagingServerImages.indd PPageage 4 11/22/13/22/13 55:40:40 PPMM ff-481-481 //208/WB00898/XXXXXXXXXXXX/ch02/text_s208/WB00898/XXXXXXXXXXXX/ch02/text_s 4 | Lesson 1 7. When the Add Roles and Features Wizard dialog box opens, click Add Features (see Figure 1-2). Figure 1-2 Adding Required Features for WDS 8. Click Next. 9. Back on the Select server roles page, click Next. 10. On the Select features page, click Next. 11. On the WDS page, click Next. 12. On the Select role services page, make sure that the Deployment Server option and the Transport Server option are selected (see Figure 1-3), and then click Next. Figure 1-3 Selecting the WDS Role Services cc01DeployingAndManagingServerImages.indd01DeployingAndManagingServerImages.indd PPageage 5 11/22/13/22/13 55:40:40 PPMM ff-481-481 //208/WB00898/XXXXXXXXXXXX/ch02/text_s208/WB00898/XXXXXXXXXXXX/ch02/text_s Deploying and Managing Server Images | 5 13. On the Confi rm installation selections page, click Install. 14. When the installation fi nishes, click Close. Configuring the WDS Server Before you can use WDS, you must configure the WDS server, including performing the initial server configuration, adding a default startup and install images, and configuring a boot menu. WDS is inactive until you perform the initial configuration of the service and add images to the server. To use WDS, your system must meet the following requirements: • The server is a member of an Active Directory Domain Services (AD DS) domain, or a domain controller for an AD DS domain. • There is an active DHCP server on the network. • There is an active DNS server on your network. • The WDS server has an NTFS file system partition to store images. PERFORMING THE INITIAL CONFIGURATION OF WDS Before you can use WDS, you must configure WDS by determining if the server will be part of Active Directory, determining where the boot and install images will be stored, and configuring the DHCP server so that clients can boot to the WDS server. To perform the initial configuration using the Windows Deployment Services Configuration Wizard, open the Windows Deployment Services console, right-click the WDS server, and then select Configure Server. PERFORM THE INITIAL CONFIGURATION OF WDS GET READY. To perform the