WDS on 1 server and DHCP on the other server problem!!

[Guest]

Hi

 

Im having a problem at the moment with WDS

 

ill explain in depth as I'm totally lost now

 

to start I have 2 domain servers,

 

Server 1:-

AD / GC

DHCP

DNS

File Services

Print and Document

Group Policy

 

Server 2:-

AD / GC

DNS

File Services

WDS

Web Server IIS (WDS only)

WSUS

Group Policy

 

im trying to get my clients to boot into PXE to connect to my WDS, as you can see above my DHCP server is on another domain server

Im getting the classic:-

 

PXE-E55: ProxyDHCP Service did not reply to the request on port 4011

 

in my DHCP server options i have set

 

option 60 to PXEClient (which i believe is default)

option 66 to the ip address of server 2

option 67 to boot\x86\wdsnbp.com

 

i have also tried this on server 2 in command prompt

 

Wdsutil.exe /delete-autoadddevices /devicetype:rejecteddevices

 

Wdsutil.exe /delete-autoadddevices /devicetype:approveddevices

 

but i get an error in return saying

 

An error occurred while trying to execute the command.

Error Code: 0xC1050100

Error Description: The Pending Devices policy is not enabled on the server.

 

ive also tried stopping the WDS server service and delete all of the files within Mgmt folder and then restart. then the files recreate!

 

this isnt working

 

im running out of ideas!!! any ideas or comments welcome

 

Thanks

 

P.S. its a brand new installation on a new server

both servers are within the same subnet

i have installed the WDS to a G: Drive on a Dynamic Disk within a folder called "Windows Deployment Services"

 

and it has installed in there.

[MrEprise]

As far as I know, Option 60 should be the name of your WDS server in order for WDS to know where to pickup DHCP addresses from when a client boots from network. This is the only thing I think I had to change on our setup for clients to be able boot into WDS.

 

Options 66 & 67 for us are set to an entirely different server to allow for Thinstation to work so i'm not sure they're required.

 

Not sure if this will help but hopefully might point you in the right direction.

[Guest]

Hi Sheilder

 

thanks for the reply. for option 60 are you suggesting that i put in the ip address of the wds server or the DNS name?? which one did you use??

[Guest]

well ive tried both ip address and DNS name and still no joy?? im scratching my head now! anyone else got any ideas??

[adhutton]

I think the The Pending Devices policy is not enabled on the server. is your clue.

 

As far as I remember, with WDS you can set PCs to be added automatically or go into a 'Pending Administrator Authorisation' state.

 

It sounds like you may have a tick in a box which shouldn't be there or maybe one which is missing in your WDS setup.

 

Andrew

[Guest]

Sorry disregard my last message

 

I've got it working!!!

 

in option 60 I've put the IP Address where my DHCP server is, even though on the Microsoft website it states to leave it as the default "PXECleint"

 

i left option 66 and 67 the same as stated above

 

rebooted client, F12 boot to network and it booted straight up!

 

thanks god i can get all these new PC's imaged, thanks to all who have replied

 

Hope this helps anyone else out there who has the same problem

 

 

DHCP:

(Server Options)

 

Option 60: IP address of DHCP server

Option 66: IP address of WDS server

Option 67: boot\x86\wdsnbp.com

 

These settings worked a charm

Edited May 22, 2012 by phillip_croxford

[sparkeh]

in option 60 I've put the IP Address where my DHCP server is, even though on the Microsoft website it states to leave it as the default "PXECleint"

For future reference I don't think that this is true. MS tell you to configure option 60 *only* if DHCP and WDS are on the *same* server. Setting option 60 to PXEClient tells the client that WDS is available on the DHCP server which obviously you didn't want. I would hazard a guess that as long as you removed the PXEClient string from option 60 the WDS boot would work.

Settings options 66 and 67 is what you need to get WDS running when DHCP and WDS are on different servers.

[sted]

for what its worth im in a school now where wds/mdt isnt on the main server (most of my schools have 1 server here i have 3) and Option 60/67/66 are not even listed on server or scope options at all and it works fine

[sparkeh]

for what its worth im in a school now where wds/mdt isnt on the main server (most of my schools have 1 server here i have 3) and Option 60/67/66 are not even listed on server or scope options at all and it works fine

Yeah... I just took a look at our config (dhcp and wds not on same server) and and we have none of that in the scope options either. Works fine.

Scratching my head as I am sure I put that in...

[TerryPDX]

Not sure why this worked, but it did fix my problem.

[theo_logical]

This worked for me too

 

I wish I'd asked my friends at Edugeek in the first place and saved myself hours of Googling, there's a lot of conflicting information out there

 

I think Sparkeh is correct, leaving the value blank is sufficient.

 

Thanks

[Guest]

Im glad it worked!