PIRATED 20130921 0039

PIRATED 20130921 0039

NOTE 1: This article is a duplicate of The History of Windows Deployment Services (WDS) which is also pirated.

NOTE 2: 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)
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."

Microsoft provided a basic network deployment solution in Windows 2000 Server and Windows Server 2003 called Remote Installation Services (RIS). It was difficult to manage and slow. As a result, many organizations chose not to use it, preferring third-party imaging solutions that had to be purchased.

The story changed starting with the release of Service Pack 2 for Windows Server 2003. It introduced Windows Deployment Services (WDS) as a replacement for the RIS role. The new network-based operating system deployment solution used boot image and installation images. Client computers used a feature of the hardware to download a boot image and then pick and install an installation image. WDS has matured with the release of Windows Server 2008 and Windows Server 2008 R2. It can be used as a stand-alone solution where administrators can install an image containing the operating system, applications, and their configurations. It can also be used to extend the functionality of the Microsoft Deployment Toolkit (MDT). MDT also uses boot images, and you can store them on a WDS server to boot up client computers without any media. Microsoft System Center Configuration Manager also makes use of WDS to allow computers to boot up on the network without any media.

WDS provides a solution where you can boot up a computer on the network using a boot image that is stored on the WDS server. An administrator or user can log into a WDS client and select an installation image to be deployed. WDS administrators can add device drivers to the WDS server so that they can automatically installed using Plug and Play during an image installation. WAIK unattended installation answer files can be used to completely automate the installation of the Windows image. There is even support for multicast deployments in Windows Server 2008 and Windows Server 2008 R2. This is everything you could ask for in a network-based operating system deployment solution. And you get all of this without having to spend anything extra on licensing.
Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
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.
  • Carsten Siemens edited Original. Comment: Duplicate Article of social.technet.microsoft.com/.../11543.the-history-of-windows-deployment-services-wds.aspx

  • Carsten Siemens edited Revision 1. 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)


Page 1 of 1 (3 items)