0

I installed the Remote Desktop Session Host server role on a windows 2012 r2 machine. After that, I rebooted the VM and now when I try to log in via remote desktop, after a little while in the log in process, I get an "Access is denied" yellow message with an OK button below. I was able to log in before that.

Any idea on how I can fix this? I am local admin on the server but I cannot launch remotely the Server Manager. I was able to run the Computer Management console.

Thanks

boggy
  • 111
  • 2
  • 6
  • Are you able to log on locally via the console, rather than remotely via RDP? Windows does differentiate depending on this. – mythofechelon Aug 15 '17 at 18:49
  • Could you please be more specific, how do I connect via the console? I was able to connect via the Computer Management console. Thanks – boggy Aug 15 '17 at 19:07
  • 1
    Try logging on to it physically (monitor, keyboard, and mouse) or, if possible, remotely via something like out-of-band management, Virtual Machine console, LogMeIn, TeamViewer, etc. – mythofechelon Aug 15 '17 at 19:08
  • Unfortunately I cannot proceed with any of these options. Any other ideas? – boggy Aug 15 '17 at 19:18
  • Is the server connected to an AD DS domain? If so, can you log on using a domain administrator account? – mythofechelon Aug 15 '17 at 19:19
  • I am not a domain admin but I asked the help of someone with higher access level than me. Yes, the computer belongs a domain. – boggy Aug 15 '17 at 19:25
  • Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/63879/discussion-between-mythofechelon-and-costa). – mythofechelon Aug 15 '17 at 19:26

2 Answers2

1

I know this is an old question, but it just got bumped up to the home page.

If you find yourself locked out of a Remote Desktop server, just run mstsc.exe /admin. This will log you in to the console session, bypassing all RDS licensing issues.

Massimo
  • 70,200
  • 57
  • 200
  • 323
0

I solved this issue by uninstalling the Remote Desktop Session Host feature via powershell commands. Unfortunately I haven't been able to find the real cause of this issue.

boggy
  • 111
  • 2
  • 6