We all know that SSL certificates enable secure communication between a browser and a web server. During the initial setup, all the VMware components are installed with self-signed certificates and it is a best practice to replace the default certificates with custom CA signed certificates. This process of replacing default certificates in vSphere 6 is very simple compared to the tedious process that was present in the previous versions of vSphere (5.1 and 5.5). To make it easier to follow,
vCSA 6.0 is out and boy, is it awesome!! Best thing about the new version : its scalability. You can go upto almost 10,000 machines and manage them all using vCSA 6.0. If that isn’t awesome I don’t know what is ;) When I initially deployed vCSA I ran into this error which said: After scratching my head for a while on why I ended up facing this error I realized that I had not resolved the hostname/FQDN on my
vCenter Server Appliance (vCSA) has always gotten stronger and more awesome with every release of vSphere. This improvement eliminates the need to deploy/install a windows based vCenter Server unless there is a specific need to do so. Now with the announcement of vSphere 6.0, vCSA has become Uber Awesome. So what makes it so awesome? Starting from version 6.0 you can manage up to 1000 hosts and 10,000 VMs using the vCSA and its embedded database. Yes you read it right.
The most awaited VMware vSphere 6.0 is finally here.The public beta was announced sometime around July 2014 and thousands of interested folks tested and analyzed the products and their new features. VMware fixed a lot of bugs and also changed some features here and there to make it fit for the final release. Everyone had lot of expectations and asks from this new version. I feel the product teams have put enough effort to do what they do best and