+ Post New Thread
Results 1 to 9 of 9
O/S Deployment Thread, Clients boot to WDS no matter what option 66 and 67 are set to in Technical; hi we currently use FOG here. We're contemplating whether we should upgrade the hardware FOG runs on, or use WDS ...
  1. #1
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    405
    Thank Post
    79
    Thanked 54 Times in 52 Posts
    Rep Power
    20

    Clients boot to WDS no matter what option 66 and 67 are set to

    hi

    we currently use FOG here. We're contemplating whether we should upgrade the hardware FOG runs on, or use WDS (Windows Deployment Services). So I've setup a test WDS server.

    WDS somehow managed to just take over, and be PXE-booted regardless of what options 66 and 67 in DHCP say.

    Anyone know why this is? It's rather annoying, and makes it a pain to test it as our ltsp clients wont boot when wds services are running.

    nick.
    Last edited by bart21; 12th May 2011 at 07:11 PM.

  2. #2
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    405
    Thank Post
    79
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    **Bump**

  3. #3

    Join Date
    Apr 2008
    Posts
    853
    Thank Post
    111
    Thanked 112 Times in 108 Posts
    Rep Power
    46
    so option 66 is wdsipnumber

    and option 67 is boot\x86\wdsnbp.com

  4. #4

    Join Date
    Apr 2008
    Posts
    853
    Thank Post
    111
    Thanked 112 Times in 108 Posts
    Rep Power
    46
    Also have you got everything in the remoteinstall folder? any eventlog errors?

  5. #5
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    19
    It's been a while since I looked at WDS, but I had a very similar problem recently when setting up a Citrix Farm which may give you a pointer.

    Check that the WDS server isn't providing PXE services - it just needs TFTP to provide the boot files. FOG needs to do all the PXE stuff and just point the clients to the relevant server. In my case the Citrix server was over-riding FOG and PXE booting the clients on the same VLAN, it may be something similar for you?

  6. #6
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    405
    Thank Post
    79
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    thanks chad, will have a look at that.

    Basically I have my 66 and 67 set to our ltsp servers. The clients that need to pxe to fog have a dhcp reservation with the relevant 66 and 67 options for fog.

    When i start wds services all the dhcp options are overridden and all pc's try to pxe to wds server. I want only a couple to do this which will be set by reservation, the rest need to remain as they are.

    any ideas?

    nick

  7. #7
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    19
    Your logic is sound, and the reservation method should work for the few clients that you want to boot to WDS as it does for the few booting to FOG.

    I'd look in the running services on the WDS server for a "PXE services" one and try disabling it temporarily and see if that helps. Like most MS stuff, it likely assumes that you want their servers to perform all roles by default.

    Chad

  8. Thanks to Chad from:

    bart21 (13th May 2011)

  9. #8
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    405
    Thank Post
    79
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    @Chad

    If i do that will my clients that have reservations pointing to the wds server still pxe boot to the wds server (as required)?
    Last edited by bart21; 13th May 2011 at 03:24 PM.

  10. #9
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    19
    It was more an idea to try to see if WDS's PXE wasn't playing nice and servicing the whole LAN regardless of DHCP options. On the Citrix one I had issues with, turning off the Citrix PXE service resolved it. Clients set with DHCP 66 and 67 pointing to Citrix still network boot from it as expected, and those pointing to FOG boot to FOG. Sorry I can't be more specific, I only tried WDS for a brief period and wiped that server long ago.

SHARE:
+ Post New Thread

Similar Threads

  1. wds stops working on clients pxe-e32 tftp open timeout
    By sted in forum Windows Server 2008 R2
    Replies: 34
    Last Post: 18th July 2014, 12:35 PM
  2. [MS Office - 2010] No help option, No options option
    By rh91uk in forum Office Software
    Replies: 1
    Last Post: 18th November 2010, 05:28 PM
  3. Network Boot DHCP/WDS
    By SteveBentley in forum Wireless Networks
    Replies: 4
    Last Post: 18th September 2008, 01:16 PM
  4. Good practice for server set up for thin clients
    By tosca925 in forum Thin Client and Virtual Machines
    Replies: 2
    Last Post: 17th March 2007, 06:01 PM
  5. dapper cd install boot option
    By CyberNerd in forum *nix
    Replies: 7
    Last Post: 3rd October 2006, 05:44 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
  •