Wdsclient ошибка связи с сервером служб развертывания windows

• 

  Have you updated your DHCP Scope to provide the Server Options for WDS?

  The settings should look similar to this:

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Have you updated your DHCP Scope to provide the Server Options for WDS?

  The settings should look similar to this:

  This is exactly what I was going to state. Check this on your DHCP server. BTW you’ll be so thankful when this does finally work for you. The amount of time you’ll save… 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Yes, I added the Boot server host name and the Bootfile name to the DHCP server. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  did you add the network card drivers to the share, and update it before you pushed it to WDS?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  kevinhughes2 wrote:

  did you add the network card drivers to the share, and update it before you pushed it to WDS?

  I’m not sure what you mean. I injected the drivers to the boot image before I made the capture image. The laptop I captured the install image from had fully installed and updated drivers. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Have you exported your Lite Touch PE boot image to the deployment share?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  1GuyITDept wrote:

  Have you exported your Lite Touch PE boot image to the deployment share?

  Yes, the boot images are saved to the REMINST share. 

  We have a Cisco firewall, that shouldn’t be blocking this internal traffic…right?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Is everything on the same subnet?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  1GuyITDept wrote:

  Is everything on the same subnet?

  Yes.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Ok. Check your WDS Server Properties (right click on server object) to make sure it will respond to all client requests.

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  1GuyITDept wrote:

  Ok. Check your WDS Server Properties (right click on server object) to make sure it will respond to all client requests.

  Yes, that is what I have it set to. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Is the WDS Server DHCP properties set correctly? The options should be left blank

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  1GuyITDept wrote:

  Is the WDS Server DHCP properties set correctly? The options should be left blank

  I had it like that before but I moved WDS to a DC with DHCP so I’m supposed to have those both checked to work. I get the same error either way. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  When I get the error and I bring up cmd prompt I can ping the server but if I try and ‘net view \server» I get «System error 5 has occurred. Access is denied.» Does that mean anything?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Well, it looks like I’ve got it working now. It appears the issue was with permissions. I had to add ‘everyone’ to the REMINST share. In my searching I didn’t see anyone else have to add ‘everyone.’ I thought the default ‘Authenticated Users’ was enough.

  Thanks for the responses! 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

If you are using new (or different) hardware from what you built your Windows image on, you may see:  WdsClient: An Error Occured While Obtaining IP Address From the DHCP Server.  Fortunately, you can ignore most of the other solutions floating around the internet telling you to manually inject the drivers into your image.  Windows Deployment Service (WDS) has a simple mechanism to inject drivers into your image using the WDS GUI.

How to Add Drivers to Windows Deployment Server:

1. Go to your hardware manufacturers website and download the network card driver(s) for the hardware in question
2. Open your WDS MMC, expand the server in question and then expand DRIVERS
3. Select ADD DRIVER PACKAGE,
4. Select SELECT ALL DRIVER PACKAGES FROM A FOLDER and browse to a folder that contains your unpacked drivers
   1. Unpacked drivers means that your driver files must be extracted from their .EXE or .MSI or .ZIP file.
      1. If you do not already know how to do this, download, 7-ZIP and start 7ZIP, select your driver package and click the EXTRACT button
5. In the AVAILABLE DRIVER PACKAGES window just click NEXT
6. In the DRIVER GROUPS window, make sure you choose, SELECT AN EXISTING DRIVER GROUP.
   1. If you do not select a group your drivers will be in WDS but will NOT be applied to any of your images
7. In the TASK COMPLETE window you can click MODIFY THE FILTERS FOR THIS GROUP NOW but I would not
   1. If you add a filter, the drivers will only be applied to devices that meet that filter… I want Windows to figure out if it is needed or not.
      1. The default is “…install all packages that match the installed hardware…” which is good with me

Now you can add those drivers to the image in question.

How to Add Drivers to An Image on your Windows Deployment Server:

1. In WDS, click BOOT IMAGES and right click on the image in question
2. Select ADD DRIVER PACKAGE, then NEXT, then click the SEARCH FOR PACKAGES button
3. The drivers you just added to your WDS server will now appear in the SEARCH RESULTS window
4. Click NEXT, NEXT, NEXT

WDS will then open the image, inject the drivers and close the image.  This is much easier than going through the manual process.

