Reading Time: < 1 minuteIn 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:
Related Posts
-
Updating SSL certificates in VMware productsVMware vSphere 5.1 There is a good post with a complete reference for all vSphere products: Configuring CA signed certificates for VMware vCenter Server 5.0.x - http://kb.vmware.com/kb/2015421 Configuring CA signed SSL certificates for vSphere Update Manager in vCenter 5.1 - http://kb.vmware.com/kb/2037581 Creating certificate requests and…
VMware View 5.x - Cambiare i certificati di defaultIn un post precedente ho discusso di come ignorare il warning dei certificati in un ambiente View 5.x. Ma l'approccio più corretto sarebbe quello di cambiarli con certificati corretti e riconosciuti da una CA pubblica o almeno interna. Questo diviene ancora più vero nelle ultime…
VMware announce the new View 5For more info: http://vmware.com/company/news/releases/vmw-end-user-vmworld-083011.html http://www.vmware.com/products/view/overview.html What’s New in VMware View 5.0 (beyond Marketing) VMware View 5.0 User Experience Enhancements View 5.0 Media Services for Unified Communications