+ Post New Thread
Results 1 to 12 of 12
Thin Client and Virtual Machines Thread, Fat and thin client coexistence in Technical; We currently have WDS server for deploying images to our fat clients, and thinstation for running our thin clients. DHCP ...
  1. #1
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15

    Fat and thin client coexistence

    We currently have WDS server for deploying images to our fat clients, and thinstation for running our thin clients.

    DHCP is all one big scope, so limited to one set of options. Options 66 & 67 are set to point to the thinstation TFTP, however since setting that up my fat clients now boot to the thinstation when I try and rebuild them.

    Is there anyway I can separate the two?

  2. #2

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,855
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    181
    AFAIK you can do this with DHCP user classes/vendor classes. You specify what class a machine belongs to in Windows, and on the DHCP server configure the options for that class.

    Never tried it myself though, but I am doing shortly so I'll let you know how it goes.

  3. Thanks to powdarrmonkey from:

    Andi (14th February 2008)

  4. #3
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    Never heard of that. I'll do a bit of research.

  5. #4

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,855
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    181
    From http://blogs.msdn.com/anto_rocks/arc...25/380231.aspx :

    "User classes are fundamentally different. User class enables partitioning the client machines into distinct classes that can receive different options values based on their user class."

  6. Thanks to powdarrmonkey from:

    Andi (14th February 2008)

  7. #5

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,800
    Thank Post
    110
    Thanked 582 Times in 503 Posts
    Blog Entries
    1
    Rep Power
    223
    It's a pita to do on a windows DHCP server. Your much better off (once you're used to it) using ISC DHCPd.

  8. Thanks to Geoff from:

    Andi (14th February 2008)

  9. #6
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    Presumably my best course of action would be to separate the two on different subnets anyway? That's something that's a hot topic here at the moment, but is not a simple move and nobody in-house knows exactly how to do it.

  10. #7

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,800
    Thank Post
    110
    Thanked 582 Times in 503 Posts
    Blog Entries
    1
    Rep Power
    223
    router + VLANs.

  11. Thanks to Geoff from:

    Andi (14th February 2008)

  12. #8
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    Yeah that's exactly what I'm intending to get setup here to lower the broadcast traffic and generally just neaten things up.

  13. #9
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    OK, seeing as changing our entire networks IP structure is quite a massive job it's not something I can even contemplate at the moment.

    Just a thought, in the meantime would it be possible to setup a second scope on my existing DHCP server (windows server 2003) and reserve IPs for the thin clients, giving them the thinstation options, and the fat clients (remaining on the existing scope) having the WDS options?

  14. #10
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    I take it that's a no then?

  15. #11

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,800
    Thank Post
    110
    Thanked 582 Times in 503 Posts
    Blog Entries
    1
    Rep Power
    223
    You would have to setup a user/vendor class. Which I could never get to work properly on windows dhcp.

  16. Thanks to Geoff from:

    Andi (27th February 2008)

  17. #12
    Andi's Avatar
    Join Date
    Feb 2007
    Location
    Newport, South Wales
    Posts
    276
    Thank Post
    52
    Thanked 4 Times in 4 Posts
    Rep Power
    15
    Ok, thanks Geoff.

SHARE:
+ Post New Thread

Similar Threads

  1. VNC on thin client
    By _Bob_ in forum Thin Client and Virtual Machines
    Replies: 12
    Last Post: 19th March 2010, 08:11 AM
  2. Another thin client one.....
    By Lee_K_81 in forum Thin Client and Virtual Machines
    Replies: 13
    Last Post: 13th May 2008, 03:41 PM
  3. Thin Client Box
    By wesleyw in forum Hardware
    Replies: 7
    Last Post: 9th July 2007, 04:29 PM
  4. CC3 via Thin Client
    By u8dmtm in forum Thin Client and Virtual Machines
    Replies: 5
    Last Post: 23rd May 2007, 01:09 PM
  5. Thin client instead of CC3
    By u8dmtm in forum Thin Client and Virtual Machines
    Replies: 13
    Last Post: 5th March 2007, 11:01 AM

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
  •