using windows deployment services WDS and getting; wdsclient an error occurred while obtaining an ip address

Have you set the DHCP scope options for PXE ?
If so, do you have multiple DHCP scopes and/or servers which also require it setting?

are you talking about the 060 DHCP setting? I did check that but was told that was only if I was using the WDS server as a DHCP server also. I am trying to use a different DHCP. I will go back in and apply it if you think it will make a difference

Yes, I have it set but then again my WDS server is on one of my dhcp servers.

Well this is unusual. I attached a fresh DELL laptop, out of the box and booted to PXE, selected to INSTALL an image and I got passed the DHCP issue I had with the HP desktop. Then I got to the part where I had to select an image and saw the HP image was out there, even though I needed to select the DELL image this time. Everything appears to be installing fine. I have no clue why this is working so smooth with the DELL laptop, but HP is having so much trouble. Does anyone have any idea if this could be a setting on the HP 6200 desktop?? I do not think it is the server

Check the BIOS for the HP computer see if there are any strange things set for PXE.

The likely culprit is the network driver on the HP.
Download the network driver from HP's support site, add it to your WDS driver install groups, and inject it into your boot image.

I will play around with the bios and PXE and I already have injected the NIC drivers from the exact same model of HP into my WDS drive install group, but I will try downloading the latest version. I am thinking though that I may just end up going with DHCP on my WDS. My only concern is to create a rogue DHCP server on the network. What steps are involved in using WDS as the DHCP for deploying? I take it I would have to

1. Authorize the Windows Deployment services server in DHCP , under the ADVANCE tab.
2. select DO NOT LISTEN ON PORT 67 and Configure DHCP option 060, under the DHCP tab
3. Go to my real DHCP server and configure 060, pointing to the IP of my WDS server

What else do I need? Do I need to actually install the DHCP server role on my WDS server and can I limit it to only issue IP to Devices that are PXE booting??

well I have played with all kinds of settings and this is getting frustrating. I have been downloading driver packages from HP and injecting them into my "DriverGroup" in WDS. I have noticed on several WDS servers they have several driver groups. I have been pushing all the drivers I download into the default DriverGroup1. Could this cause an issue? What is the benefit in having several driver groups?

I will try again, but want to mention a few things.

1. I have tried to image 3 different models of HP desktops, starting with a 6200 and all report a WDSCLEINT error "not able to find DHCP server" but when I try to image our DELL laptops everything goes smooth.

2. I press ALT F10 when i get the error and see the command prompt and do IPCONFIG. It shows the media is disconnected and if I look at the ethernet port in the back it is not lit up, but when I have any of the desktops booted up with a WIndows OS, it lights up fine.

3. How the heck can these deskops PXE boot and find the WDS server and attempt to install an image if they have no IP?

ALL advice welcome, I am a little concerned that I am injecting all these drivers I have been downloading into the wrong driver group but using the default which seems to support our DELL machines. All advice, comments and input welcome. I am about ready to recommend we switch all desktops over to DELL instead of HP this has gotten so frustrating

I should also note that when I have "Do not listen on port 67" checked, I cannot even get a good PXE boot on any of my workstations, even the DELLs. I am definetly using port 67, if that means anything on how I should configure my DHCP server

well I am really loosing it now, I installed DHCP in my WDS server and went to configure 060 and do not even see the option for it. Where can I add 060?

It's in server options rather than scope options, can't remember exactly but it is a bit out the way.

One of my colleagues has just had to upgrade the BIOS on several (100+) HP Desktops as they were experiencing random PXE boot issues.

This may help
http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/af3f1376-948a-4a96-b69c-67a6d1576dd2/

ok I will check on the HP bios and read the links you have suggested, but I have gotten myself into another mess. I went back and re uploaded the boot file for /sources on my 2008r2 DVD, putting me back to the original boot file. I tried booting from this and got my original error about not able to install network drivers or something related to that. I went ahead and injected all the driver packages I had into this boot file and returned to the error I had where I could not find a DHCP server. I went ahead and deleted this boot file and reuploaded a new one of the DVD again. I got the idea that I would selectively start injecting driver packages one at a time and hopefully find one that worked before I came across one that would return me to the DHCP error or at least discover which driver package was causing the issue. Somewhere in the process something got corrupted. I cannot inject any new drivers into a fresh boot file now, I just get an error related to corruption. Is there a way to totally remove all the driver packages I had uploaded when this issue started and let me start all over, be very selective of which drivers I upload and build a boot file that way? Right now I am kind of stuck with the 64 bit boot file I have, I cannot inject anything into it. I did a test by uploading an i386 boot driver and that seems to work and I am able to inject drivers into it, but I am trying to configure WDS so I can blow out several Windows 7 64 bit machines and really want to start over without blowing away the capture images I worked hard to create. I just want a fresh start with my driver packages, I did the stupid ASS U ME thing again by assuming the more drivers injected the better, but I am finding out some drivers do much more harm than good.

Also, is there a placed or is it legal for me to just go download the latest and greated boot file from Microsoft. The boot I am uploading from DVD is probably a couple years old. I was wondering if Microsoft had a boot that may have all the proper drivers properly injected. Comments on this welcome also..thanks

Also, since my error is related to DHCP, I am looking more into using my WDS as DHCP also. I installed the DHCP role on my WDS server, configured a small scope of two IP addresses on my subnet, made reservations for them on the other DHCP server and checked Do not listen on port 67. When I do this, my PC boots up and tries a PXE boot, but sort of goes into a loop just searching and searching for a DHCP server. It does not seem to find one even though I have it configured on the WDS server. Apparently from the article suggested above I do not see option 060 because DHCP and WDS are on the same server, but shouldn't it find one of the local DHCP on boot up. I did check the box the authorize, I think that was the Advance tab and checked both boxes in the DHCP tab. I do not care either way which DHCP I use and I can image DELLs with the original nonWDS DHCP server that we have used for years, so I did not expect to have to install DHCP on the WDS server, but I will if it will get my past this DHCP PXE issue. All comments on this are welcome also

I got the my boot files accept new drivers by following this procedure I found online;

"If you were trying to add a driver to a boot wim and it failed resulting in that error code the following may help.
 
1. Clear all your temp directorys.
 
2. Browse to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images" and delete any keys below this.
 
WDS should now allow you to add drivers to the boot.wim."

but I am going to open up another question. It seems half of what I thought I knew about WDS is not true or not appear to work the way I expected. Too complicated to add to this question, but I would still like some advice on my last few posts, minus the injecting drivers to boot issue I had..thanks

I really worked the issue out by uploading a boot.wim from a Windows 8 ISO, but this user contributed a lot and got me thinking and researching in the right places..thanks