Hello world,
I have an issue that I haven't at the beginning of 2012 / 2012 R2.
This issue affect both 2012 R2 & 2016 deployment now.
In a common RDS deployment, you should use RDWeb to connect users, this is everytime working like a charm.
However, when using thin client, you sometimes need to connect direct RDP client to RDS collection.
For this, let's describe what I Always do by the past :
- Configure a RR with fqdn name pointing to all RDSH servers
- Change the default RDSH Certificate by a certificate covering the FQDN (SAN or Wildcard, no matter). For this I usually use a gallery script powered by TP which will configure the SSLCertificateSHA1Hash regkey with the thumprint of the desired
certificate. More explanation of this regkey here : https://support.microsoft.com/en-us/help/3042780/remote-desktop-listener-certificate-configurations-in-windows-server-2
One other method is to configure this regkey with a GPO for RDSH.
It's always works perfelctly.
The issue that I got from a couple of month, is from RD Gateway.
When connecting external users to RD Gateway, I get an 0X607 error.
By searching on the web, I find this issue is caused by the replacement of the RDSH certificate. An exemple here
https://serverfault.com/questions/591572/rds-2012-r2-an-authentication-error-has-occurred-code-0x607
If I disable the regkey, of if I delete the certificate from the personnal store of local computer (which finally do the same thing), RD Gateway works fine.
But in this case, I got the RDSH non-trusted warning certificate message for all my RDP Client which are connecting directly to the RDSH RR. This is "normal", because of the deletion of the certificate / regkey.
Is someone have any solution to make working BOTH RD Gateway AND direct RDP connexion to the farm ?
I'll really appreciate any help.
I'm asking myself if the issue was not linked by the deletion of SHA1 support, last year.
Regards,
Seb