Tuesday, 18 June 2013

Complete guide to WDS (Windows Deployment Server) in Windows Server 2012

Setting up WDS Server in Windows Server 2012



The following are requirements for installing this role, depending on whether you choose the default installation (both Deployment Server and Transport Server), or only the Transport Server role service


  • Active Directory Domain Services (AD DS): A Windows Deployment Services server must be a member of an Active Directory Domain Services (AD DS) domain or a domain controller for an AD DS domain.
    The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services.

    NOTE: AD DS is not required if the WDS server is configured in Standalone mode.
    • DHCP: You must have a working Dynamic Host Configuration Protocol (DHCP) server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.
    • DNS: You must have a working Domain Name System (DNS) server on the network before you can run Windows Deployment Services.
    • NTFS volume: The server running Windows Deployment Services requires an NTFS file system volume for the image store.
    • Credentials: To install the role, you must be a member of the Local Administrators group on the server. To initialize the server, you must be a member of the Domain Users group.


    Install Windows Deployment Services

       
    1. Sign in to the server as a member of the local Administrators group.
    2. Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
    3. Click Manage.
    4. Click Add roles and features, click Next.



    1. On the Before you begin page of the Add Roles and Features Wizard, click Next.


    1. On the Select installation type page, click Role-based or feature-based installation, and then click Next.

    1. On the Select destination server page, select the appropriate server, and then click Next. The local server is selected by default.
    2. On the Select server roles page, scroll down and then select the Windows Deployment Services check box. Click Next.

    1. Remote Server Administration Tools are required to manage this feature. Select Include management tools (if applicable). Click Add Features. Click Next.
    2. On the Select features page, click Next.

    1. On the Select role services page, select the role services to install for Windows Deployment Services. If you wish to install both the Deployment Server and Transport Server, leave these role services selected. Click Next.
    2. On the Confirm installation selections page, click Install.

    1. Windows Deployment Services will now be added to the server. Installation progress will now be illustrated in the Add Roles and Features Wizard.

    Steps for configuring Windows Deployment Services for Standalone Server


    1. Log on to the server as a member of the local Administrators group.
    2. Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
    3. Click Tools, and then click Windows Deployment Services to launch the Windows Deployment Services MMC-snap (or console).


    1. In the left pane of the Windows Deployment Services MMC snap-in, expand the list of servers.

    1. Right-click the desired server, click Configure Server.





    1. On the Before you begin page, click Next.


    1. On the Install options page, choose Integrated with Active Directory.
    2. On the Remote Installation Folder Locations page, choose the default path or enter your own path to the remote installation folder. Click Next.

    Note: If your server is running as a DHCP Server, you will see the Proxy DHCP Server page.
    Select Do not listen on DHCP and DHCPv6 ports and Configure DHCP options for Proxy DHCP. Click Next.

    1. On the PXE Server Initial Settings page, choose desired option to define which client computers this server will respond to. Click Next. This will complete the configuration of Windows Deployment Services.
    2. When the configuration is completed, click Finish.

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



    Steps for Adding Images

    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 from the installation media (in the \Sources folder). The Boot.wim file contains Windows PE and the Windows Deployment Services client.
    • Install images. Install images are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the installation media (in the \Sources folder), or you can create your own custom image


    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.

    1. Browse to choose the default boot image (Boot.wim) on the Windows installation media, located in the \Sources folder.
    2. Click Open, and then click Next.


    1. On the Image Metadata page, enter the desired image name and description. Click Next.

    1. On the Summary page, click Next


    To add the Install images

    1. In the left pane of the Windows Deployment Services MMC snap-in, right-click the Install Images node and then click on Add Image Group and create a group name


    1. Open the RemoteInstall folder created in Step No.8 of Configuring WDS



    1. Navigate to the Images, Image Group name and paste the customized install.wim images which you have created for deploying the operating system


    1. Now open the WDS console and you can see all the images appearing under the Image Group section as shown


    1. Right click on any Image name and go to Properties, here you can name your Image and give description to the image. Click on Apply and OK

    Installing an Operating System on Machines using WDS


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

    1. At the Install Windows page, choose your Locale and Keyboard or Input Method. Click Next.
    2. At the Connect to Your WDS Server authentication dialog, enter your local user account and password. Click OK.
    3. 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.
    4. If prompted at the Where do you want to install Windows page, select the partition you wish to install the operating system on. Click Next.
    5. When the installation is completed, the computer will restart and Setup will continue.

    Steps for creating a Capture Image


    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 .wim file.
    • You can also create media (a CD, DVD, USB drive, or other type of media) that contains a capture image, and then boot a computer from the media. These images provide an alternative to the command-line utility, ImageX.exe. Except in advanced scenarios, you can create a capture image by using the Boot.wim file from the Windows installation media
    1. In the Windows Deployment Services MMC snap-in, expand the Boot Images node.
    2. Right-click the image to use it as a capture image. In most cases, you can just use the Boot.wim file from the installation media.
    3. Click Create Capture Image.
    4. 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. Click Next.
    5. Allow the Create Capture Image Wizard to complete.
    6. Tick Add Image to the Windows Deployment Server now. Click Next
    7. Enter the location of the Windows Image file that contains the images. Click Next.
    8. Enter your Image Name and Image Description. Click Next.
    9. On the Summary page, click Next.
    10. Click Finish.

    Capture an sysprep machine using WDS

    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 .wim file. After that, you can deploy the .wim file to a computer.
    1. Create a reference computer (install the operating system, applications, and make any other changes that you want).
    2. Ensure that you have the correct version of Sysprep.exe on the computer.
    3. At a command prompt on the reference computer, change folders to \Windows\System32\Sysprep or the folder that contains Sysprep.exe and Setupcl.exe.
    4. Type one of the following:
      • On computers running Windows 8, Windows 7, Windows Vista and Windows Server 2012, Windows Server 2008 R2 and Windows Server 2008, run the command sysprep /oobe /generalize /reboot. If you prefer, you can also use the Sysprep graphical user interface by double-clicking Sysprep.exe.
      • On computers running Windows XP, run sysprep -mini –reseal -reboot.
    5. When the computer restarts, perform a network boot on the computer by pressing F12.
    6. In the boot menu, select the capture boot image that you created in the preceding procedure, and then press ENTER.
    7. You will be presented with the Windows Deployment Services Image Capture Wizard. Click Next.
    8. On the Directory to Capture page, select Volume to capture, enter your Image name and Image description. Click Next.
      *Important
      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.
      1. 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 .wim file name extension, and then click Save. Note that this location can be a mapped network drive.
        *Important
        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.
        1. Select the Upload Image to a Windows Deployment Services check box.

        1. 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.
        2. Select your Image Group Name. Click Next. The wizard will now complete and create a custom installation image and store it in the Windows Deployment Services store.
        3. Click Finish

        Steps for creating a Discover Image


        Why Discover Image?
        • If you have a computer that is not PXE enabled, you can create a discover image and use it to install an operating system on that computer. Otherwise, you can skip this section.
        • When you create a discover image and save it to media (a CD, DVD, USB flash drive, or other type of media), you can then boot a computer to the media.
        The discover image on the media locates a Windows Deployment Services server, and the server deploys the install image to the computer. You can configure discover images to target a specific Windows Deployment Services server. This means that if you have multiple servers in your environment, you can create a discover image for each one, and then name them based on the name of the server
        Required items:
        • A 1GB USB Flash drive or greater is required for this recipe
        • The Windows 8 RTM ISO File or DVD (ISO Preferred)
        • A PC Running Windows 8 Release Preview or RTM
        1. In the Windows Deployment Services MMC snap-in, expand the Boot images node.
        2. Right-click the image you want to use as a discover image.
        3. Click Create Discover Image
        4. In the Metadata and Locations page, enter your Image Name and Image Description. In the location and file name, click Browse and select the location for storing your discover boot image. Enter the name of your discover image. Optionally, enter the name of your Windows Deployment Services server that you want to respond when you boot a computer into this image. Click Next.
        5. Click Finish.
        1. Start an Administrative Command Prompt
        2. Type “cd \” and press Enter
        3. Type diskpart
        4. Follow the example below.  Please note you will need to discover which disk number belongs to your flash drive.  Observe the “List disk” command and use drive size to find which drive is your USB flash drive.
        5. Please use the below diskpart session as the your guide to preparing the USB flash drive

        DISKPART> list disk

         Disk ###  Status         Size     Free     Dyn  Gpt
         --------  -------------  -------  -------  ---  ---
         Disk 0    Online         1863 GB      0 B
         Disk 1    Online         3828 MB      0 B

        DISKPART> select disk 1
        Disk 1 is now the selected disk.

        DISKPART> clean
        DiskPart succeeded in cleaning the disk.

        DISKPART> create part primary
        DiskPart succeeded in creating the specified partition.

        DISKPART> select part 1
        Partition 1 is now the selected partition.

        DISKPART> format fs=fat32 quick label=WDSUSB
        100 percent completed
        DiskPart successfully formatted the volume.

        DISKPART> assign letter=u
        DiskPart successfully assigned the drive letter or mount point.

        DISKPART> exit
        Leaving DiskPart...

        1. Now you need to mount the Windows 8 ISO file (by right-clicking the ISO and saying “Mount”) or inserting the Windows 8 DVD.
        2. For this we will assume the DVD drive letter for this disc is E:
        3. Using the same command prompt window from diskpart you will be running a copy command to copy the needed files.
        4. Please note Drive letter U: is my USB Flash Drive and drive letter E: is the DVD drive or Mounted ISO file.
        5. Type into the Administrative Prompt: robocopy E:\ U:\ /E /S /XF Install.WIM /XF Boot.WIM
        6. Once this is done then browse to U:\sources\  and copy your WDS Dicscover WIM file into this folder
        7. Rename the WDS Discover WIM file in U:\sources\ to boot.wim
        8. Boot the client computer to the media. You may need to change the boot order in the client BIOS to do this. When the client boots to the media, your experience will be exactly the same as if you had booted to the network





        Setting up Multicast Transmission


        Multicast transmissions enable you to deploy an image to a large number of client computers without overburdening the network.
        When you create a multicast transmission, the image is sent over the network only once, which can drastically reduce the amount of network bandwidth that is used. Note that data is transferred only if clients request data

        • Routers that support multicasting.
        • At least one install image that you want to transmit on the server.
        • The Boot.wim file from the latest version of Windows Server (Windows Server 2012).
        1. Right click ‘Multicast Transmission’ and click Create Multicast Transmission

        1. Type a name and click Next

        1. Select the image that you want to transmit using multicasting and click Next


        1. Select Auto-Cast option and click Next

        1. Click Finish to complete the process
        2. We can check the status as below

        Note: We need to authorize the WDS server in DHCP for the clients to recognize. Step 25 and 26 describes the procedure
        1. Open your local DHCP server and right click the DHCP and select Manage authorized servers


        1. In the next window, click ‘Authorize’ and enter the IP of WDS server


        1. WDS server is ready for deployment



