![]() So, all said and done, theoretically, would getting the RD Connection Broker to install (in order to generate a private key) likely solve my encryption error? And it does not say what other roles to add. It says one or more parent features are not installed- even though Hyper-V etc. So I ran the latest windows update and tried to install the Remote Desktop Connection Broker so that I can generate the pfx file. The bug is with hotfix June 2013 KB2821895. This Forum indicates that windows may have updated during the reboot, causing an unrecoverable error in installing the Remote Desktop Connection Broker role (needed, apparently, to generate a private key pfx file to import into MMC). Each time I have added the cert to trusted roots and personal for the system user in MMC Certificate snap-in. Used techniques here and here with no luck. I've tried using powershell to generate certs with private keys. I'm not certain it's my imported RD cert, either, though I do know it happens when I try to RDP from my machine. ![]() ![]() I'm not sure how to resolve the above error. The error code returned from the cryptographic module is 0x8009030D. Now I'm finding this in the event log under Administrative Events: "A fatal error occurred when attempting to access the SSL server credential C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys administrator has all privleges.hklm:\System\CurrentControlSet\Control\Terminal Server\fDenyTSConnections is 0.When I inspect the SSL cert, it shows all the details, looks good, expires in 2014. ![]() ![]() Machine was recently rebooted, worked before that.I've tested the port 3389 remotely, it is open. When I go to connect from a remote machine I get an error: "This computer can't connect to the remote computer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |