Tài liệu Windows 7 Resource Kit- P8 ppt

CHAPTER 10 Configuring Windows Deployment Services 304 the Windows 7 boot manager must be configured to boot directly into the VHD. Note, however, that if you simply deploy Windows 7 into a VHD, you’ll go through the Sysprep specialize pass, which prevents you from using the VHD on physical machines. The workaround for this is to first use the Wim2vhd tool available from http://code.msdn.microsoft.com/wim2vhd, create a VHD, and then use ImageX to apply the contents of the WIM into the VHD. VHD images are not intended to replace WIM images for general deployment purposes. Furthermore, beginning with Windows Server 2008 R2, Windows Deployment Services now supports deploying VHD images in addition to deploying WIM images. Specifically, when you deploy a VHD through Windows Deployment Services, the Bootmgr entries are automatically fixed, so there is no extra step. For example, you can use Windows Deployment Services to deploy VHD images during an unattended installation. For more information on native booting to VHD images, see “Understanding Virtual Hard Disks with Native Boot” in the Windows Client TechCenter on Microsoft TechNet at http://technet.microsoft.com/en-us/library/dd799282.aspx. For more information on deploying VHD images using Windows Deployment Services, see “Deploying Virtual Hard Disk Images” in the Windows Server TechCenter on Microsoft TechNet at http://technet.microsoft.com/en-us/library/dd363560.aspx. n PXE provider for Transport Server Windows Deployment Services now includes a PXE provider for the Transport Server role service. This lets you use a stand-alone Transport Server to boot from the network or to multicast data without the need of AD DS or Domain Name System (DNS). n Additional EFI support Windows Deployment Services now supports network booting of x64-based computers that use EFI. MoRe inFo For additional information concerning these new features, see http://technet.microsoft.com/en-us/library/dd735188.aspx. Server Requirements The hardware requirements for running Windows Server 2003 or Windows Server 2008 are sufficient to support most Windows Deployment Services installations. If you are supporting a large number of images or if you are expecting greater-than-normal client load, investigate adding additional memory for performance and additional hard drive space for image storage. Adding more network adapters can also help with the TFTP download phase if you have a large client load. The following list describes the software and service requirements for installing and using Windows Deployment Services: n AD DS A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for a domain. AD DS is used by Windows Deployment Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Planning for Windows Deployment Services CHAPTER 10 305 Services to track Windows Deployment Services clients and Windows Deployment Services servers. In addition, systems can be preconfigured in AD DS, instructing Windows Deployment Services on how to image them. Note that AD DS is required only for Deployment Server, not Transport Server. n DHCP You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which in turn uses DHCP. The DHCP server does not have to be on the Windows Deployment Services server. The type of DHCP server is not critical for Windows Deployment Services to function properly. To operate Windows Deployment Services and DCHP on the same server, see the section titled “DHCP Requirements” later in this chapter. Note that if you are using Transport Server for multicast only (no PXE), then you don’t need DHCP. n DNS A working DNS server on the network is required to run Windows Deployment Services. The DNS server does not have to be running on the Windows Deployment Services server. DNS is used to locate AD DS domain controllers and Windows Deployment Services servers. n Installation media Windows 7 media or a network location that contains the contents of the media are required to install Windows 7 using Windows Deployment Services. n An NTFS partition on the Windows Deployment Services server The server running Windows Deployment Services requires an NTFS File System (NTFS) partition for the image store. You should not create the image store on the partition containing the operating system files, so an additional partition is necessary. n SP1 or later version and RIS installed (Windows Server 2003 only) If you’re installing Windows Deployment Services on a server running Windows Server 2003, you must install RIS for the Windows Deployment Services update package to be run. Windows Deployment Services also requires at least SP1. note Installing and administering Windows Deployment Services requires the administrator to be a member of the local Administrators group on the Windows Deployment Services server. In addition, most administrative tasks for Windows Deployment Services require Domain Admins credentials. Client Computer Requirements The client computer requirements to support installation using Windows Deployment Services will vary based on how you intend to use Windows Deployment Services. The following list outlines the requirements for PXE booting to Windows Deployment Services and installing images: n Hardware requirements The client must meet the minimum hardware requirements of the operating system you’re installing. The client must also have enough memory Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 10 Configuring Windows Deployment Services 306 to run Windows PE (384 megabytes [MB] required, 512 MB recommended), because Windows Deployment Services uses Windows PE to start the client computer. n PXE DHCP-based boot ROM version .99 or later network adapter To boot directly from the Windows Deployment Services server, the client’s network adapter must contain a PXE boot ROM. If this is not the case, the client can be booted using a DVD boot disk, a Windows PE boot image copied to the computer’s hard disk, or a USB flash drive (UFD). See the section titled “Preparing Discover Images” later in this chapter. All computers meeting the NetPC or PC98 specifications should have the ability to boot from the network adapter. Investigate the basic input/output system (BIOS) set- tings of the client to determine whether you can enable a Boot From Network option. When the option is enabled, the client should briefly display an option to press F12 to boot from the network during each startup. n Network access to the Windows Deployment Services server The client must have broadcast access to the Windows Deployment Services server to enable PXE booting. Windows PE boot disks can allow you to boot to Windows PE using Windows Deployment Services as an image store without broadcast access. note The account performing the installation must be a member of the Domain Users AD DS security group. Domain Users have permission to join computers to the domain. DHCP Requirements Windows Deployment Services will configure accessible DHCP servers during installation, adding required scope options to the DHCP scopes. It may be necessary under some circumstances to modify DHCP servers manually to support advanced Windows Deployment Services scenarios. The following list describes how to manage DHCP scope modifications: n Microsoft DHCP and Windows Deployment Services on the same server When Windows Deployment Services is installed on the same physical server as the DHCP service, the Windows Deployment Services PXE server and the DHCP server will both attempt to listen on port 67 for DHCP requests. To prevent this, the Windows Deployment Services PXE server must be configured not to listen on this port. (See Figure 10-5.) This allows booting PXE clients to learn about the presence of the Windows Deployment Services PXE server from the DHCP response generated by the DHCP server. n Microsoft DHCP and Windows Deployment Services on separate servers with the clients on the same subnet as the Windows Deployment Services server When Windows Deployment Services and Microsoft DHCP exist on different servers, no additional settings are required. Both servers respond to DHCP requests. The DHCP server responds with an IP address offer; the Windows Deployment Services PXE server responds with the PXE boot information. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Planning for Windows Deployment Services CHAPTER 10 307 n Microsoft DHCP and Windows Deployment Services on separate servers with the clients on a different subnet from the Windows Deployment Services server The recommended approach in this scenario is to use IP Helper tables on the router or switch to forward PXE requests to the Windows Deployment Services server (as well as the DHCP server). An alternative approach is to configure DHCP options 66 and 67 on all scopes to specify the Windows Deployment Services server and the path to the boot program. n Third-party DHCP and Windows Deployment Services on separate servers No additional action should be required for Windows Deployment Services to coexist with third-party DHCP servers. The Windows Deployment Services PXE server will respond with boot file location information only, allowing DHCP to service the IP address request. FIGURE 10-5 Configuring DHCP options in Windows Deployment Services note RIS requires the RIS server to be authorized as a DHCP server in AD DS. This is not required to operate Windows Deployment Services. Routing Requirements When DHCP and Windows Deployment Services are located on different subnets or if clients are located on a different subnet than the Windows Deployment Services server, IP Helpers must be configured on network routers to enable forwarding of DHCP and PXE boot requests to the appropriate servers. (See Figure 10-6.) Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 10 Configuring Windows Deployment Services 308 DHCP Server DHCP Relay Agent (optional) PXE ClientPXE Client Router Enable IP Helper to forward DHCP/PXE broadcasts A B Windows Deployment Services FIGURE 10-6 Windows Deployment Services on multiple subnets note An alternative to enabling IP Helpers on your routers is to install a DHCP relay agent on the remote network, configuring appropriate scope options to allow the remote clients to locate the Windows Deployment Services server. Capacity Requirements Windows Deployment Services servers can generate a lot of network traffic when servicing multiple, simultaneous client requests. Plan for this network load by designing your deploy- ment network for sufficient capacity. You can deploy multiple Windows Deployment Services servers or use multicasting (requires Windows Server 2008 or later versions) in environments that experience significant installation activity. Note that beyond about 25 to 50 simultaneous clients, the bottleneck becomes TFTP, which is unicast and is required to download Windows PE. (Windows Deployment Services supports multicast download of Windows PE only for x64 Unified Extensible Firmware Interface [UEFI] machines). You can allocate access to Windows Deployment Services by using DHCP scopes and IP subnetting. You can also configure IP Helper tables to direct clients to one or another Windows Deployment Services server based on client network ID. Installing Windows Deployment Services Windows Deployment Services is installed as an update to Windows Server 2003 or added as a server role in Windows Server 2008 R2. The following procedures outline the basic installa- tion steps for Windows Deployment Services. Refer to the appropriate guidance (listed in the Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Installing Windows Deployment Services CHAPTER 10 309 section titled “Additional Resources” at the end of this chapter) for complete instructions and planning advice. Windows Server 2003 To completely install Windows Deployment Services on a computer running Windows Server 2003, you must first install RIS. After RIS is installed, you install the Windows Deployment Services update or Windows Server 2003 SP2 (which contains the update). The Windows AIK also includes the Windows Deployment Services update, which you can install on any server after extracting the file from the Windows AIK media. To install RIS on Windows Server 2003, perform the following steps: 1. In the Add Or Remove Programs utility in Control Panel, click Add/Remove Windows Components. 2. Select the check box next to Remote Installation Services, as shown here, and then click Next. note In Windows Server 2003 SP2, the Remote Installation Services feature is named Windows Deployment Services. To install the Windows Deployment Services update, perform the following steps: 1. Run the Windows Deployment Services update from the Windows AIK. The file is windows-deployment-service-update-platform.exe, where platform is either x86 or x64, and is found in the WDS folder on the Windows AIK DVD. (If you have already installed SP2 for Windows Server 2003, you do not need to perform this task.) Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 10 Configuring Windows Deployment Services 310 2. On the Windows Deployment Services Setup Wizard Welcome page, shown here, click Next. 3. On the Microsoft Software License Terms page, click I Accept The Terms In The License Agreement. Click Next. 4. The Updating Your System page displays installation progress. 5. On the Completion page, click Finish to restart the computer. note Unless you plan to use Riprep legacy images, you can proceed with the configu- ration of Windows Deployment Services at this point. To enable Windows Deployment Services mixed mode, ensure that you do not install this update until at least one Riprep image is installed on the RIS server. For more information on the installation and configu- ration of RIS, see “Designing RIS Installations” in the Windows Server 2003 Resource Kit. Windows Server 2008 R2 You can install Windows Deployment Services by using the Add Roles Wizard, located in Server Manager. To add the Windows Deployment Services server role, perform the following steps: 1. Start the Add Roles Wizard from Server Manager. 2. Click Next to skip the Before You Begin screen. 3. Select the Windows Deployment Services role, as shown here, and click Next. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Configuring Windows Deployment Services CHAPTER 10 311 4. Additional information on installing and using Windows Deployment Services is displayed. 5. Click Next when you are ready to proceed. 6. On the Select Role Services page, click Next to install both the Deployment Server and the Transport Server role services. The Deployment Server role service contains all of the core Windows Deployment Services functionality. The Transport Server role service contains the core networking features. 7. On the Confirm Installation Selections page, click Install. 8. Windows Deployment Services is installed. 9. Click Close to complete the Add Roles Wizard. Configuring Windows Deployment Services After Windows Deployment Services is installed, you will need to add the server to the management console and then configure it. Windows Deployment Services automatically adds the local computer to the console. If you want to add a remote server, you must add it. To add a server to Windows Deployment Services, perform the following steps: 1. Open the Windows Deployment Services management console by selecting Windows Deployment Services from Administrative Tools. You can also use the Windows Deployment Services node under Roles in Server Manager. 2. Right-click Servers in the Windows Deployment Services console tree and then click Add Server. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. CHAPTER 10 Configuring Windows Deployment Services 312 3. In the Add Server dialog box, choose a computer to add to the console. The server will be added and will now need to be configured. To initially prepare the Windows Deployment Services server, perform the following steps: 1. In the Windows Deployment Services console tree, right-click the server and click Configure Server. 2. On the Windows Deployment Services Configuration Wizard Welcome page, make sure that your environment meets the requirements and then click Next. 3. Enter a path for the image store, as shown here, and then click Next. The folder should be on a partition other than the partition containing the system files. If you choose to create the image store on the system drive, a warning message will appear. Click Yes to continue or click No to choose a new installation location (recommended). 4. Configure DHCP Option 60 settings, as shown here, and then click Next. (Depending upon your configuration, this screen may or may not be displayed.) See the section titled “DHCP Requirements” earlier in this chapter for information on how to properly configure these settings. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Preparing Discover Images CHAPTER 10 313 5. Set a PXE Server Initial Settings policy, as shown here, and then click Next. 6. On the Configuration Complete page, you can add images to the server (default) or clear the Add Images To The Windows Deployment Services Server Now check box if you want to add images at another time. To add images to your server, see the section titled “Importing Images” later in this chapter. Preparing Discover Images For client computers that do not support PXE booting, you can create boot disks using a CD or DVD, a hard disk, or a UFD. You can create these disks by using the Windows Deployment Services administration tools or the Windows PE administration tools from the Windows AIK. The process begins by creating a Windows PE boot image using the Windows Deployment Services console or Wdsutil. After this image is created, a bootable disk is made using the Oscdimg command from the Windows AIK. To create a discover image using the management console, perform the following steps: 1. In the Windows Deployment Services management console, click Boot Images. Boot Images is under Servers, server_name, where server_name is the name of the Windows Deployment Services server. 2. Right-click a boot image that you previously added to Windows Deployment Services to use as a discover image and then click Create Discover Boot Image. 3. On the Metadata And Location page, type a name and description for the discover image, as shown on the following page. Then choose the location in which to create the image and the Windows Deployment Services server to respond to it. Click Next. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. [...]... folder Summary Windows Deployment Services provides a solution for the network-based installation of Windows 7 It’s built on standard Windows 7 setup technologies, including Windows PE, wim image files, and image-based setup Using Windows Deployment Services can help reduce the cost and complexity of Windows 7 deployments In Windows Server 2008 R2, Windows Deployment Services replaces RIS Windows Deployment... installation to meet your requirements You can install Windows 7 on your reference computer either from media or using Windows Deployment Services To learn how to install Windows 7 using Windows Deployment Services, see the section titled “Installing Windows 7 earlier in this chapter 2 From a command prompt on the master computer, change directories to \Windows \System32\Sysprep and run the following command... Install Windows? page, choose a partition on which to install Windows 7 and then click Next To repartition the disk using advanced options, click Drive Options (Advanced) 7 Windows Setup will install Windows 7, prompting for required settings that are not specified in an unattended-setup answer file Capturing Custom Images Windows Deployment Services can deploy more than just default images from the Windows. .. folder of the Windows 7 media to the C:\Program Files\Microsoft Deployment Toolkit\Bin folder It also requires that at least one Windows 7 source must exist within the deployment share and that you must create and update a deployment share MDT 2010 uses the setup program files from the deployment share to install the Windows 7 image from the Windows Deployment Services server To add images from Windows Deployment... the Windows Deployment Services server role in Windows Server 2008 or Windows Server 2008 R2 The Windows Deployment Services update for Windows Server 2003 SP1 and later versions does not support multicast deployment Multicast deployment is supported for install images only The Boot.wim file used for multicast deployment must be imported from Windows Server 2008, Windows Vista SP1 or later versions, Windows. .. contacts the KMS host is running Windows Server 2008 R2, it receives an activation count of 4, because activation counts are a combination of computers running Windows Server 2008 R2 and Windows 7 If a computer running Windows Server 2008 or Windows Server 2008 R2 receives an activation count that is greater than or equal to 5, it is activated If a computer running Windows 7 receives an activation count... booted to Windows PE will enter a pending state until an administrator approves their installation You can view systems in this state in the Pending Devices item of the Windows Deployment Services management console 326 Chapter 10  Configuring Windows Deployment Services Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark Installing Windows 7 For ease of installing Windows 7, client... Windows 7 or Windows Server 2008 R2 source files You can also customize boot images with hooks into services, such as MDT 2010 For example, MDT 2010 builds custom Windows PE boot images that connect to MDT 2010 deployment points to install operating system builds You can add these custom Windows PE boot images to Windows Deployment Services to streamline the LTI deployment process To import a Windows 7 boot... Additional Resources  353 V olume Activation is a configurable solution that helps IT professionals automate and manage the product activation process on computers running the Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 operating systems licensed under a Microsoft Volume Licensing program and other programs that provide Volume License editions of Microsoft Windows This... requesting activation on the network The Windows Server operating systems (starting with Windows Server 2008) and Windows client operating systems (starting with Windows Vista) are activated after meeting different thresholds The Windows Server activation threshold is 5 computers, and the Windows client activation threshold is 25 computers The threshold includes Windows client and server operating systems . required to install Windows 7 using Windows Deployment Services. n An NTFS partition on the Windows Deployment Services server The server running Windows Deployment. http://technet.microsoft.com/en-us/library/dd735188.aspx. Server Requirements The hardware requirements for running Windows Server 2003 or Windows Server 2008 are sufficient to support most Windows