VMware ESXi and vSphere Cluster Management

Install VMware vCenter Server on Windows Using Simple Install

Learn how to deploy legacy Windows-based VMware vCenter Server with Simple Install, configure SSO, databases, services, and access the vSphere Web Client.

Simple Install is a legacy Windows installer mode for deploying the main VMware vCenter Server services together on one Windows host. This lesson covers planning, installation, configuration, validation, and first access for older vSphere releases that provided the Windows installer and Simple Install option.

For broader deployment context, see the Windows vCenter Server Simple Install guide.

Purpose and Scope of Simple Install

vCenter Server is VMware's centralized management platform for ESXi hosts, virtual machines, inventory, permissions, and related vSphere services. In the Windows deployment model, vCenter Server runs as software installed on Windows Server rather than as a prebuilt appliance.

Simple Install places the primary vCenter components on one physical or virtual Windows server. It is intended for a straightforward, single-server deployment, such as a small lab or an uncomplicated environment. The workflow manages component installation order and reduces the decisions required when compared with installing each component separately.

A single-server design is convenient, but it also creates a potential single point of failure. If the Windows host becomes unavailable, centralized vCenter management is unavailable until the host or its recovery method is restored.

Windows vCenter Server Compared with the VCSA

The vCenter Server Appliance (VCSA) is the Linux-based virtual appliance form factor for vCenter Server. Windows-based vCenter Server was an alternative in older releases and could be attractive to organizations that already had Windows administration skills, Windows monitoring, patching, and identity-management processes.

Decision factor	Windows-based vCenter Server	vCenter Server Appliance	Legacy-version consideration
Operating system	Installed on a supported Windows Server host	Delivered as a Linux-based virtual appliance	Confirm the exact release; current releases may not offer the Windows installer
Administration	Uses Windows patching, services, accounts, and operating procedures	Uses appliance-specific administration and lifecycle procedures	Existing Windows expertise was a common reason to select this model
Database options	Could use supported Microsoft SQL Server options, including historical SQL Server Express choices	Uses appliance-supported database architecture	Database support and limits vary by release
Historical feature dependencies	Some older designs required Windows vCenter Server for Microsoft SQL Server support, vCenter Heartbeat, or Linked Mode	Feature availability differed by release	These features are version-dependent; some were changed or retired

Linked Mode was a historical capability for connecting multiple vCenter Server systems for shared visibility and administration. vCenter Heartbeat was a historical availability product for protecting Windows-based vCenter Server deployments. Neither term should be treated as evidence that a feature is available in a current vSphere release.

Components Installed by Simple Install

Simple Install colocates the following services on the same Windows host. Authentication supports the other services, inventory services handle data used by management, vCenter Server coordinates the managed environment, and the Web Client provides browser access.

Component	Primary purpose	Installed by Simple Install	Key dependency or administration note
vCenter Single Sign-On	Centralized identity handling and authentication for vSphere services	Yes	Creates or uses the internal SSO domain and administrator identity
vSphere Web Client	Browser-based administrative interface	Yes	Depends on reachable vCenter services and SSO authentication
vCenter Inventory Service	Supports inventory data handling for vCenter and the Web Client	Yes	Must start correctly for inventory operations and client access
vCenter Server	Manages ESXi hosts, virtual machines, permissions, and vSphere operations	Yes	Depends on authentication, inventory, database, DNS, and certificate configuration

Prerequisites and Planning

Confirm the release and media

Identify the exact vSphere version, build, and edition you intend to install.
Use installation media that matches the planned vCenter Server release and verify that it includes the Windows Simple Install workflow.
Check the release-specific compatibility guide for Windows Server versions, hardware resources, database versions, browser requirements, and supported patches.

Plan the Windows host

Choose a physical or virtual Windows Server host according to operational, availability, and recovery requirements.
Apply supported Windows updates before installation, while avoiding changes that conflict with the selected legacy vSphere release.
Reserve sufficient CPU, memory, and disk capacity for the selected inventory size, operating system, logs, database, and future growth.
Ensure the setup account has local administrative privileges.
Check that no incompatible previous vCenter components, partial installations, or conflicting database instances are present.

Plan identity, network, and time

Assign a static IP address, gateway, and fully qualified domain name (FQDN).
Configure DNS forward lookup for the vCenter FQDN. Configure reverse lookup where required by the release, certificates, or organizational standards.
Verify that the hostname, FQDN, and IP address remain consistent before and after installation.
Synchronize time among the vCenter host, domain services, ESXi hosts, database systems, and administrative clients. Authentication and certificates can fail when clocks differ significantly.
Review host and network firewall rules, including the legacy SSO port and Web Client port used by the selected release.

nslookup <vcenter-fqdn>

The lookup should return the intended address. Correct DNS before proceeding; do not use DNS changes as a post-installation workaround unless the release documentation explicitly supports them.

Plan the database and recovery model

