VMware ESXi and vSphere Cluster Management

Deploy a Virtual Machine from a Template in VMware vSphere

Learn how to deploy a new VM from a VMware vSphere template, select compute and storage resources, apply guest customization, and validate the result.

Deploying from a VM template is the standard way to provision repeatable virtual machines in VMware vSphere. A template is a master VM image prepared with an operating system, applications, drivers, and baseline settings. The Deploy from Template workflow creates a new virtual machine from that source while leaving the original template available for later deployments.

This differs from creating a VM manually. A manual VM requires you to create virtual hardware, install or attach an operating system, and configure the guest. A template deployment starts with an approved baseline and can apply unique guest identity and network settings during deployment.

Requirements Before Deployment

Access to a vCenter Server-managed environment and permissions to deploy virtual machines.
An existing VM template visible in the vSphere inventory.
At least one suitable ESXi host or cluster.
An accessible datastore or datastore cluster with sufficient usable capacity.
A suitable virtual network, such as a port group, available to the destination compute resource.
Enough CPU, memory, and storage capacity for the new VM.
A guest OS customization specification if the deployed guest needs a unique hostname, network identity, domain membership, or other personalization.

A vCenter Server is the centralized management platform for hosts, clusters, templates, inventory, and deployment tasks. The vSphere Client is its web-based management interface. An ESXi host is the physical hypervisor on which the VM runs, while a cluster is a group of hosts managed as a shared compute resource.

Review related vSphere permissions and host inventory requirements if the required objects or actions are unavailable.

Locate the Template and Start the Workflow

Sign in to the vSphere Client connected to vCenter Server.
Open the VM Templates view, or browse the datacenter and VM folder that contains the template.
Locate the prepared template. Search by name if necessary.
Open the template's action menu or context menu.
Choose Deploy from Template to open the deployment wizard.

If the object does not appear, confirm that you are browsing the correct datacenter and folder and that your account can view templates. Also verify that the source is actually a template rather than an ordinary VM. A VM may need to be converted to a template before this workflow is available.

Step 1: Name and Inventory Placement

Enter a unique name for the new VM. Follow your organization's naming convention and avoid reusing the template name. Then select the destination datacenter and, where available, a VM folder.

A datacenter is a top-level vSphere inventory container for hosts, clusters, virtual machines, networks, and storage. A VM folder is an organizational container for virtual machines and templates. The folder controls how objects are organized in inventory; it does not determine which host runs the VM or where its files are stored.

Step 2: Select Compute Resources

Choose the destination compute resource offered by the wizard. Depending on the inventory and permissions, this may be a cluster, resource pool, ESXi host, or vApp.

A cluster provides a shared pool of hosts and may allow vSphere to select or move the VM among eligible hosts.
A specific ESXi host restricts the initial placement to that physical server.
A resource pool applies a logical allocation of CPU and memory within a host or cluster.
A vApp groups related virtual machines and can provide application-level organization and controls.

Review compatibility warnings before continuing. Check host hardware compatibility, guest OS support, CPU and memory availability, maintenance mode status, and access to the networks and datastores required by the template.

Step 3: Select Storage Placement

Select a destination datastore or datastore cluster. A datastore stores VM configuration files, virtual disks, and related files. A datastore cluster groups datastores for policy-based or automated storage placement.

When the wizard exposes these options, select an appropriate storage policy and virtual disk format. A thin provisioned disk initially consumes less datastore capacity and grows as data is written. A thick provisioned disk reserves or initializes capacity according to the selected thick format.

Confirm that the destination has enough usable free space for the VM and expected growth.
Verify that the datastore is accessible from the selected host or all eligible hosts in the cluster.
Check that the selected storage policy is compatible with the datastore.
Consider performance, resilience, backup, and capacity requirements rather than selecting only the datastore with the most free space.

Storage placement is separate from inventory placement: the VM can be in one VM folder while its files reside on a datastore selected in this step.

Step 4: Review Clone and Deployment Options

Review the options presented by the wizard. The important guest-related choice is whether to apply guest operating system customization. Customization is optional. Enable it when the new VM must receive identity and network settings that differ from the template.

Leaving customization disabled can be appropriate for a network-neutral Linux baseline or for an environment where configuration management performs setup after first boot. It is unsafe to omit customization merely to save time when multiple guests would otherwise share a hostname, machine identity, or static IP address.

Step 5: Apply Guest OS Customization

If customization is enabled, select an existing guest OS customization specification. This is a reusable vCenter configuration that applies guest-specific identity and network settings during deployment.

Setting category	Typical values	Reason for configuration	Common conflict
Hostname	Unique computer or host name	Identifies the guest on the network and in management systems	Duplicate name or invalid naming format
Domain or workgroup	Directory domain or local workgroup	Places the guest in the intended identity boundary	Invalid credentials, DNS failure, or incorrect domain
IP addressing	DHCP or static IP, prefix or mask, gateway	Provides the required network identity	Duplicate address, wrong subnet, or unavailable address
DNS	DNS server addresses and search domains	Enables name resolution and directory communication	Unreachable or incorrect DNS servers
Time zone	Operating-system time-zone setting	Keeps timestamps and scheduled tasks correct	Incorrect regional setting or time drift
Administrator or authentication settings	Local credentials, domain credentials, or identity options	Allows controlled first access and enrollment	Expired, invalid, or improperly stored credentials

