FSAVCS causes SSL/TLS errors during Visual Studio login, need to find policy item to change.
If the presence of F-Secure Client Security 12.3 causes SSL/TLS errors upon Microsoft Visual Studio Express login attempt on some computers, what could be the policy item difference causing this?
I only know the problem occurs on schoolroom computers with a generally "stricter" policy set, while teachers' computers with a more relaxed policy work fine. The sysadmin doesnt't want to relax PCs used by pupils and wishes to find a pinpoint solution or a settings change instead.
Thanks in advance, Yours Sincerely:
Tamas Feher, Hungary.