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:
- Official documentation
- KB 1008705 Guidelines for generating and importing an SSL certificate for the View Connection Server
- VMware View 5.1 and SSL Certificate Replacement (Tom Fojta’s Blog)
- SSL certificates in VMware View environments (That’s my View)