Customization behavior depends on the guest OS type and the availability and condition of VMware Tools. VMware Tools is guest software that provides integration features and is commonly required for reliable customization. Confirm that the specification matches the guest OS and that VMware Tools is installed, supported, and running in the template.

Deploy from Template Wizard Decisions

Wizard stage	Required choice	Why it matters	Validation checks
VM name and folder	Unique VM name, datacenter, and VM folder	Prevents inventory confusion and supports organization	Check naming standards and permissions
Compute resource	Cluster, host, resource pool, or vApp	Determines where the VM can run and which resources it receives	Review compatibility, capacity, and host access
Datastore and disk format	Datastore or datastore cluster, policy, and thin or thick format	Determines file placement, performance, resilience, and capacity use	Check free space, accessibility, and policy compatibility
Guest customization	Enable or skip customization; select a specification if enabled	Makes the guest distinct from the template	Verify OS match, VMware Tools, hostname, and network values
Final review	Confirm all deployment selections	Catches errors before files are created	Check name, compute, storage, network, and customization

Review, Finish, and Monitor the Deployment

Before starting, review the summary for the VM name, inventory destination, compute destination, datastore or datastore cluster, disk settings, networks, and customization selection. Then select Finish or the equivalent action to start the deployment task.

Monitor Recent Tasks or the task status pane. Wait for the task to complete successfully before treating the VM as ready. If the task fails, open its details and associated events for the specific compatibility, storage, permission, or network error.

Deployment checklist:
1. Confirm the source template and unique VM name.
2. Confirm datacenter, VM folder, compute destination, and datastore.
3. Confirm network port groups and storage policy.
4. Confirm customization specification or intentional skip.
5. Start deployment and monitor Recent Tasks.
6. Validate the VM before power-on or handoff.

Post-Deployment Validation

Confirm that the new VM appears in the expected inventory folder.
Verify the intended datastore, virtual disks, virtual hardware, and network port group.
Check that the VM is connected to the correct virtual network and that the destination host has access to it.
Power on the VM when the change window and operational plan permit.
Confirm that guest customization completed successfully.
Inside the guest, verify the hostname, IP address, subnet or prefix, gateway, DNS configuration, time zone, and domain or workgroup membership as applicable.
Check VMware Tools status and confirm that required applications and services are ready.
Keep the original template unchanged so it remains a consistent source for future deployments.

Practical Deployment Examples

Standard Windows Server VM

Select the Windows Server template from the VM Templates inventory. Give the VM a name that follows the organization convention and place it in the server VM folder. Select the production cluster and an approved datastore. Apply a Windows customization specification containing a unique computer name, domain settings, DNS configuration, and an approved static IP address. After deployment, verify domain membership and network connectivity before handing over the server.

Linux Application Server Without Guest Customization

Deploy a preconfigured Linux template to a development cluster and select a development datastore. Skip the customization specification when the VM will be configured manually or by configuration-management tooling after first boot. If the template is network-neutral, attach the appropriate port group after deployment and complete the guest network configuration before enabling application services.

Several Identical Baseline VMs

Use the same template for each deployment, but assign every VM a unique inventory name. Supply separate customization values or automation variables for each hostname and network identity. Check the IP allocation list before powering on the systems so that no two guests use the same static address.

Troubleshooting Deployment Problems

The Template Cannot Be Found

Browse the correct datacenter and VM folder, then search the VM Templates view.
Confirm that your role allows you to view and deploy from the template.
Verify that the intended source was converted to a template rather than remaining an ordinary VM.

No Compatible Host or Cluster Is Available

Read the compatibility message in the wizard.
Check template hardware and guest settings against the candidate hosts.
Confirm that the host is not in maintenance mode and has sufficient CPU and memory.
Verify required datastore and network access, then try another eligible host or cluster.

The Datastore Is Unavailable or Has Insufficient Space

Verify that the datastore is mounted and visible from the destination compute resource.
Choose storage with enough usable capacity for the VM and its expected growth.
Review storage policy and disk-format requirements for placement compatibility.

Guest Customization Does Not Apply

Confirm that VMware Tools is installed, supported, and running.
Check that the customization specification matches the guest OS type.
Review credentials, domain details, hostname rules, IP values, and DNS settings.
Inspect task events and guest logs. Correct the specification and redeploy or remediate the VM as appropriate.

The New VM Has No Network Connectivity

Verify the virtual NIC's port group and connected state.
Confirm that the selected ESXi host has access to the required network and VLAN.
Validate the IP address, subnet or prefix, gateway, DNS values, and possible address conflicts.

For broader storage and VM operations, see how to clone a virtual machine, datastore concepts in vSAN, and the VMware ESXi online course.