VMware ESXi and vSphere Cluster Management
Install VMware vCenter Server on Windows with Simple Install
Learn how to deploy legacy Windows-based VMware vCenter Server components with Simple Install, configure SSO and databases, access the vSphere Web Client, and validate the installation.
Simple Install is a legacy Windows-based VMware vCenter Server deployment workflow. It installs the main vCenter components together on one physical Windows server or Windows virtual machine. This lesson covers planning, installation, configuration, first login, validation, and common troubleshooting issues.
This procedure applies to older Windows-based vCenter Server releases. Modern vSphere releases generally use the vCenter Server Appliance (VCSA), a Linux-based virtual appliance, instead. Always check the VMware compatibility documentation for the exact release, operating system, database, ports, and sizing values you plan to use.
What Simple Install Deploys
In a Simple Install, the installer places the primary vCenter services on one Windows system instead of requiring you to install each component separately. The system can be a physical host or a Windows virtual machine that meets the release-specific requirements.
| Component | Function | Installed by Simple Install | Operational consideration |
|---|---|---|---|
| vCenter Single Sign-On | Provides centralized authentication for vSphere services and owns the internal SSO domain. | Yes | Protect the SSO administrator credentials and document the SSO domain and site. |
| vSphere Web Client | Provides the browser-based management interface for vCenter. | Yes | Its URL, port, certificate, and service status affect first access. |
| vCenter Inventory Service | Stores and serves inventory-related information for the legacy vSphere client stack. | Yes | It must initialize successfully with the other vCenter services. |
| vCenter Server | Centralizes management of ESXi hosts, virtual machines, inventory, permissions, and related services. | Yes | Its database and sizing profile must match the planned inventory. |
Simple Install is convenient for a small lab or a single-server design, but it also combines several failure domains. A service, database, DNS, certificate, or operating-system problem can affect the whole deployment.
Windows vCenter Server or the vCenter Server Appliance?
The Windows installation model runs vCenter services on a customer-managed Windows server. The VCSA is a prebuilt Linux-based virtual appliance that packages vCenter services in a VMware-provided appliance. The correct choice depends on the vCenter release and the capabilities required by the environment.
| Requirement or consideration | Windows-based vCenter Server | vCenter Server Appliance | Release-specific compatibility note |
|---|---|---|---|
| Administrator operating system familiarity | May be preferred by teams experienced with Windows Server administration. | Uses a VMware-managed Linux appliance interface and lifecycle. | Familiarity alone should not override the supported deployment model for the release. |
| Microsoft SQL Server use | Historically useful when an organization required Microsoft SQL Server. | Uses appliance-supported database architecture and release-specific options. | Check supported database versions, drivers, authentication, and collations. |
| vCenter Heartbeat | Historically associated with Windows-based vCenter high availability. | Not a general reason to choose an appliance for current releases. | vCenter Heartbeat was a legacy product; verify whether the selected release supports it. |
| Linked Mode | Historically selected for certain Windows vCenter Linked Mode designs. | Uses the Linked Mode behavior supported by the appliance release. | Topology and feature support vary substantially between releases. |
| Current VMware deployment direction | Primarily relevant to legacy environments and migration projects. | Normally the preferred model for supported modern vSphere deployments. | Confirm the product lifecycle and migration path before starting a new deployment. |
Historical reasons for selecting Windows included administrator familiarity, Microsoft SQL Server requirements, vCenter Heartbeat availability, and some Linked Mode requirements. These reasons are version-dependent. For a new supported environment, compare the installed release against the current VCSA requirements and migration options.
Before proceeding, review vCenter SSO deployment modes if the server will join a multisite SSO topology.
Deployment Planning and Prerequisites
Successful installation depends more on identity, DNS, time, database, and compatibility planning than on clicking through the wizard. Prepare the following items before launching the installer.
| Area | Requirement | How to validate | Why it matters |
|---|---|---|---|
| Windows support | A supported Windows Server version with required updates and prerequisites. | Check the compatibility matrix for the exact vCenter release. | An unsupported operating system can block installation or leave the deployment unsupported. |
| CPU, memory, and disk | Resources sized for the selected inventory profile, services, logs, database, and growth. | Compare the host or VM specification with release documentation. | Insufficient resources cause slow initialization, poor performance, and service failures. |
| FQDN and DNS | A stable fully qualified domain name with forward and reverse resolution. | Resolve the name and address from the vCenter host and administration workstation. | Services, certificates, ESXi hosts, and clients depend on consistent identity resolution. |
| Static network settings | Stable IP address, correct subnet, gateway, and DNS servers. | Review adapter configuration and test reachability. | Changing the address or hostname later can require service and certificate reconfiguration. |
| Time synchronization | Windows and infrastructure systems synchronized to a common time source. | Compare system time with domain controllers, ESXi hosts, and the NTP source. | SSO authentication, certificates, and secure communication are sensitive to time skew. |
| Administrator privileges | Permissions to install software, create services, write to selected paths, and configure the system. | Run the installer with the required administrative rights. | Missing privileges can cause prerequisite or service-creation failures. |
| Database readiness | Either supported Microsoft SQL Server Express or a prepared external database. | Confirm sizing, credentials, connectivity, version, collation, and permissions. | The database stores core vCenter state and affects scalability and supportability. |
| Firewall and ports | Required client, ESXi, database, SSO, Web Client, and service traffic permitted. | Review release-specific port documentation and test from each required network. | Do not assume a port matrix is universal across vCenter releases. |
| Installation media and licensing | Correct installer media, license information, and access to required files. | Verify the media checksum or source and locate the license key. | The installer must match the intended vCenter and Windows versions. |
Choose a service account model in advance. Local System is a highly privileged built-in Windows account and is simple to configure, but it may not satisfy organizational separation-of-duties policies. A dedicated Windows service account can reduce reliance on a built-in identity, but it requires correct rights, password management, database permissions, and service-logon configuration.
Determine the expected number of ESXi hosts, virtual machines, datacenters, clusters, folders, and other managed objects. The installer uses this information to select an inventory size, which tunes resources and database settings for the planned scale.
Launching the Installer and Choosing Simple Install
- Log in to the prepared Windows server or virtual machine with an account that has the required administrative permissions.
- Mount or open the vCenter Server installation media.
- Start the installation launcher from the media.
- Select Simple Install, not the separate component installation workflow.
- Allow the prerequisite checker to complete.
- Resolve every blocking failure before continuing. Review warnings as well, because they may indicate future support or reliability problems.
- Read and accept the applicable license agreement.
Configuring vCenter Single Sign-On
vCenter Single Sign-On (SSO) is the authentication service used by the legacy vSphere service stack. During Simple Install, configure an internal SSO domain and its initial administrative identity.
SSO administrator identity
The default SSO administrator is administrator@vsphere.local. This is an identity in the internal SSO domain, not automatically a Windows local administrator and not automatically an Active Directory user. Create a strong password, store it in an approved password manager, and record the recovery procedure securely.
The default internal domain is vsphere.local. It is separate from an Active Directory domain unless you later add a directory identity source. Avoid choosing an internal SSO domain that conflicts with the organization’s directory naming strategy.
SSO site and port
An SSO site name is a logical label for a deployment location in an SSO topology. Use an intentional, documented name if this server may participate in multisite SSO. A single-site lab can use one clearly identifiable site name.
The described legacy installer generation commonly uses SSO port 7444, but ports vary by vCenter release. Retain the expected default unless your design requires a change and the release supports it. Record the final value for firewall and troubleshooting work.
Installation Paths and Deployment Review
Choose an installation directory with enough free space for binaries, logs, temporary files, and growth. Place it on storage covered by the organization’s backup and recovery plan. Avoid a path that may be removed, renamed, or disconnected after deployment.
| Installer input | Example value | Purpose | Planning guidance |
|---|---|---|---|
| SSO administrator password | Stored securely; do not use a literal example password. | Authenticates the initial SSO administrator. | Use a unique strong secret and document recovery controls. |
| SSO domain | vsphere.local | Defines the internal authentication domain. | It is not automatically the Active Directory domain. |
| SSO site name | Primary-Site | Identifies the logical SSO site. | Choose a name that remains meaningful in a multisite design. |
| SSO port | 7444 | Provides the legacy SSO service endpoint for applicable releases. | Verify the exact port for the installed version. |
| Install directory | D:\VMware\vCenter | Stores vCenter program files and related data. | Use a supported local path with adequate capacity and backup coverage. |
| Database option | SQL Server Express or supported external SQL Server | Stores vCenter configuration and inventory state. | Use Express only within its release-specific capacity limits. |
| Service account | Local System or a dedicated Windows account | Runs the vCenter services. | Match the choice to security policy and database permissions. |
| Inventory size | Small, medium, or large profile as offered by the release | Tunes resources and database settings. | Base the choice on expected hosts, VMs, and managed objects. |
| License key | Release-appropriate vCenter license key | Activates licensed functionality. | Enter it when prompted or use evaluation mode if the release provides it. |
Before selecting Install, review the component list, SSO settings, site and ports, database choice, service identity, installation path, license mode, and inventory size. Core settings can be difficult to change after deployment and may require service reconfiguration or a redeployment.
vCenter Server Configuration Prompts
License and evaluation mode
Enter the vCenter Server license key when the wizard requests it. Some legacy releases allow evaluation mode for a limited period or feature set. Record the licensing state and convert to the intended license before evaluation access expires.
Database selection
Microsoft SQL Server Express is a bundled database option intended for smaller deployments and subject to release-specific capacity limits. It is often suitable for a small lab when the inventory remains within supported limits.
For a larger or production deployment, prepare a supported external Microsoft SQL Server instance. Confirm the server or instance name, authentication method, database account, permissions, network connectivity, supported version, and required collation before starting the wizard. Database selection affects performance, scalability, backup design, and VMware supportability.
Service logon and inventory scale
Select Local System or the prepared dedicated Windows service account. If using a dedicated account, verify that it can log on as a service where required and has the database permissions needed by the selected vCenter release.
Select the inventory size that matches the expected number of hosts, virtual machines, and managed objects. Choosing a profile that is too small can produce resource pressure as the environment grows; choosing an unnecessarily large profile consumes more resources than required.
Completing Installation and Signing In
- Start the installation after reviewing all settings.
- Wait for SSO, the Web Client, Inventory Service, vCenter Server, and database initialization to finish.
- Do not restart or shut down the Windows system while the installer is configuring services unless the installer reports that it is safe.
- Open the legacy Web Client using the version-appropriate URL. A typical pattern is
https://<vcenter-fqdn>:9443/vsphere-client. - Sign in as
administrator@vsphere.localusing the password created during SSO configuration. - Confirm that the inventory page loads and that the vCenter services remain running.
For example, a lab might use https://vcenter.example.com:9443/vsphere-client. Replace the hostname with the actual vCenter FQDN and verify the port for the installed release. A browser certificate warning may appear when the deployment uses a self-signed or otherwise untrusted certificate; validate that the address is correct before proceeding.
Post-Installation Validation
- Resolve the vCenter FQDN in both forward and reverse directions from administration workstations, ESXi hosts, and relevant infrastructure.
- Confirm that Windows, ESXi, domain services, and database systems have synchronized time.
- Review certificate names, trust status, expiration dates, and browser warnings.
- Check Windows service status for SSO, Web Client, Inventory Service, vCenter Server, and database-related services.
- Test database connectivity and review database logs or vCenter logs for connection errors.
- Open the Web Client with the FQDN and applicable legacy port.
- Add an identity source, such as Active Directory, when operational users need directory-based authentication.
- Create roles and assign permissions rather than relying exclusively on the default SSO administrator. See assigning permissions in vSphere.
- Create datacenters, clusters, folders, and resource pools as required, then add ESXi hosts to the vCenter inventory.
- Document the SSO domain, SSO site, SSO and Web Client ports, database platform, database credentials ownership, service account, installation path, certificates, license state, and recovery procedures.
After adding hosts, verify communication between the management server and ESXi systems. The guide on communication between vCenter Server and ESXi covers the relevant operational relationship.
Troubleshooting Simple Install
Prerequisite validation blocks the installation
Common causes include an unsupported Windows version, insufficient CPU, memory, or disk, missing Windows updates or installer prerequisites, and inadequate administrative privileges. Review each failure in the installer output, compare the system with the exact release requirements, install missing prerequisites, and rerun the installer with the required rights.
External SQL Server connection fails
Check the server or instance name, database network port, credentials, authentication mode, permissions, SQL Server version, and collation. Test connectivity from the vCenter Windows host to the SQL endpoint. Confirm that the database account has the permissions expected by the selected vCenter release.
Web Client does not open on port 9443
Confirm that the URL uses the correct vCenter FQDN and release-specific port. Check whether the Web Client and vCenter services are running, verify DNS resolution, test network reachability, inspect firewall rules, and review service logs. Certificate warnings and browser compatibility can also prevent a usable session.
administrator@vsphere.local login fails
Check the password, exact SSO domain suffix, time synchronization, and SSO service status. The account must be entered as administrator@vsphere.local for the default internal domain. Do not confuse it with a Windows local administrator or an Active Directory account.
Services start slowly or performance is poor
Compare the selected inventory profile with actual host, VM, and object counts. Review CPU, memory, disk throughput, and database utilization. If SQL Server Express or the original resource allocation is beyond its intended scale, plan a supported database or resource upgrade.
Exam-Relevant Notes
- Simple Install is a legacy all-in-one Windows workflow, not the modern appliance deployment model.
- The default SSO administrator is
administrator@vsphere.local; it is separate from Windows and directory-service identities. vsphere.localis the internal default SSO domain and is not automatically Active Directory.- An SSO site name identifies a logical site in an SSO topology.
- SQL Server Express is intended for smaller deployments and has release-specific limits.
- Inventory size affects resource and database tuning, so it must match expected management scale.
- FQDN, forward and reverse DNS, time synchronization, certificates, and firewall access are installation fundamentals.
- Legacy endpoint examples commonly use HTTPS port
9443for the Web Client and7444for SSO, but exact ports are release-dependent.