• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 616
  • Last Modified:

2008 TS farm - need users to get their last connected session

I have a 2008 TS farm and when a user disconnects  from one session when he comes back in to the system she is looking to grab the session she left but she is being directed by default to the next available TS server and loses his connection/place so to speak - this is not restricted to any one user but to all users.  Is there any way to program it so that users getting the last session they 'disconnected' from has a higher priority than other load-balancing considerations - in other words they get the Terminal Server their disconnected session is on? All MS here - no Citrix.
0
lineonecorp
Asked:
lineonecorp
  • 5
1 Solution
 
Sushil SonawaneCommented:
Please refer below link to configure timeout and reconncection setting for terminal server.

(http://technet.microsoft.com/en-us/library/cc754272(v=ws.10).aspx)
0
 
alexsupertrampCommented:
In terminal services configuration, you may also need to set "restrict each user to one session" to "yes".
0
 
lineonecorpAuthor Commented:
Thanks for the comments. We think we have found the solution - a hot fix from Microsoft. We are just waiting for a window of time to apply. I will notify here of the results.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
lineonecorpAuthor Commented:
Thanks for your patience. The hotfix was not applicable to 2008 R2. We have discovered some more detail of the problem. As I indicated we have a multiple physical host 2008 R2 Hyper-virtualized TS farm with several session brokers (virtualized as well) and a connection broker (VM) as well. What is happening is that around noon the Session Brokers suddenly lose their connection to the Connection Broker and then a minute later reconnect. However in the process of disconnecting and reconnecting, the Connection Broker now no longer has the appropriate connection information for the clients that were logged on to the TS. The clients are still connected via the TS to the Session Broker but because the Session Broker lost connection to the Connection Broker it seems that those users who disconnected and would ordinarily get their session back - we have a 2 hour time out - are no longer being redirected to their existing session. This only happens at noon which coincides with the time that people go for lunch and disconnect their sessions en masse - at other times of day when there is a more intermittent disconnection situation- a person here and there disconnects from their session but there is no 'mass disconnection' there is no issue - the users when the reconnect go back to the session they left. I would appreciate any thoughts as to what might be the cause of this/how we might isolate the problem? Is there some kind of maximum disconnection issues with Connection Broker?
0
 
lineonecorpAuthor Commented:
Still monitoring?
0
 
lineonecorpAuthor Commented:
Problem was related to one group of users using a common name to log into their local accounts before accessing TS.  Messed up Connection Broker's ability to keep profiles straight.
0
 
lineonecorpAuthor Commented:
Nothing posted by Experts was in the right direction. Our fix was definitive.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now