RDP Issue Connecting to Server 2012 R2 in VMWare ESXi 6

byt3
byt3 used Ask the Experts™
on
I can't remote desktop into my Server 2012 R2 Core. I turned on remote desktop and disabled the firewall. I can ping and even connect to shares on it.

I've found these event log errors, but cannot find a fix on Google for:

--System
The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on SSL connections. The relevant status code was Object already exists.

** The Remote Desktop folder in certificates mmc is empty??

--Application and Services Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS > Operational
RDP_TCP: An error was encountered when transitioning from StatePreparingX224C in response to Event_ERROR_SendingX224CC (error code 0x0).

If anyone can help it would be much appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Technical Systems Analyst
Commented:
I remember experiencing this issue before as well. The recommendation was as follows:

1) Navigate to: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\
2) Copy the keys to a different directory for backup purposes - do not skip this step!
3) Delete the files in C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\. (just the files inside of the MachineKeys directory, do not delete this entire path)
4) Reboot the server and then attempt an RDP connection.

Author

Commented:
I did found this solution on google and I swear I tried it, but it didn't help me. Went to try it again, but I get access denied to Copying or Deleting the file in MachineKeys. So I used psexec to run powershell as SYSTEM, then use icacls to give the SYSTEM user access to the file to move it:

psexec -i -s powershell.exe
cd C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys
mkdir ..\Old_keys
Get-ChildItem -Path . | % {icacls $_.Fullname /grant "NT AUTHORITY\SYSTEM:F"}
Get-ChildItem -Path . | Move-Item -Destination ..\Old_keys
Restart-Computer

Open in new window


I swear I tried it before and it didn't fix it, but this time it did.
Thanks for the help
Matt MinorTechnical Systems Analyst

Commented:
Awesome job!

 I always love when people come back with something more than just "didn't work."
AmarnadhJCloud Infra

Commented:
Hi Matt, This worked thanks for the fix, but I could find another issue that within the box where we fixed the Keys, From that box I am unable to take remote for another machine. any Idea...

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial