L
Lee Taylor
I created another collection in my RDS Farm and added a single RDS Host. The idea here is that users will use the desktop of this machine not published apps.
I created the collection using a single security group which I created just for this collection
I then added one user to the security group (they are a member of no other groups except domain users)
I then attempted to remote login through the connection broker and get the following error.
"The connection was denied because the user account is not authorized for remote login"
It appears that the connection broker is not passing the login through to the session host, but instead treating it as if it wants to login to the connection broker itself. Not sure what I have done wrong here. It clearly says on server manger "Remote Desktop is published for the users of the collection."
Note the user can remote directly to the RDS host and login, but the point is to have it go through the broker as it's IP is the only one available outside the LAN.
Lee
Continue reading...
I created the collection using a single security group which I created just for this collection
I then added one user to the security group (they are a member of no other groups except domain users)
I then attempted to remote login through the connection broker and get the following error.
"The connection was denied because the user account is not authorized for remote login"
It appears that the connection broker is not passing the login through to the session host, but instead treating it as if it wants to login to the connection broker itself. Not sure what I have done wrong here. It clearly says on server manger "Remote Desktop is published for the users of the collection."
Note the user can remote directly to the RDS host and login, but the point is to have it go through the broker as it's IP is the only one available outside the LAN.
Lee
Continue reading...