Windows deployment services transport

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.

He also configures the deployment so that when the computer restarts, the computer will not network boot unless F12 is pressed. This way, the computer then boots to the hard disk drive and finishes the installation process.

This prevents a boot loop, in which the computer would continue booting into Setup. When the installation is completed, the computer is ready for the user to log on. Shu Ito is the network architect for Wide World Importers, a large enterprise with 5, employees in offices all over the world. The major employee centers are in the United States and Germany, and there are 13 branch offices in other countries. Shu has five servers available to him in the U. The hubs are connected by T3 lines, and the other sites are connected by T1 lines.

All of the servers are hired on two-year leases. The servers in the German office and the branch sites are the responsibility of the local administrators. Currently, deployments at Wide World Importers are done by using RIS, and Shu wants to ensure that the existing computer building processes are preserved with the move to Windows Deployment Services.

In addition, it is important that each computer is deployed with an operating system in a language that is appropriate for the users in that country or region. Use multicast deployments to preserve bandwidth while deploying images to many computers concurrently. The vast majority of his deployments will be in English or German, so he creates Windows 7 or Windows 8.

Other languages will be installed by using external language packs, and applications will be downloaded by using Systems Management Server SMS.

After creating the images, Shu uploads the images and language packs to the Windows Deployment Services server. Shu authors unattend files with Windows SIM. Of the accounting computers used by Wide World Importers, are in the U.

Shu uses multicasting to deploy to the computers in the U. To do this, he creates a multicast transmission for the relevant image on his Windows Deployment Services server. To preserve the state and data on the previous computers, Shu uses the User State Migration Tool USMT to save all of the data and user configurations to a shared folder on the primary Windows Deployment Services server. Volume Activation VA provides the capability for volume licensing.

It does not apply to or interact with invoicing or billing processes. Multiple Activation Key activates the product on a system on a one-time basis. Volume Activation needs to be properly planned during the deployment process, since upgrades and changes will affect the volume licensing. Instead, the wdsutil command is used for managing the Windows Deployment Services server. See this article for more about MDT. The server must be a member of the local administrators group in order to perform the installation tasks and other server tasks required.

Prerequisites client : Able to do a PXE boot. RetrieveNamespaces Returns a collection of objects of the IWdsTransportNamespace interface that represent namespaces on the server that match specified criteria. RetrieveSessions Retrieves a collection of active transport sessions associated with this content.

StartTransmission Starts a transmission on a namespace. This method provides the means to change the running state of WDS transport services without changing their configuration. Terminate Terminates the transmission of this content by terminating all active sessions under the content and disconnecting any clients that are joined to them. WdsBpAddOption Adds an option to the packet. WdsBpCloseHandle Closes the specified handle.

WdsBpParseInitialize Receives a handle to the packet sent by the network boot program. WdsBpParseInitializev6 Receives a handle to the packet sent by the network boot program. WdsBpQueryOption Returns the value of an option from the parsed packet.

The handle is to the local copy of the image that's been transferred from the server to the client. WdsCliRegisterTrace Registers a callback function that will receive debugging messages. WdsTransportClientCompleteReceive Indicates that all processing on a block of data is finished, and that the multicast client may purge this block of data from its cache to make room for further receives.

WdsTransportClientQueryStatus Retrieves the current status of an ongoing or complete multicast transmission from the multicast client. WdsTransportClientReleaseBuffer Decrements the reference count on a buffer owned by the multicast client. WdsTransportClientShutdown Shuts down the multicast client. WdsTransportClientWaitForCompletion Blocks until either the multicast session is complete or the specified timeout is reached. WdsTransportProviderCompareContent Compares a specified content name and instance to an open content stream to determine if they are the same.

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.