Solved!
Go to SolutionRestrict to single session
with the RD Gateway and the TS session hosts it supports restricting user to single session.
vWorkspace also seems to works ok for this setting, but I've found a couple cases where it actually logs into a different session on a different server.
Am I missing a setting somewhere?
DELL-David Y
228 Posts
324
0
Posted December 28th, 2010 13:00
Hello Mark,
With vWorkspace 7.1 we introduced the SessionRoamingMode setting to allow you to restrict users to one session per farm. It may be you have this set in your farm however it was not clear from your last post. Please check to see if you have this configured:
SessionRoamingMode – When enabled, the connection broker looks for both active and disconnected sessions when a user issues a launch request. This enforces one user session per farm and allows a user to roam, being able to return to their active session from any terminal (defaults to 0=disabled):
HKLM\SOFTWARE\Provision Networks\Common\Load and License Manager
SessionRoamingMode REG_DWORD (0=disabled 1=enabled)
If you think you still have a problem after setting this option can you let me know what is happening when you see a user that has more than one session, are they using more than one client computer, what are they connecting to etc...
Thanks, David
Made the change on the connection broker and rebooted last night and tested by logging into an account from 2 different machines. It successfully restricted to a single session, however we are having a problem with a few users whereas they are disconnected from the server and login from the same machine and end up on another server
We are using a round robin DNS name for the terminal servers (which is how we do it for the basic RD connection broker) although that shouldn't matter too much as the connection broker should still be checking for sessions (active or disconnected) for the users.
Quote -
Using Quest PNTSC to connect directly to a Round Robin DNS name will bypass the Connection Broker and break session roaming mode.
Thats what I was doing. Using default Microsoft RD connection broker, thats how you do it...but not with Quest.
We've started transitioning to the app portal and its actually much nicer and easier to setup...and does load balancing correctly
DELL-Andrew W1
378 Posts
324
1
Posted January 10th, 2011 12:00
Just in case anyone else has this issue.
Each Terminal Server/RDS server should be added to vWorkspace and then you can let vWorkspace load balance via the Workload Evaluators.
Using Quest PNTSC to connect directly to a Round Robin DNS name will bypass the Connection Broker and break session roaming mode.
Kind Regards, Andrew.