PIRATED 20130921 0047

PIRATED 20130921 0047

NOTE: This content appears to have been plagiarized. Please leave a comment or email tnwiki at Microsoft (with a link to this article) if we are mistaken. The content was pulled from the following source:
  • "Mastering Windows 7 Deployment"
    Published by Aidan Finn, Darril Gibson, Kenneth van Surksum (SYBEX)
    http://books.google.de/books?id=5rJyLpS0nD0C&pg=PT265&lpg=PT265&dq=%22WDS+is+an+operating+system+deployment+solution+%22&source=bl&ots=CwP28k9god&sig=YR6v1_3JCDPpZ6WfU6LZSKfqqNc&hl=en&sa=X&ei=RtA8UrO8Oeqw0wXC14DQBA&ved=0CC4Q6AEwAA#v=onepage&q=%22WDS%20is%20an%20operating%20system%20deployment%20solution%20%22&f=false
The community rules state:
  • "Someone else has relevant content and you want to help them share it with the world. It's a nice thought, but do not copy other people's content to the Wiki, even if the owner said it was OK."






WDS is an operating system deployment solution that allows new bare-metal or existing computers to boot up from a network-stored Windows PE boot image, run a WDS client, choose a Windows Imaging (WIM)-based installation image, and install it.

That installation image must be created. You can use any of the solutions that create a WIM file, such as WAIK, or event use the default installation images on the Windows 7 media. WDS, much like cloning solutions such as Ghost, will allow you to capture an image from a generalized template computer. The new WIM file will be captured and stored on the WDS server, available to be deployed to other computers.


Boot Up with PXE


WDS depends on a technology that was created by Intel called Pre-boot Execution Environment (PXE). PXE allows computers to boot up using their network cards instead of a hard disk, floppy drive, or USB device. The computer that is to be captured or deployed is booted up using PXE. This requires the following:

The hardware is capable of supporting a PXE boot --> The computer must have a network card that is Net PC/PC98 compliant. It is the network card that is providing the boot-from network functionality. Computers have provided this support for many years.

The BIOS is configured to allow a PXE boot --> Your computer may have the option for booting from PXE disabled. You will see a prompt to press a key, such as F12, to boot from the network during the machine’s POST, if it is enabled. You should enable the boot from network option in the BIOS of any machine that you will deploy operating system images to using WDS.



The computer will start the PXE client. This will broadcast on the network. It requires responses from two services:

  • DHCP --> The computer is booting up using bare metal (it does not any operating systems installed). It will require a network configuration to communicate with the WDS server. This IP configuration will be provided by a DHCP server. This means that the broadcast domain (or subnet) that the client is booting up on must have a DHCP server that can respond to the client with a valid IP configuration for the current network.

  • PXE Server --> The PXE is a component of the WDS server. It is made up of one (by default) or more (provided possibly by third parties) providers that will respond to PXE clients. This will initiate the next phase of the bootup process.

The PXE server is what is interesting here. The broadcast sent by the client is in the form of a DHCPDISCOVER packet with PXE options on UDP port 67.

Note: It should be noted that UDP 4011 will also be used if the PXE server is running on the same server as DHCP because both services cannot share UPD 67.



This packet will be ignored by DHCP servers. The PXE server will respond with a DHCPOFFER including the following:

  • The IP address of a PXE boot server
  • A PXE boot menu
  • A timeout for the user to respond to the prompt



As said before, when a PXE client starts, it requires two things: an IP address and a Network Boot Program (NBP). The PXE client sends out a DHCP Discover; if the DHCP server and WDS server are on separate boxes, the PXE client receives two offers from the network: One for an IP address:



One for an NBP (the NBP offer would have no IP address):



The client accepts one of the IP address offers it received. Ideally, the PXE client accepts an offer that has both an IP address and a NBP, but if this is not offered, it instead accepts the IP address-only offer:





After it has the IP address, it sends out a new DHCP request for a NBP, which uses its new IP address and responds with a boot to use:





The PXE client then uses TFTP to download the specified NBP, and the client is prompted to press F12 to network boot (unless the NBP was changed to the non-F12 version).

The story is slightly different if the WDS server is also a DHCP server. In that case, the offer received by the client contains both an IP address and a NBP, which the client requests and is subsequently acknowledged by the server. At that point, the PXE client begins the NBP download.













If DHCP and WDS are on separate boxes, no configuration is required. WDS was designed to work off separate boxes for the IP and NBP. If WDS does exist on the same box as a DHCP server, some changes are required.


Downloading a Boot Image Using TFTP


The PXE boot menu, which is configured using the settings in the PXE server DHCPOFFER, will be presented to the user sitting at the client machine. A list of possible boot images will be presented if there is more than one suitable boot image. The process will continue when the user sitting at the client responds to the boot menu.

Windows Deployment Services displays a menu that enables users to select a boot image. This menu is always automated, and when there are multiple boot images, one will be selected by default when the time-out value expires (which is configurable by using the bcdedit tool). However, if there is only one boot image available to the client computer, it will be selected immediately.

The PXE client will use TFTP to download the boot image that you have chosen from the WDS server. TFTP is the network protocol used for downloading all files during network boots, including the boot image.

TFTP is an inherently slow protocol because it requires one ACK (acknowledgment) packet for each block of data that is sent. The server will not send the next block in the sequence until the ACK packet for the previous block is received. As a result, on a slow network, the round-trip time can be very long. However, this is improved in Windows Server 2008 because of TFTP windowing. TFTP windowing enables you to define how many data blocks it takes to fill up a window. The data blocks are sent back to back until the window is filled, and then an ACK packet is sent. The result is fewer ACK packets and much faster download times for the client.

Using the BCDEdit command-line tool, you can change the TFTP block size and the TFTP window size to optimize performance in your environment.


Booting Up the WDS Client


The boot image will download and boot up. The WDS client will now start up. This will allow the user to authenticate with the WDS server. If the WDS client is configured to deploy an image, then the user will select an installation image to be downloaded by the WDS client and installed.

Leave a Comment
  • Please add 4 and 1 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Carsten Siemens edited Revision 13. Comment: Pirated Content - see my comment

  • Richard Mueller edited Revision 12. Comment: Removed (en-US) from title, added tag

Page 1 of 1 (2 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Richard Mueller edited Revision 12. Comment: Removed (en-US) from title, added tag

  • Carsten Siemens edited Revision 13. Comment: Pirated Content - see my comment

  • NOTE: This article was reported as Pirated/Plagiarized Content (content you didn't write) and will be removed. Please do not steal content from others. If you feel we are mistaken, please leave a comment or email tnwiki at Microsoft with a link to this article and with clear and detailed reasons why you own the content or have explicit permission from the author.

    Content was taken from: "Mastering Windows 7 Deployment"

    Published by Aidan Finn, Darril Gibson, Kenneth van Surksum (SYBEX)

    books.google.de/books

Page 1 of 1 (3 items)