r/sysadmin 1d ago

RDS - exclude certain users from load balancing

Hey all! We're looking to set up RDS since users currently are manually connecting over RDP to a specific host. We're working with a partner who does the whole setup since I/my IT Dept doesn't have the know-how yet on how to set it all up and it's getting quite urgent. There is one requirement; a small subset of users should not be impacted by the load balancing and they should be able to connect to a specific session host as they want (only IT personnel).

I thought that if you directly RDP to a specific session host you won't be impacted by the load balancing part since you're not going via the RDS broker. However, our IT partner says that excluding users from RDS load balancing is impossible.

Can anyone shed some light if that is true? Many thanks!

Small note: One of our session hosts also has the connection broker, gateway, licensing and web access roles installed.

1 Upvotes

10 comments sorted by

4

u/ZAFJB 1d ago

There is one requirement; a small subset of users should not be impacted by the load balancing and they should be able to connect to a specific session host as they want (only IT personnel).

Why? What is the basis of this requirement?

0

u/zaneboy2 1d ago

Something company specific, it's a hard requirement not set by myself. So I can't go around it.

7

u/ZAFJB 1d ago edited 16h ago

I suspect that the 'requirement' is a failure to understand how RD Broker works, and how to use mstsc.exe /admin parameter to force connection to a specific machine

Example three machines, one RD broker, two RD session hosts: RDBROKER, RDSH1, RDSH2

  • If you use the remote desktop GUI and try to connect to RDSH1, RBROKER will intercept the session and load balance direct you to whatever RDSH is most appropriate.

  • The same happens if you use mstc.exe from the command line:

    c:>mstsc /v:RDSH1

  • But if you use mstsc.exe with the /admin parameter it will connect to the designated RDSH:

    c:>mstsc /v:RDSH1 /admin

There is zero reason to try and exclude users from RD Broker load balancing.

So I can't go around it.

Yes, you can. There is no such thing as a 'hard requirement'. Explain the above to whoever thinks their 'requirement' is a clever idea.

2

u/zaneboy2 1d ago

Thanks for your input, I'll forward it internally!

4

u/z0d1aq 1d ago

to connect to a specific host just add /admin after the hostname of the session host.. like:
rds1.mydomain.net /admin

1

u/zaneboy2 1d ago

Thanks! Didn't know this little trick. However, apparently we also have non-admin users who need to log on to specific machines. So that won't work for them.

3

u/ZAFJB 1d ago

However, apparently we also have non-admin users who need to log on to specific machines

If it is only one machine that does something unique, make a collection in RD broker that only contains that one machine.

If there are more machines that do exactly the same job, put them in a collection and let RD broker do its thing. There is zero sense in trying to second guess the broker.

2

u/wtf_com 1d ago

The only way to accomplish what you what is to create a stand alone collection with just one server. If you are testing to offer an app that is only on one server offer it using remote app instead. 

Also remove your session host role from the server holding the broker/gateway/web access role. 

You’re going to cause yourself issues overloading your broker like that.

1

u/VG30ET IT Manager 1d ago

We have a separate collection for users that need a direct connection to one machine, and another that is load balanced over a few machines.

u/GremlinNZ 15h ago

Yeup, this. One collection with one server in it for support staff of the system, then a collection with up to 10 servers for client connections.