Choose between the historical Microsoft SQL Server Express option and a supported external Microsoft SQL Server deployment.
SQL Server Express was intended for limited deployments and must be used only within the documented host, virtual machine, and inventory limits for the exact release.
Use an external supported SQL Server when the environment requires greater scale, centralized database operations, organizational SQL standards, or a database that exceeds Express limitations.
Plan database ownership, authentication, permissions, backups, transaction-log handling, and recovery testing before installation.
Document the database server, instance, database name, credentials ownership, service identity, and recovery contacts.

Launching the Simple Install Workflow

Log on to the Windows host with an account that has local administrative privileges.
Mount or open the matching vCenter Server installation media.
Start the vCenter Server installer and select Simple Install, not the individual component installation options.
Read the introduction and continue to the license agreement.
Accept the license terms only after confirming that the release and deployment model are correct.
Allow setup to run its prerequisite validation.

Prerequisite validation checks items such as operating-system compatibility, available resources, privileges, existing components, network conditions, and other release-specific requirements. Stop and remediate a failed prerequisite before continuing. Repeatedly advancing past a warning can produce a partial installation that is harder to troubleshoot.

Configure Single Sign-On

vCenter Single Sign-On (SSO) is the authentication service used by the legacy vSphere services. The Simple Install workflow asks you to create or configure the internal SSO administrator identity.

Set a strong password for administrator@vsphere.local.
administrator@vsphere.local is the default administrative identity in the internal vsphere.local SSO domain. It is not automatically the same as a Windows or Active Directory administrator account.
Protect the password in an approved credential-management system and assign clear ownership for its recovery.
Select an SSO site name. A site is a logical grouping used in legacy multisite SSO designs. In a single-site deployment, use the approved site name consistently; in a multisite design, coordinate the value with the existing SSO topology.
Review the SSO service port. The historical default is TCP 7444.

Keep TCP 7444 at its default unless a documented conflict or design requirement requires a change. If an alternate port is supported by the exact release, record it and update firewall rules, monitoring, runbooks, and troubleshooting documentation.

Configure vCenter Server Options

Installer setting	Typical selection	When to choose an alternative	Planning impact
Installation directory	A supported local volume with adequate free space	Use another volume when capacity, performance, or operating-system layout requires it	Include binaries, logs, temporary files, and growth in capacity planning
License key	Enter or apply the key through the installer workflow	Use the release-approved evaluation or later licensing workflow when applicable	Record the key owner and licensing state
Database	SQL Server Express for a small, limited deployment within documented limits	Use a supported external Microsoft SQL Server for production scale or organizational database requirements	Plan connectivity, permissions, backup, maintenance, and recovery
Service account	Local System for a simple, local-only installation when allowed by policy	Use a dedicated Windows service account when policy or external resource access requires it	Document logon rights, password ownership, and database permissions
Inventory size	The size matching the anticipated number of hosts and virtual machines	Choose a larger or smaller supported profile when the expected inventory differs	Affects service and database settings; include growth rather than sizing only for today's objects

Database and service identity choices

Local System is a highly privileged built-in Windows account. It can simplify a small local installation, but its broad privileges may not meet organizational least-privilege requirements. A dedicated service account is a Windows identity under which a service runs and accesses local or network resources. Use one when policy requires controlled permissions or when the service must access external resources.

For an external SQL Server, prepare the database and validate the service account's required permissions before starting the installer. Confirm the SQL Server name, instance, port, database details, authentication model, supported version, and collation requirements for the exact vSphere release.

Review before committing

Verify the installation directory and available disk capacity.
Confirm the license choice.
Review the database platform and all external database values.
Confirm the service account option and ownership of its credentials.
Check the inventory-size selection against the expected number of ESXi hosts and virtual machines.
Read the complete installation summary before selecting the final install or commit action.

Run the Installation

Start the installation after reviewing the summary. Simple Install controls the component installation order, so allow the workflow to complete rather than manually starting components while setup is running. Monitor progress for SSO, the Web Client, Inventory Service, vCenter Server, and database-related steps.

Do not reboot, rename the host, change its IP address, or alter database settings during installation unless the installer explicitly requests it. Record any error message and the component that reported it.

Post-Installation Validation

Validation item	Expected result	How to check	Likely issue if unsuccessful
Windows services	Expected VMware services are installed and running	Open `services.msc` and inspect service state and logon identity	Missing dependency, database failure, certificate problem, or insufficient resources
DNS	FQDN resolves to the intended vCenter address	Run `nslookup <vcenter-fqdn>`	Incorrect DNS record, stale cache, or hostname mismatch
Certificates	Services start and clients can establish HTTPS connections	Inspect the browser certificate and service logs	Untrusted, mismatched, expired, or incorrectly issued certificate
Database	vCenter can connect to and use its configured database	Review vCenter logs, SQL connectivity, and database service status	Wrong instance, blocked port, unsupported database, or missing permissions
Web Client reachability	Legacy Web Client endpoint responds over HTTPS	Use a browser or `Test-NetConnection <vcenter-fqdn> -Port 9443`	Web Client stopped, DNS error, or TCP 9443 blocked
Inventory and host management	Inventory loads and an ESXi host can be added or connected	Sign in and test the inventory and host-connection workflow	Authentication, licensing, network, certificate, or ESXi compatibility issue

