2 Posts
0
21802
Thinclients Fails to connect after Certificate Update
Following Google's warning to update we updated the Certificate on our RDS Environment. Since then the Wyse Thinclients won't login and throw an error - SSL Connection to "mydomain.com" SSL UNKNOWN CERTIFICATE AUTHORITY. SSL Certificate is Valid and works fine on the RDS Web as Web Access works fine, But Issue is only with the ThinClients.
Placed the certificate in the "cacerts" folder on our wyse ftp site where the wnos.ini file is and added a line in the wnos.ini file AddCertificate=XXXXXXXXXXXXXXXX.crt. Still, the Wyse Clients don't authenticate.
Wyse Environment is as Follows.
Wyse Device Manager - 5.7
Wyse Device R10L
Wyse Image - 8.0-210
RDS Environment - Windows Server 2012 R2
Please let me know if there is any thing else that i could perform to fix this issue.
Thanks in Advance
riyadhibm
2 Posts
0
August 3rd, 2018 01:00
I just went through this with my Server 2012 Connection Broker. Windows automatically creates the self-signed certificate with the server's name, so I just went to the Certificates snap-in within MMC on the Connection Broker server, went to Personal>Certificates, and exported the certificate with the server's name (only one there). I then used the AddCertificate=certname.cer command in the wnos.ini file. I put the certificate in /wnos/cacerts on my FTP server.