Can you restart the TS Session Broker service without it disrupting current sessions
Posted on 2009-04-23
I have six Microsoft terminal servers in a NLB cluster, running under a Windows 2008 DC. This DC is using the new TS Session Broker service (session directory?) Sometimes I have a problem where I need to take one of the terminal servers out for maintenance. During this time, the sessions build up on the remaining servers in the cluster. Although the NLB service and session broker is supposed to balance the load, sometimes it does not. The priority 1 server builds up until it hits it's maximum capacity. When the next person goes to connect, it does not connect to them to priority 2 server. Instead, it just says it cannot connect to the cluster. Is there a way to make session directory forget that a particular user logged onto a particular server? Can you restart one of the services without disrupting current sessions? In other words, I would like to be able to log off a couple of users (from the maxed server) and then have them reconnect, but the system would connect them to the east busiest server.