Install the VMware vCenter Server Appliance on an ESXi Host

Learn how to deploy a VMware vCenter Server Appliance from an OVF or OVA package to an ESXi host using the legacy vSphere Client.

The VMware vCenter Server Appliance (VCSA) is a VMware-provided virtual appliance that delivers vCenter Server management capabilities. Instead of installing vCenter Server directly on physical hardware, you deploy the appliance as a virtual machine on an ESXi host.

After the appliance is deployed and configured, vCenter Server provides centralized management for ESXi hosts, virtual machines, inventory objects, and related vSphere services. This lesson covers the OVF or OVA import stage. Powering on the appliance and completing its network and system configuration are later steps.

How the Deployment Works

The deployment involves four main components:

  • Administration workstation: Runs the vSphere Client and provides access to the downloaded appliance package.
  • vSphere Client: Starts the Deploy OVF Template workflow and sends deployment information to ESXi.
  • ESXi host: Hosts the new VCSA virtual machine.
  • Datastore: Stores the virtual machine configuration files and virtual disks.

The basic sequence is: download the VCSA package, connect to the correct ESXi host, import the OVF or OVA, select a name and datastore, choose disk provisioning, review the summary, and monitor the import task.

OVF and OVA Deployment Formats

OVF means Open Virtualization Format. An OVF package is a collection of files that describes and delivers a virtual appliance. It commonly contains an OVF descriptor, one or more virtual disk files, and a manifest used to verify package contents.

OVA is an archive-based distribution format. It packages the OVF descriptor, virtual disks, and related files into one archive file. An OVA is often simpler to move and select because the administrator handles one file in the deployment wizard.

Format: OVF

Packaging structure: A descriptor and associated files, such as virtual disks and a manifest.

Typical file handling: Keep every referenced file in its expected location.

Deployment consideration: Select the OVF descriptor and make sure the wizard can access all related files.

Format: OVA

Packaging structure: One archive containing the OVF package contents.

Typical file handling: Select the single OVA file from the workstation.

Deployment consideration: The archive must be complete, readable, and compatible with the target environment.

Download the appliance installer package before starting. Store the OVA or the complete OVF package in a location that the administration workstation can access. Do not separate an OVF descriptor from its virtual disks unless the package documentation specifically permits it.

Prerequisites and Deployment Planning

Complete the following checks before opening the deployment wizard.

Requirement: Reachable target ESXi host

Why it matters: The host will receive and run the VCSA virtual machine.

How to verify: Confirm the host address is reachable and that it is the intended deployment target.

Requirement: Appropriate credentials and permissions

Why it matters: The account must be allowed to create a virtual machine and write files to a datastore.

How to verify: Sign in with an authorized ESXi or vSphere account and confirm the required privileges with the environment administrator.

Requirement: Compute and memory capacity

Why it matters: The selected appliance size requires sufficient virtual CPU and memory resources.

How to verify: Review the host's available CPU and memory against the appliance package requirements.

Requirement: Datastore capacity

Why it matters: The appliance configuration and virtual disks must fit on the selected datastore.

How to verify: Check free space and account for the selected disk provisioning method.

Requirement: Network availability

Why it matters: The appliance will need a reachable management interface after it is powered on.

How to verify: Identify the appropriate network and plan addressing, gateway, DNS, and hostname settings for the next configuration stage.

Requirement: Package access

Why it matters: The vSphere Client workstation must be able to browse to and read the OVA or all OVF files.

How to verify: Confirm the package exists locally or at an accessible location before launching the wizard.

Also decide the following values in advance:

  • The target ESXi host.
  • The VCSA package version.
  • The virtual machine inventory name.
  • The destination datastore.
  • The disk provisioning format.
  • The network and addressing plan for post-deployment configuration.

Connect to the ESXi Host

  1. Open the legacy vSphere Client.
  2. Enter the address of the ESXi host selected for the deployment.
  3. Authenticate with an account authorized to deploy virtual machines and write to the destination datastore.
  4. Verify the host name or address in the client. Confirm that it is the correct host before starting the import.

