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
JPetersen92020
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!
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.