Since the introduction of vCenter Server appliance (vCSA), there has always been a debate on which one is better (Windows based deployment or vCSA) and what one’s advantages over the other is. Folks at VMware have spent lot of their time and effort on making vCSA better and are committed to making sure all the features are available with vCSA in order to relieve the customers of the dilemma of choosing between the two. This is very evident with every
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.
In my last two posts i wrote about upgrading ESXi and vCD from 5.1 to 5.5. In this post we will look at vCSA upgrade. Download the vCSA from VMware download page : https://my.vmware.com/web/vmware/downloads Deploy the Virtual Center Server Appliance 5.5 OVF/OVA on your supported ESXi like you did with your vCSA 5.1. After deploying the open your web browser and point it to https://<vCSA-ip>:5480. default username is root and password is vmware. After logging in accept the EULA. Choose the