On a Windows Server 2012(R2) I have users who connect to it via RDP.
When using Chrome on that server just ONE user receives certificate warning when connecting to an internal HTTPS website. Chrome on that terminal server is latest 64bit version (as told by the Chrome Help | About page).
All the rest of users can connect to the site normally from this and other terminal servers, with no warnings (the lock icon is locked).
It is NET::ERR_CERT_SYMANTEC_LEGACY error, but our server uses RapidSSL wildcard certificate, which was created in 2017, not Symantec one.
I tried to clear all Chrome caches for that user and restart Chrome, but that didn't help.
Any ideas how to fix this or what could be the problem?
Sounds like the Google "distrusting" of Legacy Symantec PKIs.
https://productforums.google.com/forum/#!msg/chromebook-central/c_OUU8KPIqQ/uJkWySlOBgAJ