You should not have to restart your WDS service, but if you have troubles, restart it.

Also remember that you will likely want to add these drivers to images other than the BOOT image.  Specifically, you will likely want to repeat the process for the image you are trying to apply and to any CAPTURE image you may have.

WdsClient – An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operation DHCP server on this network segment.

This is the error I got recently when trying to image some new machines for one of the schools I support.

The correct drivers were installed on the WDS server and I’d previously imaged some desktops of the same model with no problems. I tried a new cable and network point, restarted WDS and DHCP on the server all to no avail. All settings on WDS were fine and as they should be.

Do try the above steps first, as 90% of the time it’s resolved by one of them. This problem is also common if you have a faulty or very long network cable.

It turned out that the PC was taking too long to get an IP address, meaning it couldn’t reach the WDS server at the time it tried to. By the time it has been assigned an IP it had already timed out and thrown me this error.

DHCP seemed to be functioning correctly, as other devices were working with no problems – it just seemed to be DHCP and WDS that weren’t working together properly. I needed a way around this, and after a lot of research I found a way to modify my WIM file so it wouldn’t launch the PE until it could ping the server. Obviously if it can ping it has an IP address, so therefore can continue as it should.

Here’s how to do it:

I advise doing this on a client PC, and not the server.

1. Install the Windows AIK. In this example, I am using and deploying Windows 7, so required the Windows 7 AIK.
2. Open “Windows PE Tools Command Prompt” and type the command below that corresponds to the CPU architecture that your current WDS boot image is on:

   • 32bit - copype x86 C:newbootimage

   • 64bit – copype x64 C:newbootimage

     These commands will create a new Windows PE wim image in C:newbootimage. The file path can be altered if you so wish.

3. Go into the WDS console on your server, and export the current image that you’re having trouble booting to. (Right click > Export Image) and copy that to C:oldbootimage on the client PC you created other wim with in the previous step. For the rest of the tutorial, I will assume this file is called wds.wim
4. Mount both images:
   • Mount the image created in step two by running:

      imagex /mountrw “C:newbootimageWinPE.wim” 1 "C:newbootimagemount"

   • Mount the image exported in step three by running:

      imagex /mountrw “C:oldbootimagewds.wim” 2 "C:oldbootimagemount"

5. Now, copy the sources folder from the old boot image (C:oldbootimagemountsources) to the new boot image (C:newbootimagemountsources). This adds the necessary WDS client setup files to the new image.
6. Open the startnet.cmd file (C:newbootimagemountwindowssystem32starnet.cmd) in Notepad.
   The current files will most likely contain very little text. You need to replace the contents with the following:

   @echo off
    wpeinit
    
    @echo Waiting for the WDS server…
    :testagain
    ping –n 1 wds > NUL
    if %errorlevel% == 0 goto pingok
    
    REM wait 3 sec. and try it again
    ping –n 3 127.0.0.1 >nul
    goto testagain
    
    :pingok
    x:sourcessetup.exe /wds /wdsserver:WDS
    

   This small script will keep trying to ping the server called WDS until it receives at reply. At which point it will continue to boot into WDS setup mode.
   You may change the server name from WDS in the script if you wish, however I advise keeping the script as is and adding a DNS entry for the WDS to point to your server’s IP. This way, the wim file is usable across any server / network by just adding a DNS entry.

7. Save changes to the cmd file.
8. Remove all unnecessary components from the new WDS image with the following command:

    peimg /prep mountwindows

9. Unmount the new image and save changes with the following command:

    imagex /unmount /commit mount

10. At this point the new wim image will probably be around 200mb. It’s advised you export the image to a new wim file to reduce it in size with the following command:

     imagex /export “C:newbootimageWinPE.wim” 1 “C:newbootimagenewwds.wim” “Custom WDS Windows PE”

The image at this point is now complete, and will be around 120mb. You can then add this to the boot images section of your WDS server as you normally would with boot.wim from a Windows DVD or ISO.

For your convenience, I have created a Windows 7 32 and 64 bit version of wim which you can download from the following links:

• W732PE.wim
• W764PE.wim

Thanks to svengru at TechNet for sharing his solution. The above is merely a modified version of his solution, clearing up some sections that don’t need to be done post Vista such as importing drivers to the wim.