Remote Desktop Connection Broker ??

We currently have two Remote Desktop servers. Both servers have the same applications on them. I have basically manually split users, half of them connect to RD01 & the other half to RD02. Each Remote desktop server has a public ip with port 3389 port forwarding.

What I would like to do is add another remote desktop server and setup roaming profiles and figure out how all users can remote desktop to one public ip address and that server can then figure out what session host server to put them on.

Is this possible? Can someone clarify to me how best to do this where I will understand please.

Thanks!!
LVL 2
LeviDailyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

hmarcbowerCommented:
It looks like there is quite a bit of functionality built into 2008 R2, if tha's what you are using....

http://technet.microsoft.com/en-us/library/cc753891.aspx
AustinComputerLabsCommented:
The following article "How to Configure Windows Network Load Balancing for pure Terminal Server environments"
Is written for server 2003 and your question did not specify what version you are using. Regardless it will give you good start on understanding the process.

http://www.brianmadden.com/blogs/brianmadden/archive/2004/11/29/how-to-configure-windows-network-load-balancing-for-pure-terminal-server-environments.aspx
LeviDailyAuthor Commented:
Server 2008 R2 - vmware env
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

hmarcbowerCommented:
Alright, so you're already on 2008 R2, and virtual.  That's exactly the scenario discussed in the article I posted. :)  It talks about roaming profiles, as well, which is where you would need to go for load balancing - and also redirected folders (redirect My Documents to a network drive should really be all you need to implement along with roaming profiles).  

We've used these technet guides at work for several things, and they're really very good.
LeviDailyAuthor Commented:
Thank you! I am just not clear on some things, maybe you can help. Since we have users outside of the network using RDP, it looks like I need a Remote Desktop Gateway. It also looks like I need a Dedicated Redirector and a RD Connection Broker. Is this correct? I would like all users from outside the network to be able to remote to remote.domain.com which is a public IP with 3389 forwarded to the RD Gateway. The RD Gateway would be the Dedicated Redirector. I think?? :)

Here is what I see? Someone tell me what to change if I am wrong.

Step 1) Client connects to remote.domain.com via Remote Desktop Client on port 3389. The RD Gateway/Dedicated Redirector then passes the content to the RD Connection Broker.
Step 2) The RD Connection Broker activates the RD Session Host plugin which then determines the best RD Session host server and sends the result to the RD Gateway/Redirector
Step 3) The redirector sends the IP to the client.
Step 4) The client then silently connects to host server using that IP Address

Is this right? If so, I would need a dedicated public IP address for each RD Session Host server that I have?
hmarcbowerCommented:
I think the gateway is used so that you don't need direct connections from outside your network to your session host servers.  Based on this statement:  "The improvements to the RD Gateway role service will be of interest to organizations that currently use or are interested in extending Remote Desktop Services to clients that are not directly connected to the corporate network." So as long as they can get to your gateway server, then you shouldn't need external IP addresses for your session host servers.  It appears your Gateway should either be outside the firewall or inside the firewally with port 3389 opened, then it communicates from the gateway to the session host servers on port 443.  When it's outside the firewall, that usually means you don't have any more configuration to do as 443 is usually an open port on a firewall.

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
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
Windows Server 2008

From novice to tech pro — start learning today.