I have a 2012 R2 RDS server. Previously we used a locally self signed certificate to allow clients to setup Remote App and Desktop connections. This certificate was not able to be extended and so expired. We purchased a SSL certificate and gave it FQDN of server.companyname.co.uk. The RDS server is called server.companyname.local. On setting up new clients we get an error saying certificate is in one name and server name is different. However setup will complete. But when remote app programs are run they fail because says certificate is in one name and server name connecting to is different.
I imagine this issue has been encountered by everyone who has moved from self signed to 3 party SSL on a RDS.
I have a work around but would like a proper solution to this.