Results 1 to 2 of 2

Thread: How to configure Windows Deployment Services

  1. #1
    Join Date
    Apr 2008
    Posts
    598

    How to configure Windows Deployment Services

    Windows Deployment Services

    Windows Deployment Services is a server role that enables you to remotely deploy Windows operating systems. You can use it to set up new computers by using a network-based installation. This means that you do not have to install each operating system directly from a CD or DVD. To use Windows Deployment Services, you should have a working knowledge of common desktop deployment technologies and networking components, including Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory Domain Services.

    Configure Windows Deployment Services
    1. On the Start menu, click Administrative Tools, and then click Windows Deployment Services.
    2. In the left pane of the Windows Deployment Services MMC snap-in, expand the server list. If there is not a server listed under the Servers node, right-click the Servers node and click Add Server to add the local computer.
    3. Right-click the server that you want to manage, and click Configure Server. If the server is not in the servers list, right-click the Servers node to add a server.
    4. At the Welcome page, click Next.
    5. At the Remote Installation Folder Location page, do one of the following:
      • If this is a new installation of Windows Deployment Services (that is, if the server has not been running RIS), click Next to accept the default location of C:\RemoteInstall.
      • If the server has been running RIS (that is, if you are moving from Legacy to Mixed modes) you should specify the location of your existing RemoteInstall folder. However, note that the location should not be on the system partition.
    6. If the Microsoft DHCP service is on the server that is being configured as a Windows Deployment Services server, set DHCP Option 60 to PXEClient and set Windows Deployment Services to "Do not listen on Port 67".
    7. On the PXE Server Initial Settings page, select how you want the server to respond to clients. Known client computers are computers that have been created (prestaged) in Active Directory before the operating system is installed.
    8. Click Finish to complete the configuration.
    9. Clear the Add images to Windows Deployment Services now check box, then click Finish.
    10. If you want to modify any of the settings of the server, right-click the server in the MMC-snap in, and clicking Properties.


    Known issues with configuring Windows Deployment Services
    • If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes.
    • If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the following:
      • (recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts).
      • Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com.
    Source: Microsoft

  2. #2
    Join Date
    Apr 2008
    Posts
    439

    Windows Deployment Services Benefits

    Windows Deployment Services provides the following benefits:
    1. Allows network-based installation of Windows operating systems, which reduces the complexity and cost when compared to manual installations.
    2. Supports mixed environments including Windows XP and Windows Server 2003 through Windows 7 and Windows Server 2008 R2.
    3. Uses standard Windows Setup technologies including Windows Preinstallation Environment (Windows PE), .wim files, and image-based setup.
    4. Transmits data and images by using multicast functionality.
    5. Allows you to create images of a reference computer using the Image Capture Wizard, which is an alternative to the ImageX tool.
    6. Allows you to add driver packages to the server and configure them to be deployed to client computers along with the install image. In addition, you can add driver packages (such as network adapter drivers, mass storage drivers, and bus drivers) to your Windows 7 and Windows Server 2008 R2 boot images.
    7. Allows you to deploy virtual hard disk (.vhd) images as part of an automated deployment.

Similar Threads

  1. How to configure Web application in Windows SharePoint Services 3.0
    By Christina 80 in forum Software Development
    Replies: 5
    Last Post: 12-03-2010, 04:41 AM
  2. How to configure WCF services using Configuration Files
    By Pollock in forum Operating Systems
    Replies: 3
    Last Post: 11-08-2009, 10:38 AM
  3. Naming a computer in Windows Deployment Services...
    By GANGSTA in forum Vista Setup and Install
    Replies: 2
    Last Post: 30-04-2008, 01:29 AM
  4. Replies: 0
    Last Post: 05-03-2008, 08:47 PM
  5. Windows Deployment Services does not start
    By Dennis van Leur in forum Windows Server Help
    Replies: 2
    Last Post: 17-05-2007, 04:13 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,710,835,683.82157 seconds with 16 queries