This may defeat the purpose of the Farm..but...
Is there a way to add a terminal server to a Remote Desktop Clustered Farm but not let it do the load balancing? For example:
Say I have 3 Terminal Servers. I only want "user A" to be able to log into "TS 1" and not "TS 2" or "TS 3".
I've made a GPO that only allows "user A" access to "TS 1" and try to log into that directly but the load balancing will try to put "user A" on "TS 2" or "TS 3" and essentially error out because "user A" doesn't have access to either one.
Any help or advice is appreciated.
You cant control it with a GPO because the GPO's aren't processed until the client reaches the server. One way to do it is to setup a standalone terminal server natted directly to the outside with a separate public DNS name.
Ken, thanks for the reply.
To be honest I'm not really following what you are saying here.
You could do this by publishing that user's applications only to TS 1 with a different name. Then, when they launch there is no choice but to go to that one server. It might mean a little more administrative work, but it accomlish what you are trying to do (for whatever reason).
Why is it called "Common Sense"? It doesn't seem all that common!