Record the selected vSphere release, SSO site, ports, FQDN, IP address, installation directory, license ownership, service account details, database location, credentials ownership, backup configuration, and recovery procedure. Protect this information according to organizational security policy.

Sign In to the Legacy vSphere Web Client

Open the legacy Web Client with the vCenter FQDN:

https://<vcenter-fqdn>:9443/vsphere-client

Username: administrator@vsphere.local
Password: the SSO password configured during installation

TCP 9443 is the historical HTTPS port commonly used by the legacy vSphere Web Client. An initial deployment may use a self-signed or otherwise untrusted certificate, causing a browser warning. Verify that the hostname and certificate details are appropriate for the server before accepting the warning. Replace the certificate with a trusted certificate when organizational policy requires it.

After login, verify that the inventory loads, the licensing state is appropriate, and the vCenter Server can connect to a test or production ESXi host according to the change plan.

Security and Operational Considerations

Use a strong, unique SSO administrator password and store it in an approved password-management system.
Limit access to the Windows host, vCenter services, database, and administrative interfaces.
After initial setup, create appropriate identity sources, roles, and permissions. Use least privilege instead of granting every operator full administrator rights.
Use trusted TLS certificates where required, and monitor certificate expiration.
Protect both the Windows vCenter host and its database with tested backups and recovery procedures.
Test restoration rather than assuming that a completed backup is usable.
Treat a single-server Simple Install deployment as a potential single point of failure. Consider additional legacy availability designs only when they are supported by the exact vSphere release and fit the organization's recovery objectives.

Practical Deployment Examples

Small lab deployment

Create a Windows virtual machine with supported resources, a static IP address, and a stable FQDN.
Verify forward DNS and time synchronization.
Run Simple Install to colocate SSO, Inventory Service, Web Client, and vCenter Server.
Select SQL Server Express only if the planned inventory is within the documented limits of the release.
Open the legacy Web Client endpoint and sign in as administrator@vsphere.local.
Add a test ESXi host and confirm that its inventory is visible.

Production deployment with an external database

Prepare a supported Microsoft SQL Server instance before running setup.
Create the required database and validate the vCenter service account's database permissions.
Confirm SQL network connectivity, listening ports, firewall rules, supported version, and collation.
Select the external database during Simple Install instead of SQL Server Express.
Use a dedicated service account when organizational policy requires controlled access to SQL Server or other network resources.
Document database backup, vCenter backup, and recovery procedures before placing the system into service.

Port conflict planning

If another application is already bound to TCP 7444, identify that process and determine whether it can be stopped, reconfigured, or removed. Use an alternate SSO port only when the exact release supports it and the change is approved. Update firewalls, monitoring, runbooks, and recovery documentation to match the selected value.

Troubleshooting

Prerequisite validation fails

Common causes include an unsupported Windows version, missing updates, insufficient CPU, memory, or disk space, missing local administrative privileges, or a conflicting previous component. Read the specific validation result, confirm compatibility for the exact release, and remediate the failed item before continuing. Remove legacy components only after identifying their purpose and confirming backup or recovery status.

The Web Client URL does not open

Check that the Web Client service is running in services.msc. Run nslookup <vcenter-fqdn> and test Test-NetConnection <vcenter-fqdn> -Port 9443. If name resolution is correct but the port test fails, review Windows and network firewalls. Confirm that the URL uses the correct FQDN and legacy port.

administrator@vsphere.local login is rejected

Verify the exact account format and the SSO password created during setup. Confirm that SSO-related services are running. Check time synchronization among the vCenter server, domain services, and client because significant time skew can affect authentication.

External SQL Server connection fails

Validate the SQL Server name, instance, port, database name, authentication model, and network reachability from the vCenter host. Confirm that the selected service account has the required permissions and that the SQL Server version and collation are supported by the precise vSphere release.

A port conflict occurs during SSO setup

Identify the process listening on TCP 7444. A partial prior installation may have left a service or reservation behind. Stop, reconfigure, or remove the conflicting component only after confirming its role. If an alternate port is supported, document it and update every dependent firewall and operational configuration.

Services do not start after installation

Inspect VMware logs and Windows event logs, starting with the first reported error. Confirm database connectivity, service-account permissions, DNS, certificates, time synchronization, and available resources. Correct the underlying dependency instead of repeatedly restarting the services.

Exam-Relevant Notes

Simple Install is a legacy Windows workflow that installs the main vCenter components together on one host.
The colocated components are SSO, vSphere Web Client, Inventory Service, and vCenter Server.
administrator@vsphere.local belongs to the internal vsphere.local SSO domain.
TCP 7444 is the historical default SSO installer port; TCP 9443 is the historical Web Client HTTPS port.
SQL Server Express is intended only for limited deployments within release-specific documented limits.
Inventory size is an installer sizing choice based on the expected number of managed hosts and virtual machines.
Windows vCenter Server, Linked Mode, and vCenter Heartbeat are legacy, version-dependent concepts; do not assume availability in modern releases.