This post is also available in: Italian

Reading Time: 1 minute

In a previous post I’ve described how ignore the warning in a View 5.x environment. But the right way so solve this “issue” remain replace the self generated and signed certificates with new one signed from a trusted CA (a public on, but also an internal one could be fine, if you can push its certificate on all the clients). This may become a mandatory requirement for future version of View (although it is not yet confirmed).

For how generate and replace the certificates see:

Andrea MauroAbout Andrea Mauro (2904 Posts)

Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-18. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-18. Nutanix NTC 2014-18. PernixPro 2014-16. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.


Share