+ Post New Thread
Results 1 to 7 of 7
Windows Server 2012 Thread, RDS Farm in Technical; Hi all, Just need to query something regarding 2012 RDS farms and thin client devices. I have create a new ...
  1. #1

    Join Date
    Feb 2007
    Location
    Wolverhampton
    Posts
    330
    Thank Post
    18
    Thanked 35 Times in 33 Posts
    Rep Power
    21

    RDS Farm

    Hi all,

    Just need to query something regarding 2012 RDS farms and thin client devices.

    I have create a new session collection in my RDS environment and added two session host servers. These are appearing in the properties for the collection under load balancing. I have one session host server to use but what address would the thin client machines use to connect to the farm and where is it setup?

    Do i need to create DNS entries for the farm name with each IP of the session host servers? But would this not bypass the session broker?

  2. #2
    maark's Avatar
    Join Date
    Feb 2006
    Location
    leicester
    Posts
    474
    Thank Post
    90
    Thanked 74 Times in 66 Posts
    Rep Power
    38
    Am setting up similar here for sims web apps.
    Set it up on one server and added two session servers - I let them get addresses from DHCP - did not configure anything in DNS and when you connect to the name of the first one then it automatically uses the next session server for each user accessing the remote app.

  3. #3

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    17,879
    Thank Post
    518
    Thanked 2,486 Times in 1,928 Posts
    Blog Entries
    24
    Rep Power
    838
    Best way to do it is with DNS records (same name for each server, pointing at each IP) - that way the initial 'landing' before the RDS load balancer kicks in is equally spread as well as the actual RDS load.

    In reality, the amount of load this causes will be very minor in a school environment.

    It also means you have a level of failover too, otherwise if the 'main' server goes down, you lose your entire farm, but if you have an RDS record specific to the farm it will be easy to remove the faulty IP address from it until it is fixed.
    Last edited by localzuk; 22nd January 2014 at 02:44 PM.

  4. #4

    Join Date
    Feb 2007
    Location
    Wolverhampton
    Posts
    330
    Thank Post
    18
    Thanked 35 Times in 33 Posts
    Rep Power
    21
    Quote Originally Posted by localzuk View Post
    Best way to do it is with DNS records (same name for each server, pointing at each IP) - that way the initial 'landing' before the RDS load balancer kicks in is equally spread as well as the actual RDS load.

    In reality, the amount of load this causes will be very minor in a school environment.

    It also means you have a level of failover too, otherwise if the 'main' server goes down, you lose your entire farm, but if you have an RDS record specific to the farm it will be easy to remove the faulty IP address from it until it is fixed.
    So on the thin client machines you would point them at the DNS name that i create for the servers. Would this not bypass the broker?

  5. #5

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    17,879
    Thank Post
    518
    Thanked 2,486 Times in 1,928 Posts
    Blog Entries
    24
    Rep Power
    838
    RDS Brokering is done silently when you connect to an RDS server, the client doesn't know about the broker at all.

    This is our setup for student RDS servers:

    RDSSB - Session Broker
    RDS1 - RDS Server
    RDS2 - RDS Server

    RDSFarm - CNAME DNS record to RDS1
    RDSFarm - CNAME DNS record to RDS2

    RDS1 and RDS2 set up to use RDSSB as the load balancer/broker.

    Works perfectly.
    Last edited by localzuk; 22nd January 2014 at 03:18 PM.

  6. Thanks to localzuk from:

    deano (5th February 2014)

  7. #6

    Join Date
    Feb 2007
    Location
    Wolverhampton
    Posts
    330
    Thank Post
    18
    Thanked 35 Times in 33 Posts
    Rep Power
    21
    Quote Originally Posted by localzuk View Post
    RDS Brokering is done silently when you connect to an RDS server, the client doesn't know about the broker at all.

    This is our setup for student RDS servers:

    RDSSB - Session Broker
    RDS1 - RDS Server
    RDS2 - RDS Server

    RDSFarm - CNAME DNS record to RDS1
    RDSFarm - CNAME DNS record to RDS2

    RDS1 and RDS2 set up to use RDSSB as the load balancer/broker.

    Works perfectly.
    When you say setup to use broker, you mean just the initial configuration of the session collection. No other configuration required somewhere

  8. #7
    TheScarfedOne's Avatar
    Join Date
    Apr 2007
    Location
    Plymouth, Devon
    Posts
    1,143
    Thank Post
    677
    Thanked 169 Times in 154 Posts
    Blog Entries
    78
    Rep Power
    85
    Your session hosts need to be told from the session host config that they are part of a farm. That's where the farm name is specified. You also need to install the connection broker role on your connection broker server

SHARE:
+ Post New Thread

Similar Threads

  1. RDS Session Host Farm vs Clustering
    By 1steelhead in forum Thin Client and Virtual Machines
    Replies: 0
    Last Post: 10th April 2012, 10:18 PM
  2. RD Session Host farm with 2003 TS style logon screen
    By teky in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 15th September 2011, 09:17 PM
  3. Server farm
    By matt40k in forum Hardware
    Replies: 6
    Last Post: 29th January 2009, 09:41 AM
  4. 'Deathstar' server farm
    By CyberNerd in forum Other Stuff
    Replies: 2
    Last Post: 31st May 2007, 03:20 PM
  5. TES Magazine [ 23 rd March ]
    By mattx in forum General Chat
    Replies: 6
    Last Post: 27th March 2007, 09:21 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
  •