osx auto trust rdp connection

New Contributor


Is there a way to make OSX auto-trust Microsoft Remote Desktop Connection (to specific addresses) regardless of certificate in JAMF? I know the client can hit view certificate and click always trust but is there a way to automate this or have a policy that always allows this?




Try this.

On a Mac, Connect RDC and trust the cert. That should add it to the current user’s keychain. Open Keychain Access, locate the cert and drag to the desktop. In a Jamf Pro, create a new configuration profile and add the cert to the Certificates payload. Scope and deploy to a test Mac.

Certs deployed via profile should be trusted automatically.

New Contributor

Cool. im going to try that

@rotorstudiosdid this work for you?  Is the certificate set to Always trust?

Contributor II

Just posting in case helpful. Inherited an environment where Mac's have always RDP's to Windows and gotten the "The certificate couldn't be verified back to a root certificate..." warning and it's been ignored.

Note: Windows > Windows RDP should be using Kerberos authentication, which is why you're not seeing the error there.

I believe the below is the proper way to fix (with the upside of working on all machines you're RDP'ing to, as long as they have the GPO). As opposed to just marking the cert it can't verify as trusted. At least this is what myself and our server guy came up with after putting our heads together. We no longer get those certificate warnings.

1. Have AD CS configured and a Root CA.

2. Create a certificate template to be the RDP cert / cert used to authenticate an RD Session Host server. 

3. GPO on Windows machine you are RDP'ing to - Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security - Server Authentication Certificate Template - pointing to template mentioned above.

4. (Group policy update on each VM/machine is needed before warning will go away upon connecting.)

5. Get your Root CA cert, import it onto your Mac, mark it trusted in keychain access, then export.

6. Create a config profile in Jamf with that cert and push out.

7. Ensure you are connecting by FQDN in your macOS RDP client (and not regular domain name or IP address) or you'll still get the error.

8. There should no longer be a warning upon initiating the RDP connection.