Is there a way to drainstop a terminal server when users are connecting through vWorspace Connection Broker (7.1)?
Our setup is that multiple terminal servers (or remote desktop servers) shares a published application (desktop). If you remove a server from that published app, the users are not connecting to the removed server (as it should be).
Now, can you somehow remove a server from a published app, but allow disconnected sessions (that is connected to the removed server) to still be able to reconnect to that server? New users with no active (or disconnected) sessions will be connected to a server that is still active and shares the app.
OK - we've been looking at this today. The Enable/Disable Logons feature works in 7.1 and 7.2 beta 2 for x86 Terminal Servers. In the final version of 7.2 we will support x64 Terminal Servers and Session Hosts.
A server can either be an available server or not for a published app. You would have to create a secondary app to give the group of people that are in a disconnected state and manage that manually. Not pretty.
We tried this, but it did not work... I created a "Workload Evaluator" with the counter "Number of Users" to a "Max Value" of 0... Users without disconnected sessions were still able to logon to the server where I applied this Workload Evaluator (are currently using 2 terminal servers with a published desktop).
I'm sorry to say that the connection broker does not detect if the server is "draining".... It sends client to that server despite beeing drainstopped (change logon /drain).
You only get the usual "Remove logins are currently disabled".
/QUERY Query current session login mode. /ENABLE Enable user login from sessions. /DISABLE Disable user login from sessions. /DRAIN Disable new user logons, but allow reconnections to existing sessions. /DRAINUNTILRESTART Disable new user logons until the server is restarted, but allow reconnections to existing sessions.
DELL-Jon Ro
1 Rookie
•
64 Posts
1887
1
Posted November 3rd, 2010 21:00
OK - we've been looking at this today. The Enable/Disable Logons feature works in 7.1 and 7.2 beta 2 for x86 Terminal Servers. In the final version of 7.2 we will support x64 Terminal Servers and Session Hosts.