Exam objective 1.3 — Deploy and manage vCenter Server — is the heart of what it means to virtualise a datacentre. Without vCenter Server, managing more than a few virtual machines becomes a nightmare of logging into each host individually. Mastering this chapter means you understand how to turn a pile of servers into a unified, manageable pool of resources, which is exactly what the VCP-DCV exam wants you to prove.
Jump to a section
A simple way to picture vCenter Server Deployment and Management
A City Planning Director is the person in charge of making sure a city runs smoothly and grows in an organised way. They don't fix potholes or drive the buses themselves; they manage the managers who oversee the roads, the traffic lights, the public transport, and the building permits. When a new neighbourhood needs power and water, the director designs the zoning rules, decides where things go, and controls who gets access to what. If a busy street needs all its traffic signals reconfigured, the director doesn't climb the pole — they send the work order to the traffic engineer team.
Now, think of vCenter Server as that City Planning Director for a datacentre. Each individual server (called an ESXi host) is like a single building. The virtual machines (VMs) running on each host are the offices and apartments inside that building. Without a planning director, you would have to walk into each building separately to check who lives there, turn lights on or off, and move furniture. The director gives you a single dashboard where you see the whole city at once. You can move a running business application from one building to another without anyone noticing a power cut, just as a director can reroute traffic before a parade. You can set up alarm systems that ping you if the building's foundation shakes. The director is not the physical building — it's the brains that turn scattered hardware into an orderly, flexible, and secure city.
vCenter Server is a software application that acts as a central management platform for VMware ESXi hosts. An ESXi host is a physical server that runs a hypervisor, which is a thin layer of software that allows multiple virtual machines (VMs) to share the same physical hardware. Think of ESXi hosts as the bricks in a wall; vCenter Server is the mortar that holds them together and lets you treat the whole wall as a single surface.
Before vCenter Server existed, administrators had to manage each ESXi host individually. If you wanted to create a new VM, you had to log directly into the ESXi host's management interface, find free resources, and configure networking and storage right there. That worked for two or three hosts, but imagine a company with fifty hosts and five hundred VMs. You would spend your whole day bouncing from one screen to another, trying to balance workloads manually. You could easily overload one host while another sits mostly empty.
vCenter Server solves this by introducing the concept of a single pane of glass. You install vCenter Server on either a Windows Server or as a pre-packaged virtual appliance called the vCenter Server Appliance (VCSA). The VCSA is the modern, preferred deployment method because it comes with its own operating system, bundled database (usually PostgreSQL), and all the services you need. Deploying the VCSA is like buying a fully furnished flat — you just plug it in and turn it on. The Windows version requires you to provide your own Windows Server license and a separate Microsoft SQL Server database, which adds complexity.
Once vCenter Server is running, you add your ESXi hosts to it. At that point, vCenter Server discovers the hosts and lets you build higher-level constructs such as:
Clusters: A cluster is a group of ESXi hosts that share resources. When you place hosts in a cluster, vCenter Server can automatically move VMs between those hosts to balance the workload, using a feature called DRS (Distributed Resource Scheduler).
Datastores: These are storage containers that hold the VM files. Datastores can live on local hard drives inside the host, or on shared storage arrays like SAN (Storage Area Network) or NAS (Network Attached Storage).
Folders and Tags: You can organise VMs, hosts, and networks using folders and custom tags, making it easy to apply permissions or policies to groups of objects.
vCenter Single Sign-On (SSO): This domain authenticates users across all VMware components. Administrators log in once and can access all the hosts in the datacentre without entering credentials again.
Deploying vCenter Server requires careful planning. First, you decide on the deployment size — tiny, small, medium, large, or extra-large — based on how many hosts and VMs you need to manage. The size determines how much CPU, RAM, and disk storage the VCSA gets. You also choose a network configuration: an IP address and DNS settings so other devices can reach it. During deployment, you join the vCenter Server instance to an existing SSO domain or create a new one. You must also ensure that all ESXi hosts can communicate with the vCenter Server over the management network.
After deployment, the real management begins. vCenter Server lets you perform life-cycle operations on VMs: create, clone, migrate, snapshot, and delete. It also provides monitoring tools that track CPU, memory, disk, and network usage across the entire environment. When something goes wrong — say, a host loses connectivity — vCenter Server fires an alarm that can send an email or run a script. You can also use vCenter Server to schedule maintenance: put a host in maintenance mode, which moves all its VMs to other hosts, so you can patch or reboot the physical server without downtime.
vCenter Server is not just about convenience; it's about the features that make enterprise virtualisation possible. Without it, you cannot use advanced features like vMotion (live migration of a running VM), HA (High Availability — automatic restart of VMs if a host fails), or DRS. The exam tests your understanding of deployment prerequisites, the difference between the appliance and the Windows version, and how to perform common management tasks from the web interface.
Download the VCSA ISO from VMware Customer Connect
Begin by logging into your VMware account and navigating to the Download section. Select vCenter Server Appliance for the correct vSphere version (e.g., vSphere 8.x). Download the ISO file to your local workstation. This ISO contains the installer and the OVA (Open Virtual Appliance) template for the appliance.
Run the VCSA Installer (Stage 1 – Deploy the Appliance)
Enter ESXi Host Details and Configure Appliance Network
The installer prompts for the target ESXi host's IP address or FQDN, username (root), and password. Provide the virtual appliance name, root password for the appliance VM, and select the deployment size (tiny, small, medium, large, extra-large). Choose the datastore for the VM files and configure the temporary network settings for the appliance (IP address, subnet mask, gateway, DNS). Stage 1 powers on the new VM.
Run the VCSA Installer (Stage 2 – Configure the Appliance)
After Stage 1 completes, the installer automatically advances to Stage 2. Log into the appliance's configuration interface using its IP address. Set the time zone and NTP servers. Choose to create a new vCenter Single Sign-On (SSO) domain or join an existing one. If creating a new domain, provide a domain name (e.g., 'vsphere.local') and an administrator password. Wait for the configuration to finish.
Access the vSphere Web Client and Create a Datacentre
Open a web browser and navigate to the vCenter Server's IP address or FQDN on port 443 (https://<vcenter-ip>/ui). Log in with the SSO administrator credentials (administrator@vsphere.local). The first task is to create a datacentre object by right-clicking the vCenter Server root and selecting 'New Datacentre'. Name it (e.g., 'Production-DC'). This container will hold all your clusters and hosts.
Create a Cluster and Add ESXi Hosts
Right-click the datacentre and choose 'New Cluster'. Give it a name (e.g., 'Cluster-01') and decide whether to enable vSphere HA and DRS immediately. Once the cluster appears, right-click the cluster and select 'Add Host'. Enter the IP address, username, and password for each ESXi host you want to manage. The host is added to the cluster and appears in the inventory. Repeat for all hosts.
Configure Advanced Features (HA, DRS, DPM)
To unlock the full power of the cluster, configure vSphere HA to automatically restart VMs if a host fails. Enable DRS to balance workloads across hosts. If you want energy savings, enable Distributed Power Management (DPM) to power off unused hosts during low-demand periods. Verify that all hosts show as 'Connected' and that no alerts appear.
You are the sole IT administrator for a mid-sized logistics company, SpeedFreight, that runs 30 ESXi hosts supporting 250 virtual machines. The company is migrating from an old set of standalone servers to a fully virtualised environment. Your first job is to deploy vCenter Server so that you can manage everything from one place.
You download the VCSA ISO file from VMware's website. Mount the ISO on your desktop workstation and run the installer. The installer presents you with two phases: Stage 1 deploys the appliance to an ESXi host or to a vCenter Server instance, and Stage 2 configures the appliance. You choose to deploy directly to one of the ESXi hosts that will eventually be managed by this vCenter. The installer asks for the ESXi host's IP address, username (root), and password. It also asks for the name you want to give the new vCenter Server, its root password, and its network settings — IP address, subnet mask, gateway, and DNS server.
You select a 'medium' deployment size because the current environment has 30 hosts and 250 VMs. That gives the appliance 8 vCPUs and 24 GB of RAM. You let the installer assign a thin-provisioned 300 GB virtual disk. Stage 1 finishes in about 15 minutes, and the new vCenter Server VM powers on automatically.
Next, you proceed to Stage 2. You log into the appliance's configuration interface using its IP address. Here you:
Set the time zone and NTP (Network Time Protocol) servers so the VM stays synchronised.
Create a new vCenter Single Sign-On (SSO) domain, because this is the first vCenter Server in your company. You name it 'speedfreight.local' and choose an administrator password.
Wait for the configuration to finish — another 10 minutes.
Now vCenter Server is ready. You open a web browser and navigate to its IP address, launching the vSphere Web Client. The first thing you do is create a datacentre object named 'SpeedFreight-DC'. Inside that, you create a cluster called 'Production-Cluster'. You drag your 30 ESXi hosts into the cluster. As each host joins, vCenter Server asks for the host's credentials and then takes over management.
With the hosts inside the cluster, you enable the following services:
vSphere High Availability (HA). This configures the cluster so that if one host fails, the VMs on that host are automatically restarted on other hosts in the cluster.
vSphere Distributed Resource Scheduler (DRS). This sets the automation level to 'Fully Automated', meaning vCenter Server will automatically move VMs between hosts to balance CPU and memory loads without you lifting a finger.
vSphere DPM (Distributed Power Management). This allows DRS to power off hosts that are not needed and power them back on when demand increases, saving electricity costs.
Now for a typical day: a project manager tells you that a new client management application needs to be deployed. You right-click the cluster, select 'New Virtual Machine', and walk through the wizard. You choose the compute resource (cluster), the datastore (a shared SAN volume called 'Gold-01'), and the guest operating system (Windows Server 2022). The VM is created in about a minute. Later, you need to patch the physical server hosting a critical database VM. You right-click the ESXi host, choose 'Enter Maintenance Mode', and vCenter Server uses vMotion to migrate the database VM to another host without interrupting its network connections. The migration takes 30 seconds, and the database keeps running. You reboot the host, apply patches, bring it back online, and exit maintenance mode. The user never noticed a thing.
The exam expects you to understand exactly these steps: how to deploy the VCSA, how to add hosts, how to create clusters, and how to enable HA and DRS. They also test your knowledge of the upgrade path and what happens if the vCenter Server itself fails (yes, you can back up the VCSA).
The VCP-DCV exam focuses heavily on the practical decisions around deploying and managing vCenter Server. You will see questions that test your knowledge of the deployment wizard, the difference between the appliance and Windows versions, and the prerequisites that must be in place before you click 'Finish'. The exam is not asking you to remember every checkbox in the UI; it wants to know that you understand why you make each choice.
Key exam topics include:
Deployment options: When to use VCSA (vCenter Server Appliance) versus the Windows-based version. The modern exam almost always favours VCSA because it is the current recommended method. You need to know that VCSA is the way forward, and the Windows version is deprecated (still tested as legacy knowledge).
Sizing: Matching the deployment size (tiny, small, medium, large, extra-large) to the number of hosts and VMs. For example, a medium deployment supports up to 400 hosts and 4,000 VMs. Traps often give you a scenario with 500 hosts and ask which size to use — the answer is 'large'.
DNS and IP address: vCenter Server absolutely requires forward and reverse DNS resolution. A common trap is a scenario where the DNS record is missing, and the question asks why the deployment fails. The answer is always DNS.
SSO domain: You must decide whether to create a new SSO domain or join an existing one. If the organisation already has a vCenter Server, you should join the existing SSO domain for unified authentication. A trap question might list 'Create a new SSO domain' as correct when the scenario clearly says 'company already has a vCenter'.
Licensing: vCenter Server itself requires a license. ESXi hosts also need licenses. The exam tests the difference between vCenter Server Standard, vCenter Server Foundation, and vCenter Server Essentials. Standard is the full-featured version; Foundation and Essentials are for smaller environments.
Linked Mode: This allows multiple vCenter Server instances to be managed from a single view. The exam expects you to know that Linked Mode requires all vCenter Servers to be in the same SSO domain.
Backup and restore: vCenter Server has a built-in backup and restore tool (file-based backup). You must know that you back up the VCSA configuration, not the VMs themselves. A trap question might suggest using VM snapshots as a backup strategy for vCenter Server — that is wrong because snapshots can grow and break the appliance.
Upgrading vCenter Server: Upgrading from an older version to a newer one is a multi-step process using the VCSA installer's 'Upgrade' option. You cannot skip versions; you must go through each version step (e.g., 6.7 to 7.0, then 7.0 to 8.0). The exam likes to present a scenario where a company jumps from 6.5 to 8.0 and asks if that is possible — the answer is no.
Managed objects: The exam quizzes you on the hierarchy: Datacentre > Cluster > Host > VM. You must know that you create a datacentre first, then a cluster, then add hosts. Doing it in the wrong order will break the structure.
Trap patterns to watch for:
Questions that present the Windows-based vCenter as the only option when the scenario lists a small budget. The correct answer is VCSA because it does not require a separate Windows license.
Questions that claim you can use a local MySQL database with the VCSA — VCSA uses an embedded PostgreSQL database, not MySQL.
Questions that say you can change the IP address of a deployed vCenter Server without redeploying. You cannot; the IP is set during Stage 1 and changing it later requires redeployment or complex reconfiguration.
Questions that state you should run vCenter Server on the same host as the VMs it manages. That is bad practice because if the host goes down, vCenter Server also goes down, losing management. The correct practice is to run vCenter Server on a separate, dedicated host or a cluster with high availability.
Memorise the exact names of the deployment phases: Stage 1 deploys the appliance, Stage 2 configures the appliance. Know that Stage 1 can target an ESXi host or an existing vCenter Server instance (for upgrade or migration). Stage 2 is only accessible after Stage 1 finishes and the VM boots.
vCenter Server is a central management platform that turns multiple standalone ESXi hosts into a unified, manageable pool known as a cluster.
The vCenter Server Appliance (VCSA) is the recommended deployment method over the Windows-based version because it does not require a separate operating system or database license.
Stage 1 of VCSA deployment creates the virtual appliance on a target ESXi host, and Stage 2 configures the appliance's settings, SSO domain, and network.
vCenter Server requires a valid DNS record with forward and reverse lookup; missing or incorrect DNS is the most common cause of deployment failures.
vCenter Server Clusters enable advanced features like vSphere High Availability (HA) and Distributed Resource Scheduler (DRS), which are mandatory for enterprise environments.
You must back up the vCenter Server appliance configuration separately from individual VMs, using the built-in file-based backup tool; VM snapshots are not a valid backup strategy for the vCenter Server itself.
Linked Mode lets you view and manage multiple vCenter Server instances from a single web interface, but each instance still independently manages its own hosts and clusters.
These come up on the exam all the time. Here's how to tell them apart.
vCenter Server Appliance (VCSA)
Comes with its own Linux-based operating system (Photon OS), no separate OS license needed
Uses an embedded PostgreSQL database, no separate database server required
Deployed as a virtual appliance via OVA, simple two-stage process
Fully supported for all current vSphere versions (8.x); receives all new features
Windows-based vCenter Server
Requires a full Windows Server license and a supported SQL Server license (additional cost)
Database (SQL Server) must be installed and configured separately, adding admin overhead
Installed via an MSI installer on a Windows VM; more complex debugging
Deprecated by VMware for newer versions; no new features added; only maintained for legacy compatibility
vSphere High Availability (HA)
Purpose: Automatically restart VMs on other hosts if a host fails (fault tolerance for availability)
Monitors host heartbeat and VM status; triggers restarts when host goes offline
Configuration involves admission control to reserve spare capacity for failover
vSphere Distributed Resource Scheduler (DRS)
Purpose: Automatically migrate running VMs between hosts to balance CPU and memory load (performance optimisation)
Uses vMotion to move VMs live without downtime; can also power off hosts if idle (DPM)
Configuration involves automation level (Manual, Partially Automated, Fully Automated) and migration thresholds
Linked Mode
Links multiple vCenter Server instances into a single management view for administrators
Does not move VMs between vCenter instances; they remain under original management
Requires all vCenter instances to be in the same SSO domain and time-synchronised
Cross-vCenter vMotion
Moves a running VM from one vCenter Server to another (inter-vCenter movement)
Requires a shared datastore and compatible network between source and destination
Can work across different vCenter instances, even in different SSO domains, with proper configuration
Stage 1 (Deploy)
Creates the virtual appliance on a target ESXi host or another vCenter Server
Sets the initial network configuration (IP, DNS, gateway) for the new appliance
Completes in about 15-20 minutes; powers on the new VM automatically
Stage 2 (Configure)
Configures the software inside the appliance: time zone, NTP, SSO domain
Requires the appliance to be reachable via the IP set in Stage 1
Completes in about 10-15 minutes; provides final web access to vCenter
Mistake
vCenter Server is required to run a single ESXi host.
Correct
You can manage a single ESXi host directly using the host's built-in web interface (ESXi Web Client) without vCenter Server. vCenter Server is needed when you have multiple hosts and want to use features like HA, DRS, or vMotion.
Beginners often assume that every ESXi host needs vCenter Server because training materials emphasise vCenter features. They forget that a standalone host works perfectly fine.
Mistake
vCenter Server can be installed on an ESXi host that it manages.
Correct
You can deploy vCenter Server as a VM running on an ESXi host, but that host will then be managed by that same vCenter Server. This is common in single-host test labs, but in production it creates a circular dependency: if the host fails, vCenter also fails. It is technically possible, which is why beginners think it is recommended.
The word 'deploy' sounds like installing something onto the hardware, not realising that vCenter Server is itself a VM that lives on top of ESXi.
Mistake
The Windows-based vCenter Server is still the recommended deployment method in the current exam.
Correct
VMware stopped developing new features for the Windows version years ago. The VCSA is the only option with full support for vSphere 8.x. The exam tests both for historical knowledge, but the correct answer in any 'best practice' or 'recommended' scenario is VCSA.
Many older training materials and YouTube videos still teach the Windows version. Beginners follow those old resources and assume they are current.
Mistake
vCenter Server automatically backs up all the virtual machines it manages.
Correct
vCenter Server can back up its own configuration (using file-based backup), but it does not back up VMs. VM backups require a separate tool like vSphere Data Protection or a third-party solution such as Veeam.
The word 'backup' in the context of vCenter is confusing. People think it is an all-in-one solution when it is only the control plane, not the data plane.
Mistake
You can deploy vCenter Server without providing DNS settings.
Correct
vCenter Server requires forward and reverse DNS resolution to function properly. The deployment wizard asks for a fully qualified domain name (FQDN) and will fail if that name does not resolve in DNS. The VCSA uses DNS for service discovery and certificate validation.
Many beginners come from small office environments where DNS is not configured. They think they can just use an IP address and skip DNS entirely, not realising how deeply VMware relies on it.
Mistake
Linked Mode allows one vCenter Server to manage ESXi hosts that belong to another vCenter Server's cluster.
Correct
Linked Mode only connects the management views of two or more vCenter Server instances. Each vCenter Server still manages its own hosts and clusters. You can see both environments in one web client, but you cannot move a host from one vCenter to another through Linked Mode — that requires cross-vCenter migration tools.
The term 'Linked Mode' sounds like a feature that merges everything into one big system. Beginners assume it is a union, when it is actually just a federation of separate management points.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes. vCenter Server requires its own license key (e.g., vCenter Standard). ESXi hosts also each require a license. The exam tests that you know the difference between vCenter licensing tiers (Standard, Foundation, Essentials) and host licensing.
No. The VCSA installer deploys the appliance to an ESXi host, not to a local workstation. The installer runs from your laptop but the actual VM is created on the target ESXi host. You cannot run vCenter Server on a regular operating system like Windows or macOS.
You can reset the SSO administrator password using the vCenter Server Appliance management interface (VAMI) if you have root access to the appliance VM. If you also lose the root password, you must redeploy vCenter Server from a backup. There is no known backdoor.
Yes, as long as the vCenter Server can communicate with each host's management network interface over the network (typically port 443 for host management). The hosts do not need to be on the same subnet or even the same location, but latency should be low for features like vMotion.
No. Snapshots are not backups. A snapshot creates a delta file that grows over time and can corrupt the appliance if it runs out of space. Use the built-in file-based backup feature instead, which exports the appliance configuration in a safe, compressed format.
You use the same VCSA installer ISO to perform an 'Upgrade' from Stage 1. The installer will migrate configuration from the old appliance to a new one. You cannot skip major versions; you must go through each version incrementally (e.g., 6.7 to 7.0, then 7.0 to 8.0).
The most common cause is that the FQDN you provided for the vCenter Server appliance does not have a matching forward and reverse DNS record. Check that the IP address you assigned resolves correctly both ways (nslookup <IP> returns the FQDN, and nslookup <FQDN> returns the IP). If DNS is not set up, the deployment will fail.
You've finished vCenter Server Deployment and Management. Continue through the VCP-DCV study guide to build a complete picture of the exam.
Done with this chapter?