Alasdairb
asked on
RDS server no longer allows log in
Hi,
I am running a trial 2016 RDS server, all was working okay this morning. I modified a domain GPO to try and lock down the users a bit and rebooted the RDS server. When the server came back up no user could log in any more. Not even the local administrator which makes me think it wasn't anything I did in the domain GPO.
I can only log in using the console on the ESXi host.
I see these errors in the System Event Log
The remote Desktop License Server cannot update the license attributes for the user .....
The license server ad RDS server are on the same machine. I checked to see if the RDS server was in the domain group Terminal Server License Servers and it wasn't (but all was working fine before). I added it anyway and rebooted the RDS server but no change.
Does anyone have any ideas?
Thank you.
Alasdair
I am running a trial 2016 RDS server, all was working okay this morning. I modified a domain GPO to try and lock down the users a bit and rebooted the RDS server. When the server came back up no user could log in any more. Not even the local administrator which makes me think it wasn't anything I did in the domain GPO.
I can only log in using the console on the ESXi host.
I see these errors in the System Event Log
The remote Desktop License Server cannot update the license attributes for the user .....
The license server ad RDS server are on the same machine. I checked to see if the RDS server was in the domain group Terminal Server License Servers and it wasn't (but all was working fine before). I added it anyway and rebooted the RDS server but no change.
Does anyone have any ideas?
Thank you.
Alasdair
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have seen this before. Some setting cannot be undone remotely. You have to set local policy with explicit values to get the server to communicate again. Only then will it get the new policy
ASKER
Hi both,
thanks for replying. I removed the disable access to the command prompt and removed disable access to registry editing tools and rebooted, all OK again. Don't know why the GPO would cause this as the local administrator also could not log in.
The power of a reboot, eh?
Thanks again
Alasdair
thanks for replying. I removed the disable access to the command prompt and removed disable access to registry editing tools and rebooted, all OK again. Don't know why the GPO would cause this as the local administrator also could not log in.
The power of a reboot, eh?
Thanks again
Alasdair