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

-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.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

advserverAuthor Commented:
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?
Henrik JohanssonSystems engineerCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
advserverAuthor Commented:
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!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.