+ Post New Thread
Results 1 to 10 of 10
Windows Server 2008 R2 Thread, WDS on 1 server and DHCP on the other server problem!! in Technical; Hi Im having a problem at the moment with WDS ill explain in depth as I'm totally lost now to ...
  1. #1
    phillip_croxford's Avatar
    Join Date
    Feb 2012
    Location
    Doncaster
    Posts
    96
    Thank Post
    23
    Thanked 2 Times in 2 Posts
    Rep Power
    6

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

    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.

  2. #2

    Join Date
    Jun 2008
    Location
    Dawlish/Teignmouth
    Posts
    268
    Thank Post
    45
    Thanked 38 Times in 37 Posts
    Rep Power
    20
    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.

  3. #3
    phillip_croxford's Avatar
    Join Date
    Feb 2012
    Location
    Doncaster
    Posts
    96
    Thank Post
    23
    Thanked 2 Times in 2 Posts
    Rep Power
    6
    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??

  4. #4
    phillip_croxford's Avatar
    Join Date
    Feb 2012
    Location
    Doncaster
    Posts
    96
    Thank Post
    23
    Thanked 2 Times in 2 Posts
    Rep Power
    6
    well ive tried both ip address and DNS name and still no joy?? im scratching my head now! anyone else got any ideas??

  5. #5
    adhutton's Avatar
    Join Date
    Dec 2008
    Location
    Northeast England
    Posts
    399
    Thank Post
    164
    Thanked 86 Times in 64 Posts
    Rep Power
    54
    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

  6. #6
    phillip_croxford's Avatar
    Join Date
    Feb 2012
    Location
    Doncaster
    Posts
    96
    Thank Post
    23
    Thanked 2 Times in 2 Posts
    Rep Power
    6
    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
    Last edited by phillip_croxford; 22nd May 2012 at 11:37 AM.

  7. Thanks to phillip_croxford from:

    davipton (3rd November 2012)

  8. #7

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,746
    Thank Post
    1,275
    Thanked 1,648 Times in 1,104 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by phillip_croxford View Post
    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.

  9. #8


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,588
    Thank Post
    228
    Thanked 856 Times in 735 Posts
    Rep Power
    296
    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

  10. #9

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,746
    Thank Post
    1,275
    Thanked 1,648 Times in 1,104 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by sted View Post
    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...

  11. #10

    Join Date
    May 2011
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Thanks Phillip!

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

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 2
    Last Post: 14th December 2011, 10:37 PM
  2. Replies: 1
    Last Post: 1st September 2011, 11:41 PM
  3. WSUS 3.0 and Sophos on the same Server?
    By tosca925 in forum Windows
    Replies: 8
    Last Post: 7th May 2007, 09:58 PM
  4. Help and advice on using the GPMC
    By standunstan in forum Windows
    Replies: 6
    Last Post: 21st March 2006, 09:46 PM
  5. Shadow copies and WSUS on ame Server 2003
    By tosca925 in forum Windows
    Replies: 4
    Last Post: 5th February 2006, 01:16 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •