?
Solved

Need Overview of 2008 R2 Remote Desktop Services Clustering/Network Load Balancing

Posted on 2010-01-12
3
Medium Priority
?
981 Views
Last Modified: 2013-11-21
-I have a client who is looking to implement Server 2008 R2 Remote Desktop Services for 600 external users.  
-The external users will only RDP to the server and not use Web Access.
-There will be 3 servers available with more than adequate system resources so that network load balancing/clustering can be utilized

With the 3 servers that I will have availble what design will I be looking at?  
One server loaded as the Connection Broker, Licensing Server, and Gateway with the other 2 servers being Session Hosts?
Is Windows Clustering needed or recommended?

I am basically trying to get a grasp on how the design should look.
0
Comment
Question by:advserver
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 4

Author Comment

by:advserver
ID: 26305588
After thinking about this for a while, an attempt to answer my question.

-4 servers instead of 3 will be used.
-2 servers clustered and set as connection brokers.
-2 servers on the back end set as session hosts.
-The clients although remote are all domain joined and therefore should not need a Gateway server in the design.  
-When additional users come into play additional session hosts will be added.  

Does this sound correct? Thoughts?
0
 
LVL 31

Accepted Solution

by:
Henrik Johansson earned 2000 total points
ID: 26331342
For RD Session Host, use NLB (Network Load Balancing) instead of clustering with Failover Cluster.
I have earlier had thaughts about clustering RD Connection Broker, but haven't seen the neads yet. If the service is temporary unavailable, clients will be able to logon to the Session Hosts.
Gateway is neaded if clients can't connect directly to the Session Host addresses when for example laptops go offsite.
If using NLB, the RDCB will sometimes redirect the client to use the other RDSH than the original used for the NLB connection making the clients nead to be able to reach the RDSH either directly or proxied through RD Gateway.
0
 
LVL 4

Author Comment

by:advserver
ID: 26353111
Thank you very much for your insight! We will not be clustering the Session Hosts but will cluster the Connection Brokers as the client feels it is a necessary service due to the number of users that will eventually be using the servers.  Thank you again!
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question