RDP users cannot logon
Good morning,
I am trying to deploy my first Terminalserver outside my test lab. For this I am running Windows Server 2012 R2 Standard in VMware. The license server resides on another host (the DC, also 2012R2, also VMware), all the other RD roles are installed locally. Web Access etc. are not required.
On my first try, I installed the RDP session host role itself without using the RDP rollout wizard in System manager. There I received on every user logon the message that no licensing host was configured. I did not find any means to configure a licensing host.
So I tried again, removed the role and started over using the system manager tools that are meant for running RDP. I installed the RDP gateway, the session broker and all the rest of it to this host, rebootet twice and I received message that all is well.
Now I cannot connect to this host at all anymore (except via mstsc /admin). The RDP client asks for credentials and denies access if the credentials are false. On correct credentials the client seems to connect up to "configuring remote session" - then it fails and I get something like "the client cannot connect - retry or contact your system administrator".
What really gets me, though, is that I am receiving no messages in eventlog - nothing at all. Security log shows successful login and logoff for the user, all the rest is void of any information. This happens on domain users as well as local system administrator user.
I have assigned the license server in System Manager and set the licensing mode to "User" which matches the installed and activated CALs. I did not find any place to grant access privileges to certain users.
What am I missing?
Thanks,
Ralph
I am trying to deploy my first Terminalserver outside my test lab. For this I am running Windows Server 2012 R2 Standard in VMware. The license server resides on another host (the DC, also 2012R2, also VMware), all the other RD roles are installed locally. Web Access etc. are not required.
On my first try, I installed the RDP session host role itself without using the RDP rollout wizard in System manager. There I received on every user logon the message that no licensing host was configured. I did not find any means to configure a licensing host.
So I tried again, removed the role and started over using the system manager tools that are meant for running RDP. I installed the RDP gateway, the session broker and all the rest of it to this host, rebootet twice and I received message that all is well.
Now I cannot connect to this host at all anymore (except via mstsc /admin). The RDP client asks for credentials and denies access if the credentials are false. On correct credentials the client seems to connect up to "configuring remote session" - then it fails and I get something like "the client cannot connect - retry or contact your system administrator".
What really gets me, though, is that I am receiving no messages in eventlog - nothing at all. Security log shows successful login and logoff for the user, all the rest is void of any information. This happens on domain users as well as local system administrator user.
I have assigned the license server in System Manager and set the licensing mode to "User" which matches the installed and activated CALs. I did not find any place to grant access privileges to certain users.
What am I missing?
Thanks,
Ralph
Peter Hutchison
Load Server Manager, Configuration, Users and Groups and add the Domain Users group to the Remote Desktop users group to allow users to remote onto the server.
ASKER
Do you mean the local group "Remote Desktop Users"? The Domain-Users-Group is already a member. But that would have resulted in a proper error message saying that the user is missing privileges, wouldn't it?
I am receiving no error at all - at least not on the server side.
I am receiving no error at all - at least not on the server side.
You mentioned Host Licensing is missing. This is a requirement for Remote Destkop services for client CALs. It can be installed via Server Manager as a component of Remote Desktop Services. See picture, you may also want the Connection Broker installed for clients to reconnect to their session.
See picture.
See picture.
ASKER
That is at least not what I meant to say.
On my first try, I did not find means to tell the RDS-Server where to find it's licensing host. Then I tried over, installed all the roles and was now successful in configuring the licensing host. Licensing service resides on the DC, that is another VM.
On my first try, I did not find means to tell the RDS-Server where to find it's licensing host. Then I tried over, installed all the roles and was now successful in configuring the licensing host. Licensing service resides on the DC, that is another VM.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Took some research...