Windows deployment services operate in

To configure the Windows Deployment Services server role integrated with Active Directory, use the following procedure. On the Install options page, choose Integrated with Active Directory. Now that you have configured the server integrated with Active Directory, you will need to add your images.

For instructions, see the next section, Steps for adding images. You must add at least one boot image and one install image before you will be able to boot to the Windows Deployment Services server and install an image. Boot images. Boot images are Windows PE images that you boot a client computer into to perform an operating system installation.

In most scenarios, you should use the Boot. The Boot. Install images. Install images are the operating system images that you deploy to the client computer. You can also use the Install. The following instructions use Windows 7 installation media as an example for creating an install image that can be deployed with Windows Deployment Services.

You can also use the same instructions for server installation media. Browse to choose the default boot image Boot. On the Image Metadata page, enter the desired image name and description. After you have at least one boot and one install image on the server, you can deploy an install image. Select the appropriate boot image from the boot menu. This boot image selection menu will be available only if you have two or more boot images on the server.

Click OK. At the Install Windows dialog box, select the operating system you wish to install. If you only have one operating system to install, choose that and click Next. If prompted at the Where do you want to install Windows page, select the partition you wish to install the operating system on. When you have multiple boot or install images available to client computers, clients will be presented with a boot and an install menu that displays the selection of images to choose from.

Windows Deployment Services allows you to set priorities to control the order that both boot and install image listings are presented to clients. This ability is integrated directly into Windows Deployment Services. Click the Boot Images node. Click Properties. In the Image Properties dialog, on the General tab, enter in your desired priority into the Priority text box. The items that appear first on your install image menu are the ones with the lowest value.

Double-click the Install Images node. You will see your image group or image groups appear as a sub menu item. Right-click your desired image within your image group from the right-hand side of your Windows Deployment Services MMC snap-in. On the Image Properties dialog, in the General tab, enter in your desired priority into the Priority text box. When you have completed this procedure and you perform a PXE boot on a client computer, a boot or install menu with the menu order you set using priorities will appear.

Priorities are pre-populated with a default value that lets you place images higher or lower on the list. The items that appear first on the list are the ones with the lowest value. Optionally, you can create custom install images for Windows 8. To do this, use the instructions in this section to create a capture boot image, prepare a reference computer using Sysprep, and then capture the operating system using the Image Capture Wizard.

When you boot into the capture image, the Image Capture Wizard will start. Note the following points about this wizard:. If you do not run Sysprep on the computer before you boot into the image, you will not see any drives to capture. You must enter a local location to save the new install image; otherwise, you will not be able to capture the image. This location can be a mapped network drive but we recommend that you use a local location to avoid image corruption in the event of a network malfunction.

To create an install image, you must first create a capture image. Capture images are boot images that you boot a client computer into to capture the operating system into a.

These images provide an alternative to the command-line utility, ImageX. Except in advanced scenarios, you can create a capture image by using the Boot.

Right-click the image to use it as a capture image. In most cases, you can just use the Boot. Type in your Image Name, Image Description, and the location and file name where you want to save a local copy of the file. You must specify a location in case there is a problem with the network when you deploy the capture image. Enter the location of the Windows Image file that contains the images.

Enter your Image Name and Image Description. After you have created the capture image, follow the instructions in the next section to boot a computer into the capture image and capture the operating system.

Now that you have a capture image, you need to prepare a reference computer and then create the install image. The reference computer can be a computer with a standard Windows installation or a Windows installation that has been configured for your environment. First, you boot a computer which has been prepared with Sysprep into the capture image. Then a wizard creates an install image of the reference computer and saves it as a. After that, you can deploy the.

Create a reference computer install the operating system, applications, and make any other changes that you want. In the boot menu, select the capture boot image that you created in the preceding procedure, and then press ENTER. On the Directory to Capture page, select Volume to capture , enter your Image name and Image description. Referring to Volume to capture , you will see only drives that contain operating systems prepared with Sysprep.

If you do not run the command in step 4, you will not see any drives to capture. Click Browse next to Name and location and browse to a local folder where you want to store the captured install image. Type a name for the image, using the. Note that this location can be a mapped network drive. You must enter a local location to save the new image; otherwise, you will not be able to capture the image. This requirement is enforced to avoid image corruption if there is a network malfunction.

Click Connect. If prompted for credentials, provide a user name and password for an account with permissions to connect to the Windows Deployment Services server.

Select your Image Group Name. The wizard will now complete and create a custom installation image and store it in the Windows Deployment Services store. When this process is complete, you can PXE boot a client computer to install this image. The image will be listed in the installation option. If you have a computer that is not PXE enabled, you can create a discover image and use it to install an operating system on that computer. Otherwise, you can skip this section. The discover image on the media locates a Windows Deployment Services server, and the server deploys the install image to the computer.

