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

Remote Desktop Session Broker does not reconnect session if loggin on from another workstation

This may seem a silly question and I am certain there is a configuration that I missed for this. I am working with a 5 server site. 1 DC 1 Dedicated Session Broker and 3 Remote Desktop Services Hosts. The Broker and load balancing seems to be working almost flawlessly, however there is one snag. When a user opens an RDP session from a workstation to the Remote desktop session host they are able to login and work without any problems. If they close the session instead of logging off they are able to reconnect to the disconnected session without any difficulty. If they try to login from another workstation they get a message of access denied session broker unable to connect to session. If the user logs off, there is no issue moving to another workstation. There must be a configuration of the session broker that I am missing that allows the session to reconnect from any workstation not the single station the user logged into. All servers are Windows 2008R2
0
overcld9
Asked:
overcld9
1 Solution
 
JPetersen92020Commented:
From my experience there is no configuration to allow someone to unlock a locked PC from another location. Please update this post if you find one!
0
 
meko72Commented:
0
 
overcld9Author Commented:
OK neither of these two posts are helpful. The session broker and the session hosts are configured and working. What I am talking about is when a user logs into the remote desktop session, (Opens Remote Desktop types FARMNAME and licks connect) if the user disconnects their existing session and moves to another PC they cannot re-connect to the session. It works for Administrator, I can close remote desktop without logging off and reconnect to the disconnected or orphaned session from any machine on the network. If I try to do this from a standard user, I get an error message of access is denied. If I go back to the original machine and login it re-connects my session and I can then log off. Once logged off I can go to any other machine on the network and login again but once the session is created it seems to be locked to the workstation that initiated the session until that session is closed.
0
 
overcld9Author Commented:
I have a bad habit of answering my own questions. I found a hotfix from Microsoft that applies to 2008 R1 TS Session broker. The issue that the hotfix addresses is that when the user tries to login to a disconnected session from another machine on the network, a second session is created instead of reconnecting the disconnected session. What I am thinking is that since I have the Group Policy setting for limit users to 1 session, when you try to reconnect from another machine it tries to open a second session and thus denies the ability to log on through the session broker because a session is already in place. I will test it out and post my results.

here is the KB link

http://support.microsoft.com/kb/977541
0
 
Darius GhassemCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
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

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

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