As you may be aware, the VMware vCenter 5.5 appliance now supports somewhere between 300 and 500 hosts; I know quite range but I am still finding contradicting documentation. Anyways, worst case scenario it will support up to 300 hosts or 3000 VMs – more than enough for a lot of environments. In this post I will review the installation steps for the appliance.
- Download and import the OVF/OVA. If you haven’t done an OVA/OVF import just have your network settings handy and follow the prompts.
- Make sure to set your host name as a FQDN (so host.doman.tld)
- **The process would NOT allow me to use an over provisioned datastore, even though I would be thin provisioning so make sure you have 125GB free**
- When the deployment finishes, power on the VM (or tick the power on check box at the end of the deployment wizard).
- **Another apparent problem, the network settings provided during the OVA/OVF deployment wizard didn’t take, it booted up configured for DHCP**
- Navigate to the URL on the console: https://your.ip.address:5480 (Default username and password is root / vmware)
- Accept the license agreement.
- If, like me you need to change your network settings, you will be told to cancel the wizard (seems a little lazy to me VMware)
- Cancel, go to the network tab and configure your network settings, dont forget to enter the FQDN and create a DNS record for the host name if you plan on using AD.
- Navigate to the new IP you just set (dont forget :5480)
- Click the ‘Launch’ button the right to restart the setup wizard.
- I opted to use the custom settings, selected the embeded database and embedded SSO
- Enter the password for the firstname.lastname@example.org SSO user
- Click start, if all is well in your universe you should get green checkmarks for AD, database and SSO configuration then finally starting services
You should now be able to log in as email@example.com and configure your AD groups/users for access to vCenter, add host and other virtualization goodness. If you did not set an FQDN during setup, you will not be able to configure AD authentication, so make sure to verify that setting.
After a bumpy start with the VM not taking the network settings from the OVF/OVA deployment wizard, deploying the appliance was quite smooth. Remember to give your host a FQDN and create DNS records for it and get on to your 5.5 upgrade projects!