When I use RD Tab (or Remote Desktop) to connect to a server and I don't connect to the server by the fully qualified domain name that it expects, then I am prompted with a certificate error (in Windows Vista or Windows 7) that I must click the "Yes" button on (or I can left-arrow, enter).

This is common for me because a lot of the servers I remote into only have a DNS record in the form of:
hostname.domain.com

And the servers think of themselves as:
hostname.subdomain.domain.com

I know I can get rid of the certificate error by asking the relevant sysadmin to register both DNS records and use the second form to RD into the system. However, given the landscape of where I work that will not be practical.

To reproduce this, you could log into server by it's IP instead of it's DNS record. That will show you the certificate error I'm talking about.

I'd like to request considering the ability for RD Tabs to automatically ignore certificate errors. Or even better would be to auto-accept them, but flash a quick warning that it did that. Perhap make this a global config that people in my situation could turn on. I realize that this is probably a low priority request.

Thanks for the consideration and for making a great product!
-EWG

The behavior is baked into the MS RDP libraries, so I can't get rid of the modal pop-ups (believe me, I'd like to), but I can offer a couple workarounds.

1. Under Advanced on the Connection Properties, select "Legacy encryption." Since you do not care about verifying the authenticity of the remote server (which is what TLS offers), don't use TLS. 🙂 Of course, the remote computer has to also be configured to accept legacy connections.

2. Under Tools->Options, check "Cache connection properties (username, domain, certificate warnings)." The modal certificate warning dialog will now have a checkbox that allows you to say "don't warn me again" or something to that effect.

Great, option #2 is a good workaround for my situation. Thanks for pointing that option out.
-EWG