Connecting directly to ESXi is important in this workflow. If the client is connected to a different host or management endpoint, the appliance may be deployed to the wrong inventory or datastore.

Launch the Deploy OVF Template Workflow

Use the vSphere Client option for deploying an OVF template. In the legacy client, this is commonly available from the host's inventory or an actions menu as Deploy OVF Template. Start the workflow after confirming the correct ESXi host is selected.

The wizard reads and validates the appliance package before creating the virtual machine. It may check the package structure, referenced files, manifest information, virtual hardware, and compatibility details.

Select the Appliance Source

  1. Choose the option to deploy from a file or local source.
  2. Use the file browser to locate the downloaded OVA archive or the OVF descriptor.
  3. Select the correct file and continue.
  4. Read any validation messages before proceeding.

When selecting an OVF descriptor, keep its associated virtual disk files and manifest in the expected locations. A descriptor that has been copied without its referenced disks cannot be imported successfully. When selecting an OVA, use the complete archive rather than a partially copied file.

Validation errors can indicate a missing component, an invalid path, a damaged download, an unsupported package, or a compatibility problem. Stop and correct the issue rather than continuing with an incomplete package.

Review OVF Template Information

The wizard displays metadata extracted from the appliance package. Review the appliance identity and, when available, publisher information. Also check the virtual hardware details, required storage, and other deployment metadata.

This is the first opportunity to confirm that the package is the intended VCSA version and appliance size. Compare the displayed information with your deployment plan. Continue only when the package identity, resource requirements, and compatibility information are appropriate for the target ESXi host.

Name the Virtual Appliance

Assign the virtual machine inventory name. This is the label used to identify the appliance in the ESXi or vSphere inventory. Choose a name that communicates its environment, site, or management role, such as vcsa-lab or vcenter-management.

The inventory name is not necessarily the same as the appliance operating system hostname or DNS name. The hostname, IP address, gateway, and DNS settings are configured during the later initial appliance setup.

Choose the Datastore and Disk Format

Select the datastore that will contain the VCSA virtual machine configuration files and virtual disks. The datastore must be accessible to the selected ESXi host and must have enough free capacity.

The wizard may offer thin or thick virtual disk provisioning, depending on the package and host capabilities.

Provisioning type: Thin provisioning

Initial datastore use: Physical capacity is consumed as data is written, rather than reserving the full logical disk size immediately.

Capacity planning impact: Initial free-space usage may be lower, but future growth must be monitored carefully.

Appropriate use case: A lab or another environment where thin provisioning is permitted and capacity monitoring is reliable.

Provisioning type: Thick provisioning

Initial datastore use: Capacity is reserved on the datastore when the virtual disk is created.

Capacity planning impact: More capacity is committed immediately, but the storage reservation is clearer and more predictable.

Appropriate use case: Production or policy-controlled environments that require reserved capacity or a specific provisioning standard.

Choose the format according to organizational policy, datastore capacity, and workload requirements. Do not select thin provisioning merely because it allows the wizard to continue if the datastore cannot accommodate later growth. Likewise, do not select thick provisioning unless enough capacity is available for the reservation.

Review and Complete the Deployment

Before submitting the wizard, review the final summary.

Wizard stage: Source package

Administrator action: Confirm the selected OVA or OVF descriptor.

Decision or validation point: Verify that it is the intended VCSA version and that package validation succeeded.

Wizard stage: Target host

Administrator action: Confirm the destination ESXi host.

Decision or validation point: Make sure the host is reachable and has adequate resources.

Wizard stage: Appliance name

Administrator action: Confirm the inventory name.

Decision or validation point: Use a meaningful name and remember that it is separate from the future hostname.

Wizard stage: Datastore

Administrator action: Confirm the storage destination.

Decision or validation point: Check datastore visibility and free capacity.

Wizard stage: Disk format

Administrator action: Confirm thin or thick provisioning.

