$SecurePassword = $PlainPassword | ConvertTo-SecureString -AsPlainText -Force $CertificateFileName = 'RDCManCertificate.pfx' You need to protect the certificate with a password, that way it will be protected from being imported by anyone else than you Create and export a self signed Certificate for Remote Desktop Connection Manager This way way we know we can import it even on other computers. So, lets us first create the certificate, export it and then remove it and finally import it. There just to have to be a replacement for makecert.exe… PowerShell to the Rescue! So lets use Certificate instead, but, how do you create a Certificate that can be moved around easy and at the same time is secure and protect itself?Īccording to the help file, we shall of course use the one utility on the planet that I hate most, I don’t like that fact that you need to spend hours to download an SDK kit just to run a app to create file that takes 1 second. I need to have to be able to use the configurations files on more then one computer and they need to be protected. If I move the RDCMan file to another computer then all the passwords are lost, on the other hand, that is also more safe.

RDCMan can encrypt the passwords stored in files either with the local user’s credentials via CryptProtectData or an X509 certificate One really great feature is that you can save the password for each and every connection, and if you read the help file, it states: The mini view of 3 computers in RDCMan 2.7 Security is important Using Remote Desktop Connection Manager makes that process easier, you can basically work with all machines in a single windows. Note: Script has been updated to include $YEARS, the suggestion came from Thanks!Įven if IT is changing into more “Pets” and “Cattle’s”, we still have a massive amount of system that will be managed using Remote Desktop for a long time.

Rdcman download 2.7