27 comments:

  1. When doing WDS do I need the dvd media iso mounted or does it store all files needed to deploy the image in the RemoteInstall folder?

    ReplyDelete
    Replies
    1. windows 7 key professional , windows 10 serial keys product key , key for win 7 home , genuine win 7 ultimate product key free , windows server 2008 standart key , product key for windows 7 professional , windows 7 key order , office 2016 registry purchase , sRTMPn

      office 2016 registry purchase

      cheap office 2013 key

      microsoft visio professional 2016 order

      cheap windows 10 product key sale

      Delete
  2. Thanks for this, has worked a treat!

    ReplyDelete
  3. There is noticeably much to experience this. I believe you made several well points in Features as well. http://www.lowhosting.com/justhost-review/

    ReplyDelete
  4. Do you have this has a pd file ?

    ReplyDelete
  5. if you need genuine office you can try this link, my office got here and works well,strongly recommend you, it is brilliant www.aakeys.com
    wish you good luck

    ReplyDelete

  6. Great writing post! Very helpful blog.Thanks for share
    windows development

    ReplyDelete
  7. Cannot get the usb to boot from, the machine now it's there and boots to it. but just sit there on a blinking cursor. When i open the usb drive, it show e folder. I moved the boot file to the source folder but still no luck help!

    ReplyDelete
  8. friends who was interested in windows can visit here, not oly key you can get, but problem you can solve www.facebook.com/Download-Microsoft-Office-Key-1530057303978560 really helpful

    ReplyDelete
  9. if you need genuine office you can try this link, my office got here and works well,strongly recommend you, it is brilliant www.instructables.com/id/How-to-Activate-Windows-7

    ReplyDelete
  10. For any kind of product keys, check out this site to get what you want: www.gankings.com. 100% working!!!

    ReplyDelete
  11. Office 2016 Product Key (http://www.windows10keysale.com)


    I want to thank Office 2016 Product Key here, she has won my business and I'll be posting my experience to you and others.
    My old computer crashed days ago. I had to buy a new computer. It costed me much.
    My budget was not much. To purchase a Office 2016 Product Key from MS was not enough. Then I went to Tomshardware, and one guy recommended Office 2016 Product Key (http://www.windows10keysale.com) to me. Their price did attract me. So I decided to try after several emails to Office 2016 Product Key . She was very patient and answered clearly to all my questions. I receved the key immediately after I sent {price} bucks. It worked perfectly. I was very very satisfied.
    I'll be buying from Office 2016 Product Key (http://www.windows10keysale.com) from now on as well.

    Office 2016 Product Key (http://www.windows10keysale.com)

    ReplyDelete
  12. windows 10 product key tool , windows 10 key sale , windows 10 product key facebook , windows 8.1 pro key buy , windows 10 activation software , microsoft outlook 2010 serial key , project professional 2010 key , windows 10 product key viewer , l9keRo

    buy office 2016 product key

    windows server 2012 r2 free

    rosetta stone french key sale

    ReplyDelete
  13. Great information...I got the super information...thank you for posting....
    Computer Hardware

    ReplyDelete
  14. Its like you read my mind! You seem to know so much about this, like you wrote the book in it or something.
    PC Server

    ReplyDelete
  15. Hello, good job. It is well explained and detailed. I just added this role and will perform the different steps. I just have a question regarding the Capture Image would it include all the application installed on that machine + different file, let say a new desktop image background or the sysprep would erase all of that ?

    ReplyDelete
    Replies
    1. It will keep all the applications plus the Desktop backgroud. You can also customize the Workstations Logo in the System Properties to company specific information. Sysprep only generalizes a machine which is anything which is User defined or user related, whatever we do is all computer specific information

      Delete
  16. Share with you a good site that you can get cheap product keys from there: www.vanskeys.com, all versions of windows keys and office keys can be found in that site.

    ReplyDelete
  17. Somebody who need windows key click: www.vanskeys.com to got. here i got a working key on my windows about activator. and after i used my windows works properly. hope it help you.

    ReplyDelete