Decision or validation point: Match the choice to capacity planning and policy.

  1. Read the complete deployment summary.
  2. Correct any source, host, name, datastore, or disk-format error.
  3. Submit the wizard to begin the import and virtual machine creation process.
  4. Monitor the task list in the vSphere Client until the import completes.

Deployment duration depends on the package size, the connection between the workstation and ESXi, and datastore performance. Do not assume that a slow task is failed without checking the task details and host activity.

Post-Deployment Validation

After the task reports success:

  • Verify that the VCSA virtual machine appears in the ESXi host inventory.
  • Confirm that the import and virtual machine creation tasks completed successfully.
  • Check the appliance virtual machine's selected name, datastore, virtual disks, and virtual hardware.
  • Confirm whether the virtual machine is powered on according to the deployment plan.

Successful OVF import does not necessarily mean that vCenter Server services are fully configured or reachable. The next phase is to power on the appliance, complete its initial network and system configuration, and validate management connectivity. This includes applying the planned hostname, IP addressing, gateway, and DNS settings.

For the broader installation workflow, continue with vCenter Server Appliance installation.

Practical Deployment Examples

Deploy from a Single OVA

An administrator downloads the VCSA OVA to an administration workstation and connects the vSphere Client directly to the intended ESXi host. The administrator selects the OVA, assigns the inventory name vcsa-lab, chooses a datastore with adequate free space, and selects thin provisioning because it is allowed for the capacity-constrained lab. After reviewing the summary, the administrator starts the import and watches the task until completion.

Deploy from an Extracted OVF Package

An administrator selects the OVF descriptor instead of an OVA archive. The associated virtual disk files remain alongside the descriptor, allowing the wizard to resolve all referenced paths. The administrator reviews the template identity and storage requirements before continuing.

Distinguish the Naming Stages

During OVF deployment, the virtual machine receives the inventory label vcenter-management. During later appliance setup, the administrator configures the operating system hostname, IP address, gateway, and DNS settings. These are related naming decisions, but they are not the same field.

Troubleshooting

The Wizard Cannot Locate Required Files

Likely causes include moving the OVF descriptor away from its virtual disks, selecting a file that is not a valid descriptor or OVA, or denying the workstation access to the package location.

  • Use the original complete package.
  • Keep all extracted OVF components together.
  • Select the correct OVA or OVF file through the wizard's file browser.

The Datastore Cannot Be Used or Has Insufficient Space

The datastore may not have enough free capacity, may not be mounted on the selected host, or may require more immediately available space for the chosen disk format.

  • Check free space and datastore visibility from the target host.
  • Choose another datastore accessible to that host.
  • Reassess thin or thick provisioning according to policy and capacity requirements.

Deployment Does Not Start or Fails During Import

Possible causes include an invalid or incomplete package, a connectivity interruption between the workstation and ESXi, insufficient permissions, or host resource and compatibility limitations.

  • Read the detailed vSphere Client task error.
  • Validate the downloaded appliance package and obtain a complete copy if necessary.
  • Confirm that the account can create virtual machines and write to the datastore.
  • Verify host capacity, datastore availability, and client-to-host connectivity.

The Appliance Appears but Is Not Ready for vCenter Server

The virtual machine may not be powered on, initial appliance configuration may be incomplete, or network, DNS, and service settings may not yet be valid.

  • Confirm that deployment completed successfully.
  • Check the virtual machine power state.
  • Proceed with the initial appliance configuration workflow.
  • Validate management network reachability and name resolution.

Exam-Relevant Notes

  • VCSA is a prebuilt virtual appliance delivered as a virtual machine on ESXi.
  • OVF normally consists of multiple related files; OVA is a single archive containing an OVF package.
  • The datastore stores the appliance configuration and virtual disks.
  • Thin provisioning consumes datastore capacity as data is written; thick provisioning reserves capacity at creation time.
  • The inventory name is distinct from the appliance hostname and DNS name.
  • Import completion confirms deployment of the virtual machine, not necessarily completion of vCenter Server configuration or service availability.