Академический Документы
Профессиональный Документы
Культура Документы
Advanced Tasks
The earlier sections of this document describe the very basic usage and configuration of WDS, however WDS has a lot more to offer. In this section you will see some of the additional things you can do with WDS to improve automation and network utilization.
8/23/13
To start with I will explain how to create a WDS client unattended XML file, then I will cover the OOBE unattended XML file. Both files can be made using the WAIK namely the Windows System Image Manger utility however each file will vary greatly.
itadmintips.wordpress.com/category/windows-deployment-services/
One thing to remember with both files is try to keep them simple. Group policy can handle basically 2/13
8/23/13
One thing to remember with both files is try to keep them simple. Group policy can handle basically everything that the unattended files can do, so keep the options within the XML file to a minimum. This will reduce the hassle of troubleshooting these files, as the error messages are not too much help.
To apply the ImageUnattend.xml: 1. 2. 3. 4. 5. 6. 7. 8. Open the WDS Console. Expand the Servers > YourServer node and select Install Images. Select an image group group containing an image. Right click an image, select properties. On the general tab, tick Allow image to install in unattended mode. Click Select File and browse to the ImageUnattend.xml file. Click Open Click OK
Multicast Transmissions
As stated earlier, WDS uses unicast to send images to clients by default. If you are only imaging 1 or 2 computers, thats fine; however if you needed to image 50 computers at once, it would cause enormous amounts of traffic. That is where the multicast comes in.
itadmintips.wordpress.com/category/windows-deployment-services/
With WDS, multicast uses a round robin approach. Computers can join the multicast whenever they 3/13
8/23/13
With WDS, multicast uses a round robin approach. Computers can join the multicast whenever they want and if they miss out on the first 100 packets, they will get them next time around. This means that you can set up 50 computers, start them at the same time, and the image will get sent once, but will be received by all 50 computers. This greatly reduces network bandwidth utilization and speeds up imaging performance when imaging large numbers of machines. Multicasting requires 1 main thing, which is network hardware (switch/router) that supports the IGMP protocol. This protocol allows the switch to identify clients of a multicast and send data to only their addresses. If IGMP is not enabled, multicast packets will be treated as broadcast packets, which will lead to network flooding. For information on enabling the IGMP protocol, or to find out if your network hardware supports the IGMP protocol, contact your hardware vendor. The other thing multicasting requires is that you use at least either the Vista SP1 Boot.WIM, or the server 2008 Boot.WIM.
When you connect your clients using the Server 2008/Vista SP1 Boot.WIM and select the image that has a multicast created, it will be added to the multicast automatically. Depending on the multicast type you chose, it will start automatically, or you can choose to have a scheduled start, or a manual start.
itadmintips.wordpress.com/category/windows-deployment-services/
4/13
8/23/13
8/23/13
Once the WDS server is configured and you have a capture image and a normal boot image setup you can start to deploy and capture images using WDS. The following sections outlines the steps required to setup and capture an install of Windows 7 Enterprise.
Capturing an Image
Setup a Reference System
The reference system is simply a system that you have set up, containing all of your desired applications and drivers. This reference image is captured with WDS and can then be deployed to computers across the network. Some important things to check include: Ensure you have the right MAK key installed on the reference install. If you have a KMS server this will not be needed. Turn off hibernation (type powercfg h off at the command line) to save HDD space. Turn off system restore to save HDD space. Remember that doing so will stop windows from taking snapshots as the system changes and will mean that you cannot restore the computer to previous states. This feature seems unnecessary considering you can use the image you are creating to revert the system to the original state. Make sure you sysprep the machine before attempting to capture the image, otherwise you will NOT be able to capture it. (explained below) Add any language settings you may want. Once you have setup all programs on the reference computer, you must use the sysprep utility to strip the reference computer of machine specific things, such as the machine SID. To sysprep a machine: 1. 2. 3. 4. Ensure all of your programs and settings are configured. Navigate to C:\Windows\System32\Sysprep Double click the sysprep.exe file. A small, simple GUI will show. Select Enter System Out-of-Box Experience from the drop down box. 5. Tick the generalize box. 6. Select shutdown from the shutdown options box. 7. Click Ok Sysprep will now remove all machine specific data and force the machine to boot into the OOBE on the next boot just as if the PC had come from an OEM like HP or Dell. It is a requirement of WDS that you sysprep the machine before capture any volume that has not been syspreped will not show up as an available volume to capture with WDS!
itadmintips.wordpress.com/category/windows-deployment-services/ 6/13
8/23/13
Deploy an Image
Deploying an image with WDS can be done in 2 main ways unicast or multicast. This part of the guide will show how to use a simple unicast. Unicast mode requires no setup, as it is the default method of transfer. To deploy an Image (i.e. the one you just made in the previous steps) Do the following: 1. PXE boot any computer and select the install boot image, rather than the capture boot image. 2. You will see screens very similar to a standard disc install of windows, select your desired settings (Image, HDD Config etc) and then let the Image install. 3. Once the image is installed, you will be booted into the OOBE screens. Select the appropriate time, date, and computer name and so on. 4. The image is now ready to use and can be joined to the domain without the need to ReSID. This section outlined the basic steps to create, capture and install an image using WDS. For further information, such as using multicast groups and unattended installations, see the next section.
itadmintips.wordpress.com/category/windows-deployment-services/
8/23/13
Continue to Part 4 Advanced Tasks (http://itadmintips.wordpress.com/2011/05/19/wds-setup-guidepart-4-%e2%80%93-advanced-tasks/) FILED UNDER WINDOWS DEPLOYMENT SERVICES TAGGED WITH 7, ADD, BOOT, CAPTURE, DEPLOYMENT, DRIVER, IMAGE, INJECT, PXE, SERVICES, UNATTEND, WINDOWS, XML
8/23/13
6. Give a name and description to the image, click Next. 7. Review the settings and click Next, the image will be added to the server. 8. Click Finish. The boot image you just added should be visible in the right hand pane when you click the Boot Images node. The Image name you chose will show up as an option when you network boot a computer. This Image type is used when you want to install an Image to a machine, to capture an image see the next section.
The server should now be setup to capture and deploy images. These images can be deployed to any computer with PXE booting enabled. The next section outlines how to setup an image, sysprep it for capturing with WDS, and then deploy the image to multiple computers. Continue to Part 3 Install Images Capture and Deployment (http://itadmintips.wordpress.com/2011/05/19/wds-setup-guide-part-3-%e2%80%93-install-imagescapture-and-deployment/) FILED UNDER WINDOWS DEPLOYMENT SERVICES TAGGED WITH 7, ADD, BOOT, CAPTURE, DEPLOYMENT, DRIVER, IMAGE, INJECT, PXE, SERVICES, UNATTEND, WINDOWS, XML
itadmintips.wordpress.com/category/windows-deployment-services/
9/13
8/23/13
itadmintips.wordpress.com/category/windows-deployment-services/
10/13
8/23/13
MMC Setup
Once the role is installed: 1. Go to Start > Administrative Tools > Windows Deployment Services The WDS MMC will start up. 2. Right Click the Servers node and select Add Server. 3. Enter the name of the server hosting WDS and click ok. 4. Right click the newly added server and click All Tasks > Start. This is the basic setup required, however when I installed it myself, I had to configure the AD settings to point to our local DC before the service would successfully start.
Initial Configuration
1. 2. 3. 4. Right Click the newly added server. Select Properties. Select the Advanced Tab. Select the Let Windows Deployment Services use only these specified servers radio button, and browse for the local DC Use the same setting for both the Domain Controller and Global Catalog fields. 5. Click Ok to apply the changes. 6. Right click the server and click All Tasks > Start. The server should now successfully start. Once you have successfully started the service, you must enable the PXE server to allow clients to boot using their network boot option. You may also set the server use DHCP to assign IP addresses to WDS clients. 1. In the WDS MMC, right click the server and choose Properties. 2. Go to the PXE Response Settings tab. 3. Select Respond to all (known and unknown) client computers. Radio button. Leave the tick box blank[1] 4. Go to the Network Settings tab. 5. Select Obtain IP address from DHCP Once you have completed the above steps, clients should be able to access the PXE server on boot; however they will not have any available images to boot into. Setting up boot images and install images will be covered in the following section. You will notice that WDS creates its own image store, which is shared on the network. Do not modify the structure of this share, as it may cause issues.
itadmintips.wordpress.com/category/windows-deployment-services/ 11/13
8/23/13
[1] Leaving this blank means that anyone can connect to the PXE server without Admin Approval; I chose this because I was getting access denied errors while trying to allow PXE clients awaiting authorization. If you have sufficient privileges, select the check box as it allows for greater control over the use of the PXE server. Continue to Part 2 Boot Image Setup (http://itadmintips.wordpress.com/2011/05/19/wds-setupguide-part-2-boot-image-setup/) FILED UNDER WINDOWS DEPLOYMENT SERVICES TAGGED WITH 7, ADD, BOOT, CAPTURE, DEPLOYMENT, DRIVER, IMAGE, INJECT, PXE, SERVICES, UNATTEND, WINDOWS, XML