You can configure discover images to target a specific Windows Deployment Services server. This means that if you have multiple servers in your environment, you can create a discover image for each one, and then name them based on the name of the server. After you create the discover image, you will need to create media that contains the image. You must create discover images by using the Boot.

In the location and file name, click Browse and select the location for storing your discover boot image. Enter the name of your discover image. Optionally, enter the name of your Windows Deployment Services server that you want to respond when you boot a computer into this image.

This following example details how to create media that contains a discovery image. However, it is an example only; you can substitute any values you require. This will force the computer to await explicit authorization before it will be processed by the PXE server. Click Next to continue. The configuration process for WDS takes several minutes, depending on the speed of the server being used Figure Q.

Once WDS has been successfully configured, it'll be ready to use, except it does not have any media -boot or install WIMs--to deploy. Click the Finish button to complete the configuration. Windows Deployment Services will require boot images to respond to client requests and install images to actually deploy Windows onto these client systems. This will allow for specified OSes to be installed by default on client computers in a straightforward manner.

Has WDS simplified your Windows deployment tasks? Share your experiences and advice with fellow TechRepublic members. He brings 19 years of experience and multiple certifications from seve Image: iStockphoto. Editor's Picks. The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script.

TasksBoard is the kanban interface for Google Tasks you've been waiting for. Paging Zefram Cochrane: Humans have figured out how to make a warp bubble. Comment and share: How to get started with Windows Deployment Services.

Show Comments. Hide Comments. My Profile Log out. This took her around 45 minutes per computer almost 19 hours to set up the operating system on all the client computers. For almost three days, Monica was unavailable to work on anything else. Then she would spend almost as much time installing the applications on each computer. Monica is the only IT professional at Fabrikam, which means that she also must help teach users about the new operating system.

Therefore, it is important that she minimizes the amount of time she spends on deployment. To accomplish this, Monica chooses to use Windows Deployment Services because she can:. Adds the Boot. Adds the Install. Uses the MMC snap-in to create a capture image from the boot image she added in step 3.

This image contains Windows PE and a wizard that will capture her custom image into a. All users at Fabrikam have the same desktop hardware, which was purchased from a single vendor.

To deploy a standard image to the computers, Monica does the following:. Boots a reference computer from the network and installs the Install. Uses the Image Capture Wizard to recapture the operating system and upload it directly to the Windows Deployment Services server.

Now, Monica is ready to install the new operating systems. She does not need to migrate any user data, because all of the employees store their user data on a server rather than on their hard disks. She reboots a client computer and then presses F12 to perform a network boot. This boots her into the Boot. She selects the disk partition and image she wants, and then the installation begins.

While waiting for the image to be applied to the first computer, Monica boots another computer and starts the same process on that one. Northwind Traders is a shipping firm with three offices: a central office in Tooth City, and branch offices in the towns of Brushville and Flosston. His responsibility is maintaining the client computers used by the company's employees.

These are mostly desktop computers, but the sales force uses laptops for customer presentations. There are computers in the central office in Tooth City, and 25 each in the Brushville and Flosston offices.

Each site has an internal network running at MB per second MBps , and the branch sites are connected to the Tooth City office by a T1 line. Ron has three Windows Deployment Services servers at the Tooth City office and one in each of the branch offices, which are administered remotely.

Previously, this would have involved many expensive trips to Brushville and Flosston, and it would have taken Ron several weeks to complete. He wants to use Windows Deployment Services to deploy Windows remotely; however, company policy dictates that there can be only one DHCP server on the corporate network, and this server is located at the Tooth City office.

Remotely deploying images to the 50 computers at the branch offices would cause immense congestion on the connection. Use the network boot referral system to minimize network traffic between the branch sites and the central office. Ron prestages each client computer and assigns the appropriate branch office server as the referral server for each. This ensures that the client downloads files and images from the local server, which minimizes traffic on the line between the offices.

Ron has two standard operating system configurations — one for the desktop computers and one for laptops that contains the sales presentations and drivers for projectors. Therefore, he builds two images: one with the desktop configuration, and one with the laptop configuration with no applications. He stores all the user data on one of the servers, so he can deploy Windows without preserving any existing data on the client computers.

These files automate the installation, so Ron does not need to be present at each computer during the installation. They also automatically install Microsoft Office and the line-of-business application that the company uses for package tracking. He uses the Windows Deployment Services management tools to associate the unattend files with the images. Next, Ron configures Windows Deployment Services so when a computer is restarted, it will boot from the network automatically and deploy the appropriate image without requiring the users to press F After the image is applied to each computer, the computer is automatically joined to the corporate domain and restarted.