Try Certificates - Current User -> Intermediate Certification Authorities -> Certificates first. The certificate should be here somewhere.Add another Certificates snap-in, this time for My user account.Follow steps 1 to 3 as described in 'Import Certificate on Client.'.Skip the steps above and just move the certificate to the right place: If you already installed the certificate through the warning dialog, you can find the certificate in the current user's store. You should no longer receive the warning. Place all certificates in the following store -> Trusted Root Certification Authorities.Enter the path to the exported certificate, e.g.cer.Select Certificates (Local Computer) -> Trusted Root Certification Authorities -> Certificates.Select Certificates -> Add -> Computer account -> Local computer -> Finish.the computer you're connecting from, an receive the warning popup, do: At least compare the fingerprints, so you can be sure you trust the right certificate.

But you're trusting the network in this case. DER encoded binary X.509 (.CER).Īnother way to get the certificate is to follow steps 6 to 10 on your client computer, on the Remote Desktop warning dialog mentioned in the question.

There should be a single certificate with your computer's name.

Select Certificates (Local Computer) -> Remote Desktop -> Certificates.

The console should now contain Certificates (Local Computer).

Select Certificates -> Add > -> Computer account -> Local computer -> Finish.

If you think you already installed the certificate, skip to 'Move Certificate on Client.' Export Certificate on Serverįirst the certificate needs to be exported to a file. Adding it to the user's 'Trusted Root Certification Authorities' store is not enough! If this sounds confusing don't worry - it is. The certificate needs to be added to your Local Computer's 'Trusted Root Certification Authorities' store.

Devolution rdp