none
WDS RRS feed

Answers

  • Step 1. Setup and configure active directory

    Click on Start and choose Server Manager, scroll down to Roles Summary and choose Add Roles.

    When the wizard appears click next

    As WDS needs the folllowing:-

    Active Directory Domain Services, DHCP, DNS, we will add the following role first:-

    Active Directory Domain Services

    We must install this role first before continuing to add the other roles, so lets select it and click on next.

    We will then be informed that installing AD requires us to run dcpromo.exe afterwards to make the server a fully functional domain controller. Click install to continue.

    click close to continue

    Once done the server manager will list our ADDS service with a red X beside it, click on it to run Dcpromo.exe.

    This will open up the Roles section of Server manager, and we'll see a summary which says This server is not yet running as a domain controller. Run the Active Directory Domain Services Installation Wizard (dcpromo.exe).

    Click on the blue text to continue.

    This will start the Active Directory Domain Services Installation Wizard. Click on next to continue.

    Next we will get a screen telling us that older versions of Windows (pre Vista Sp1 ....) may have problems with a bunch of things including Windows Deployment Services

    click next to continue

    Now we get to choose what type of domain we will setup, and for the purpose of this lab, we will select the second option, Create a new domain in a new forest.

    next we are prompted for the fully qualified domain name of the forest root domain (eg: WDSServer.contoso.com)

    after clicking next the wizard will check the validity of the fqdn,

    next we get to choose the forest functional level, click the drop down menu and select Windows Server 2008 from the three choices (Windows 2000, Windows Server 2003, Windows Server 2008).
    As this is only a test lab, we are not concerned that we can only add Windows 2008 or later servers to this forest.

    Clicking next will give some addtional options, leave them as they are (DNS Server selected) and click on Next again.

    if you get a warning about dynamically assigned ip addresses ignore it (choose yes),

    you will most likely get another DNS warning if like me you don't have a Windows DNS server in the forest. Click yes to continue.

    Next we are asked where to store the AD database, logfiles and sysvol, stay with the defaults and click next.

    and we are then prompted to set the Directory Services restore mode administrator account password

    finally we get a summary of our actions

    click next to get started

    after a while you should see the AD wizard complete. Click Finish

    you'll be prompted to restart, so please go ahead and click on Restart Now.

    Step 2. Add the DHCP role

    After completing Step 1, you now should see that Active Directory Domain Services and DNS server are installed (you can verify this in Server Manager, Roles, Roles Summary).

    Now that we are in server manager lets click on Add roles again followed by next.

    Select DHCP Server and click next.

    Review the information about DHCP server...

    and if you have more than one network card in your Windows 2008 server, select the one which will be handing out ip's (in my case that is 192.168.3.1), I removed the tick from the other network card listed

    next you will need to clarify which DNS server ip address to listen to, I changed it from my second nic's ip address 192.168.3.1, clicking on Validate will verify that it's ok

    enter your WINS settings, I went with the default and clicked next,

    next we have to input our DHCP server scope options, to do this click on Add

    enter your scope settings

    click ok and your DHCP scope will now be listed

    click next and you'll get IPV6 options, I chose to disable this as I'm not using IPv6 yet

    next we are asked about DHCP credentials for the AD DS, I stayed with the default,

    and then we will see a summary of our actions and choices for the DHCP server role

    clicking on Install will apply these settings and after some time you should hopefully see the following:-

    Step 3. Add the WDS role:-

    In Server Manager, Highlight and select Windows Deployment Services and click next.

    you will get an information screen which has some info including the following:-

    Click next and notice the two role services listed, Deployment Server and Transport Server, make sure they are both selected and click next to continue.

    view the summary and click install to install the WDS role...

    if you check server manager under roles you should now see the WDS role added.

    Step 4. Configure the Windows Deployment Services gui (mmc snap in)

    Click on Start/All Programs/Administrative tools/Windows Deployment Services.

    at this point we can see that WDS is not configured yet, so let's do that now.

    right click on the server name in the left pane and choose Configure Server

    at the welcome page click next

    change the remoteinstall path from the default C:\RemoteInstall to D:\RemoteInstall

    I put a checkmark in each of the DHCP options then clicked next

    I then chose to respond to all known and unknown computers (by default it's set to Do not respond to any)

    clicking on Finish applies these settings

    when done, you'll be told that the configuration is complete and that you can now add images to the WDS server, click on Finish (again).

    Step 5. Adding boot.wim and install.wim


    Note: You should use only the boot.wim file from the Windows Server 2008 DVD. If you use the boot.wim file from the Windows 7 DVD, Folder \Source\boot.wim \Source\install.wim

    The Windows Deployment Add image wizard will appear, insert your Windows 2008 Server DVD and click Browse, select the sources folder on the Windows 2008 DVD and then click next


    you'll be prompted to create a new image group, lets call it ImageGroup1 (the default name, you can change it later to Windows Server 2008 or Windows Vista Sp1 or whatever...).
     

    review your settings and click next when ready

    After a long while, the selected images will be added to the WDS server

    click finish and review the WDS server as it is now

    in the Boot Images pane, you should see Microsoft Windows Longhorn Setup (x86) and this is the original boot.wim file from the Windows 2008 Server DVD, please note that this is the default description name of the image, you could change it when addint the boot.wim image to something more descriptive

    In the Install Images pane, we can see the six available images from the Windows 2008 Server DVD, these are based upon the install.wim file on the DVD.

    you can now PXE boot your client computers to the Windows 2008 WDS server.


    Kalpesh Patel

    Wednesday, June 20, 2012 9:10 AM

All replies

  • Step 1. Setup and configure active directory

    Click on Start and choose Server Manager, scroll down to Roles Summary and choose Add Roles.

    When the wizard appears click next

    As WDS needs the folllowing:-

    Active Directory Domain Services, DHCP, DNS, we will add the following role first:-

    Active Directory Domain Services

    We must install this role first before continuing to add the other roles, so lets select it and click on next.

    We will then be informed that installing AD requires us to run dcpromo.exe afterwards to make the server a fully functional domain controller. Click install to continue.

    click close to continue

    Once done the server manager will list our ADDS service with a red X beside it, click on it to run Dcpromo.exe.

    This will open up the Roles section of Server manager, and we'll see a summary which says This server is not yet running as a domain controller. Run the Active Directory Domain Services Installation Wizard (dcpromo.exe).

    Click on the blue text to continue.

    This will start the Active Directory Domain Services Installation Wizard. Click on next to continue.

    Next we will get a screen telling us that older versions of Windows (pre Vista Sp1 ....) may have problems with a bunch of things including Windows Deployment Services

    click next to continue

    Now we get to choose what type of domain we will setup, and for the purpose of this lab, we will select the second option, Create a new domain in a new forest.

    next we are prompted for the fully qualified domain name of the forest root domain (eg: WDSServer.contoso.com)

    after clicking next the wizard will check the validity of the fqdn,

    next we get to choose the forest functional level, click the drop down menu and select Windows Server 2008 from the three choices (Windows 2000, Windows Server 2003, Windows Server 2008).
    As this is only a test lab, we are not concerned that we can only add Windows 2008 or later servers to this forest.

    Clicking next will give some addtional options, leave them as they are (DNS Server selected) and click on Next again.

    if you get a warning about dynamically assigned ip addresses ignore it (choose yes),

    you will most likely get another DNS warning if like me you don't have a Windows DNS server in the forest. Click yes to continue.

    Next we are asked where to store the AD database, logfiles and sysvol, stay with the defaults and click next.

    and we are then prompted to set the Directory Services restore mode administrator account password

    finally we get a summary of our actions

    click next to get started

    after a while you should see the AD wizard complete. Click Finish

    you'll be prompted to restart, so please go ahead and click on Restart Now.

    Step 2. Add the DHCP role

    After completing Step 1, you now should see that Active Directory Domain Services and DNS server are installed (you can verify this in Server Manager, Roles, Roles Summary).

    Now that we are in server manager lets click on Add roles again followed by next.

    Select DHCP Server and click next.

    Review the information about DHCP server...

    and if you have more than one network card in your Windows 2008 server, select the one which will be handing out ip's (in my case that is 192.168.3.1), I removed the tick from the other network card listed

    next you will need to clarify which DNS server ip address to listen to, I changed it from my second nic's ip address 192.168.3.1, clicking on Validate will verify that it's ok

    enter your WINS settings, I went with the default and clicked next,

    next we have to input our DHCP server scope options, to do this click on Add

    enter your scope settings

    click ok and your DHCP scope will now be listed

    click next and you'll get IPV6 options, I chose to disable this as I'm not using IPv6 yet

    next we are asked about DHCP credentials for the AD DS, I stayed with the default,

    and then we will see a summary of our actions and choices for the DHCP server role

    clicking on Install will apply these settings and after some time you should hopefully see the following:-

    Step 3. Add the WDS role:-

    In Server Manager, Highlight and select Windows Deployment Services and click next.

    you will get an information screen which has some info including the following:-

    Click next and notice the two role services listed, Deployment Server and Transport Server, make sure they are both selected and click next to continue.

    view the summary and click install to install the WDS role...

    if you check server manager under roles you should now see the WDS role added.

    Step 4. Configure the Windows Deployment Services gui (mmc snap in)

    Click on Start/All Programs/Administrative tools/Windows Deployment Services.

    at this point we can see that WDS is not configured yet, so let's do that now.

    right click on the server name in the left pane and choose Configure Server

    at the welcome page click next

    change the remoteinstall path from the default C:\RemoteInstall to D:\RemoteInstall

    I put a checkmark in each of the DHCP options then clicked next

    I then chose to respond to all known and unknown computers (by default it's set to Do not respond to any)

    clicking on Finish applies these settings

    when done, you'll be told that the configuration is complete and that you can now add images to the WDS server, click on Finish (again).

    Step 5. Adding boot.wim and install.wim


    Note: You should use only the boot.wim file from the Windows Server 2008 DVD. If you use the boot.wim file from the Windows 7 DVD, Folder \Source\boot.wim \Source\install.wim

    The Windows Deployment Add image wizard will appear, insert your Windows 2008 Server DVD and click Browse, select the sources folder on the Windows 2008 DVD and then click next


    you'll be prompted to create a new image group, lets call it ImageGroup1 (the default name, you can change it later to Windows Server 2008 or Windows Vista Sp1 or whatever...).
     

    review your settings and click next when ready

    After a long while, the selected images will be added to the WDS server

    click finish and review the WDS server as it is now

    in the Boot Images pane, you should see Microsoft Windows Longhorn Setup (x86) and this is the original boot.wim file from the Windows 2008 Server DVD, please note that this is the default description name of the image, you could change it when addint the boot.wim image to something more descriptive

    In the Install Images pane, we can see the six available images from the Windows 2008 Server DVD, these are based upon the install.wim file on the DVD.

    you can now PXE boot your client computers to the Windows 2008 WDS server.


    Kalpesh Patel

    Wednesday, June 20, 2012 9:10 AM
  • Installing Windows Deployment Services

    1. Ensure that you are a Domain Administrator.

    2. Click Start, click Administrative Tools, and then click Windows Deployment Services. 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. In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.

    4. Right-click the server, and then click Configure Server (Note that the screenshots included in this document are from Windows Server 2008).

      241e9dfc-71c4-4305-8ee2-698d236ab51c
    5. Follow the instructions in the wizard.

    6. When the configuration is completed clear the Add images to Windows Deployment Services now check box and then click Finish.

    Now that you have configured the server, you will need to add images. For instructions, see the next section.

    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.wim file on the product DVD from one of the following operating systems:

      • Client: Windows Vista (with at least Service Pack 1 (SP1)) or Windows 7
      • Server: Windows Server 2008 or Windows Server 2008 R2
      You can also use custom boot images that you have created using the Windows AIK (for example, for diagnostic testing).
    • Install images. Install images are the operating system images that you deploy to the client computer. You can use the Install.wim file from the product DVD to deploy images for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. For operating systems released prior to Windows Vista, you must create a custom install image. For instructions, see Creating Custom Install Images and Deploying Earlier Versions of Windows.

    To add the Install.wim from the product DVD, use the following procedures.

    1. In the Windows Deployment Services MMC snap-in, right-click the Install Images node, and then click Add Install Image.

      b6f3361d-af95-4b2a-a6c9-b8c976fd741b
    2. Specify a name for the image group, and then click Next.

      405ac2d0-d2c7-4325-9375-b650b2c29786
    3. Browse to select the default install image (Install.wim), which is located in the \Sources folder of the product DVD, and then click Open.

    4. To add a subset of the images included in the Install.wim file, clear the check boxes for the images that you do not want to add to the server. You should add only the images for which you have licenses.

    5. Follow the instructions in the wizard to add the images.

    6. Click the image group to verify that the correct images were added.

      c4df1536-a42a-4e70-aa96-efe2f08216df
    7. Repeat this procedure to add any additional install images.

    1. In the left pane of the Windows Deployment Services MMC snap-in, right-click the Boot Images node, and then click Add Boot Image.

      b58b0018-e7a6-46cb-a6e7-c525322242c7
    2. Browse to choose the default boot image (Boot.wim) on the product DVD, located in the \Sources folder.

    3. Click Open and then click Next.

    4. Follow the instructions in the wizard to add the image.

    5. Repeat this procedure to add any additional boot images. When multiple boot images are available to client computers, clients will be presented with a boot menu that displays the boot images. For more information, see Managing the Boot Menu (http://go.microsoft.com/fwlink/?LinkId=115305).

    6. If you want to modify any of the settings of the server, right-click the server in the MMC-snap in, and click Properties.

      8d9ceb1c-d610-4d73-a4f6-89029c1ac4fe
    7. Now that you have at least one boot and install image on the server, you can perform a PXE boot on a client computer to install an operating system using the steps in the following section.

    After you have at least one boot and one install image on the server, you can deploy an install image.

    • The client computer must be capable of performing a PXE boot.
    • Your user account must be a member of the Domain Users group.
    • The client computer must have at least 512 MB of RAM, which is the minimum amount of RAM for using Windows PE.
    • The client must meet the system requirements for the operating system of the install image.

    To perform a PXE boot on a computer to install an image, use the following procedure.

    1. Configure the BIOS of the computer to enable PXE booting, and set the boot order so that it is booting from the network first.

    2. Restart the computer, and when prompted, press F12 to start the network boot.

    3. 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.)

    4. Follow the instructions in the Windows Deployment Services user interface.

    5. When the installation is completed, the computer will restart and Setup will continue.

    This section applies to you if want to upgrade your server running Windows Server 2003 with SP1 or SP2. We recommend that you perform a clean installation whenever possible. However, if you decide that you want to upgrade your server, you should read the upgrade guidance in Upgrading to Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=110832) to ensure that your upgrade is successful.

    When moving an existing RIS infrastructure to Windows Deployment Services, we recommend that you upgrade all of your servers to Windows Deployment Services. The three server modes on Windows Server 2003 and the ability to convert RIPREP images enable you to transition seamlessly from RIS to Windows Deployment Services. We do not recommend installing Windows Deployment Services on new servers in your environment while continuing to maintain the existing RIS servers—because it requires additional hardware and administrative overhead. Having two PXE servers that are configured differently on the same network segment can lead to unpredictable results.

    There are three modes of operation for Windows Deployment Services in Windows Server 2003: Legacy, Mixed, and Native. Your server must be in Native mode to upgrade to Windows Server 2008 or Windows Server 2008 R2. Your upgrade will be blocked if RIS is configured, or if your server is in Legacy or Mixed mode. To determine which operating mode the server is currently in, run the command WDSUTIL /get-server /show:config.

    To determine how to upgrade, consider which of the following scenarios applies to you:

    • If RIS is currently running on the server but you do not have Windows Deployment Services installed, you must install it before upgrading. Windows Deployment Services is included in the Windows AIK and Windows Server 2003 SP2. For more information about how to install and configure Windows Deployment Services, see the Step-by-Step Guide for Windows Deployment Services in Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=94643). Then use the following procedures to switch from Legacy mode (the default setting) to Native mode.
    • If RIS was installed on the server when you installed Windows Deployment Services, it will be in either Legacy or Mixed mode; you will need to change it to Native mode before upgrading.
    • If RIS was not installed on the server when you installed Windows Deployment Services, the server will be in Native mode and therefore ready to be upgraded.

    Use one or both of the following procedures to change the server mode to Native.

    1. Initialize the server by doing one of the following:

      • Using the MMC snap-in. On the Start menu, click Administrative Tools, and then click Windows Deployment Services. Right-click the server, and then select Initialize Server.
      • Using WDSUTIL. Run the command WDSUTIL /Initialize-Server /RemInst:C:\RemoteInstall (assuming that C:\RemoteInstall is the location of your REMINST shared folder).
    2. When the process is completed, use the following procedure to change the server mode from Mixed to Native.

    1. Retire your RISETUP and RIPREP images, or convert them to .wim format. To retire them, just delete the images. If you want to convert them, you have two options:

      • Convert them offline (for RIPREP images only). To do this right-click the Legacy Images node, right-click the image and click Convert to WIM.
      • Deploy and recapture them by using the Image Capture Wizard (for RIPREP or RISETUP images). For instructions, see Creating Custom Install Images.
    2. Run the command WDSUTIL /Set-Server /ForceNative.

    3. When the process is completed, the server is ready to be upgraded. For more information about upgrading, see Upgrading to Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=110832).

    To uninstall the Windows Deployment Services component, you can click Remove Roles in Server Manager, or run ServerManagerCmd -remove WDS at an elevated Command Prompt window.

    You can also uninitialize the server if you want to reset the server to a nonconfigured state but you do not want to uninstall Windows Deployment Services. This is helpful if you want to start over but would like to retain existing settings. For example, if you want to move the RemoteInstall folder (perhaps you got a new hard disk for your server and wanted to move this folder to it), you would uninitialize the server, copy the folder to the new location, and then reinitialize the server by using the new path. To uninitialize the server, run the command WDSUTIL /uninitialize-server in an elevated Command Prompt window.

    For instructions on performing more advanced tasks, see the following topics:

    • Performing Multicast Deployments. In order to deploy an image using multicasting instead of unicasting, you must first create a multicast transmission. Multicast transmissions make the image available for multicasting, which enables you to deploy an image to a large number of client computers without overburdening the network.
    • Managing and Deploying Driver Packages. If you have Windows Server 2008 R2, you can deploy driver packages to client computers as part of an installation, and you can add driver packages to boot images prior to deployment.
    • Creating Custom Install Images. You can use Windows Deployment Services to create custom install images using capture images, which provide an alternative to the command-line utility, ImageX.exe. To create a custom image, you create a capture image, prepare a reference computer using Sysprep, and then capture the operating system using the Image Capture Wizard.
    • Performing an Unattended Installation. You can automate the entire deployment using two unattend files: one for the Windows Deployment Services user interface screens, and one for the later phases of Setup.
    • Creating Discover Images. A discover image is a type of boot image that you can use to install an operating system on a computer that is not capable of network booting using the Pre-Boot Execution Environment (PXE).
    • Proposed as answer by Fuat Ceylan Thursday, August 9, 2012 6:31 PM
    Wednesday, August 8, 2012 4:19 PM