This guide walks you through installing VMware vCenter Server 6.7 on a Windows Server machine, turning it into the central management hub for your vSphere environment. You’ll learn the prerequisites, the exact installation steps, and how to avoid the most common pitfalls. By the end, you’ll have a working vCenter Server Appliance or Windows-based vCenter Server ready to manage your ESXi hosts.
What You’ll Need
- A Windows Server 2012 R2, 2016, or 2019 machine (64-bit) with at least 8 GB RAM and 100 GB free disk space.
- The vCenter Server 6.7 ISO file (downloaded from VMware’s site).
- A static IP address and a fully qualified domain name (FQDN) for the vCenter Server.
- A DNS server that can resolve the FQDN to the IP address.
- Administrator credentials on the Windows machine.
- An external database (like SQL Server) or the bundled PostgreSQL database. For production, an external SQL Server is recommended.
- ESXi hosts you plan to manage, with their credentials ready.
Step-by-Step
- Prepare the Windows Server – Ensure the machine is fully updated, has a static IP, and the FQDN is correctly set in System Properties > Computer Name. Join it to your domain if you plan to use Active Directory authentication.
- Mount the ISO – Right-click the vCenter Server 6.7 ISO and select “Mount” to make it appear as a drive (e.g., E:).
- Run the Installer – Navigate to the mounted drive and run
autorun.exeas Administrator. The vCenter Server Installer menu opens. - Choose Install – Click “Install” next to “vCenter Server” (not the VCSA, which is the appliance version).
- Accept the EULA – Read the license agreement, check “I accept the terms of the license agreement,” and click Next.
- Enter Deployment Type – Select “Embedded Deployment” if you’re using the bundled PostgreSQL database, or “External Deployment” if you have a separate SQL Server. For most small-to-medium environments, embedded is fine.
- Set the System Network Name – Enter the FQDN of the vCenter Server (e.g., vcenter.example.com). This must match the DNS record.
- Configure the Database – If using embedded, the installer sets up PostgreSQL automatically. If external, provide the SQL Server ODBC DSN, database name, and credentials.
- Set SSO Domain – Choose a Single Sign-On domain name (default is vsphere.local). This is the administrative domain for vCenter. You’ll set a password for the administrator@vsphere.local account.
- Select the Destination Folder – Choose where to install the program files. Default is C:\Program Files\VMware.
- Select Data Directory – Specify where to store vCenter Server data (logs, stats, etc.). Use a separate disk if possible.
- Set the Service Account – Choose whether to run vCenter services under the Local System account or a domain service account. For security, a dedicated domain account is better.
- Choose the Ports – Accept the default HTTPS port 443, or change it if needed. Also set the HTTP port (80) for redirects.
- Review and Install – Review the summary, then click “Install”. The installer will copy files, install services, and configure the database. This can take 20-40 minutes.
- Complete and Reboot – When finished, click “Finish”. Reboot the server if prompted. After reboot, vCenter Server services start automatically.
- Verify Installation – Open a browser and go to
https://(or/vsphere-client https://for the older web client). Log in with administrator@vsphere.local and the password you set.:9443 - Add ESXi Hosts – In the vSphere Client, right-click the datacenter, select “Add Host”, and enter the ESXi host IP and credentials. Follow the prompts to add it.
Common Mistakes
- Using an IP address instead of FQDN – vCenter requires a resolvable FQDN. Using an IP will cause certificate errors and functionality issues.
- Wrong DNS records – If the FQDN doesn’t resolve to the correct IP, the installer may fail at the network name step. Verify with
nslookup. - Insufficient disk space – The installer may not warn you until it fails. Ensure at least 100 GB free, especially on the data drive.
- Not running as Administrator – The installer needs elevated privileges. Right-click and “Run as administrator”.
- Ignoring the SSO password complexity – The SSO password must meet complexity requirements (uppercase, lowercase, number, special). If it doesn’t, the installer will reject it.
- Using a non-supported SQL Server version – If using external SQL, make sure it’s a version supported by vCenter 6.7 (e.g., SQL Server 2012 SP2, 2014, 2016).
Tips
- Before starting, take a snapshot of the Windows Server VM (if virtualized) to roll back if something goes wrong.
- Use a dedicated service account for vCenter services, not Local System, to avoid permission issues with external databases or shared storage.
- Set the Windows time zone and time sync correctly. vCenter is sensitive to time skew with ESXi hosts.
- Keep the installation media handy; you may need to repair or uninstall later.
- If you plan to use the vSphere Web Client (HTML5), note that it’s available at
https://./ui - After installation, apply the latest vCenter Server patches from VMware to fix known bugs.
Troubleshooting
- Installer fails at “System Network Name” – This usually means the FQDN doesn’t resolve. Check DNS, run
ipconfig /allto confirm the DNS server, and add a host entry in C:\Windows\System32\drivers\etc\hosts if needed. - Services don’t start after reboot – Open Services.msc and look for VMware services. Check the Windows Event Viewer for errors. A common cause is the service account password expiring or lacking “Log on as a service” rights.
- Database connection errors – If using external SQL, verify the ODBC DSN is set up as a System DSN, not User DSN. Test the connection with the same credentials.
- Cannot log in to vSphere Client – Ensure you’re using the correct SSO domain (e.g., administrator@vsphere.local). If you forgot the password, you may need to reset it via the vCenter Server Appliance (if using VCSA) or reinstall.
- Web client shows blank page – Clear browser cache, try a different browser (Chrome or Firefox), and ensure Java is not required (HTML5 client doesn’t need it). Restart the vSphere Web Client service.
- Installation hangs at 90% – This often happens during database setup. Wait 10-15 minutes; if still stuck, check the installer logs in %TEMP%\vminst.log. Common causes: antivirus interfering, or the SQL Server isn’t reachable.
Frequently Asked Questions
Q: Can I install vCenter Server 6.7 on a domain controller?
A: Technically possible, but not recommended. It creates conflicts with DNS and security policies. Use a dedicated server.
Q: What’s the difference between vCenter Server and VCSA?
A: vCenter Server for Windows is installed on a Windows OS, while VCSA is a pre-built Linux appliance. VCSA is now the default recommendation, but Windows is still supported in 6.7.
Q: Do I need a separate database for vCenter?
A: For small environments, the embedded PostgreSQL database is fine. For production with many hosts, use an external SQL Server for better performance and manageability.
Q: How long does the installation take?
A: Typically 30-60 minutes depending on hardware and whether you use an external database. The installer copies many files and configures services.
Q: Can I upgrade from vCenter 6.5 to 6.7 in place?
A: Yes, you can upgrade the Windows version in place, but it’s recommended to take a snapshot first. The upgrade process is similar to a fresh install but preserves settings.
Q: What ports must be open on the firewall?
A: The vSphere Client uses HTTPS (443). vCenter also uses 80 for redirect, 389/636 for LDAP, and 902 for ESXi communication. Ensure these are open on the Windows firewall.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- Fix Slow Internet Lag on Samsung Galaxy Note
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step