Many websites will say that vCenter 6x requires DNS lookup, but these steps and screenshots prove that you can install a new vCenter 6.7 with only an IP address and no DNS.
Start vCenter install from .iso file using Windows 10
1. Download the install .iso file for your vCenter (available from the downloads area of vmware.com. On a Windows PC (I am using Windows 10), double-click the .iso file to mount it. It will show up in a virtual DVD drive.2. Open your virtual DVD drive and expand the vcsa-ui-installer folder.3. Expand the win32 folder (for a Windows PC). If you are using Linux or Mac as your desktop, select the appropriate folder.4. Run the installer.exe file as administrator (on Windows). This will start the program that allows you to deploy, upgrade, or migrate vCenters.
vCenter install stage 1
5. Initial options display. In our case, we are installing a brand new vCenter with no DNS, only IP address. So pick Install.6. Go through the introduction and end use license agreement. For the deployment type, select Embedded Platform Services Controller (this is normally the correct choice unless you have a very large, complex environment)7. Normally you will be installing a new vCenter directly onto an ESXi host. Put the IP address of your ESXi host into the “ESXi host or vCenter Server name”. Leave the port 443, enter the correct root account and password for that ESXi host.
8. Configure options for “set up appliance VM” — this gives the name for the VM on your host (and will affect naming of the datastore folders). Set the root password for the vCenter appliance here. Select deployment size – for most situations, the default of Tiny is fine unless you have more than 10 hosts. Select datastore – pick the datastore to create the VM into.
9. Configure network settings: Here is the important part. Network should be a virtual port group (switch) that your desktop can communicate with. IP assignment should be static. In the FQDN field, enter the IP address of your vCenter server. In the IP address field, enter the IP address of your vCenter server. Enter the rest of the fields as appropriate for your environment. If you don’t have a DNS server at all, use your gateway or another bogus IP.10. Confirm your settings and start deployment. For me, I was able to complete Stage 1 in about 15 minutes, despite using a slow (100mbps) network.
vCenter installation stage 2
11. Stage 2 starts. If you have an NTP server, set it here, otherwise make sure your ESXi host has correct time and use it.12. Most deployments create a new SSO domain.13. Enter “vsphere.local” into SSO domain name, enter a password for administrator. Your logon username will be administrator@vsphere.local with the password you set.14. Select whether you want to participate in the Customer Experience Improvement Program (secure facilities say no). Then review your settings and Finish to start configuration.15. How long does it take to complete Stage 2, Appliance setup? For me, it took 10 minutes. If it takes more than 45 minutes, your deployment is probably failing.16. Stage 2 completes. Note that the link assumes you are using DNS. It won’t work unless you have updated your HOSTS or put an entry into your DNS server. Since we are avoiding DNS, lets just say it won’t work.
Now to connect to your new vCenter VCSA without DNS..
17. As you can see, if you don’t have DNS and just click the link, the page won’t open.18. Change the URL to the IP address of the vCenter server. Now the page displays.19. If you follow the “Launch vSphere client HTML5” link, or simply enter the URL https://vCenter_IP/vsphere-client , the vCenter logon page will display.20. Enter administrator@vsphere.local and the password you set in Step 13. Make sure you have Flash enabled on your browser.21. The vCenter page will open successfully with no DNS.22. How to access the VCSA appliance to perform management functions? Use the URL https://vCenter_IP:5480 and log on with root and the password you set in Step 8.23. Here is the management website for the VCSA
Selfish plug time (sorry!)
Thanks for reading this article! I hope it helps you! If you have tips or feedback, please comment or send me an email so that others can benefit.
I am a consultant in the Maryland/DC area in the USA. My specialties are Windows migrations (to 2016 and to Office 365 / Azure), VMware migrations, Netapp and SAN, and high availability / disaster recovery planning. If you would like help with your complex project, or would like a architectural review to improve your availability, please reach out! More information and contact can be found on the About page. – Amira Armond
Talk to an Expert
Tell us where you are with compliance and we’ll map out the next steps for your team.
