How to Clone a Virtual Machine to a Template

You can clone a virtual machine to a template once it’s been created. Templates are primary copies of virtual machines that allow you to generate virtual machines that are ready to use. While the original virtual machine is preserved, you can make changes to the template, such as adding extra applications in the guest operating system.

After you’ve created a template, you can’t change it. To edit an existing template, first convert it to a virtual machine, then make the necessary modifications before returning the virtual machine to a template. Clone a template to a template to keep the original state of the template.

Prerequisites to Clone a Virtual Machine to a Template

Stop any load generators that are active in the virtual machine before performing the clone procedure.

Check that you have the following permissions:

Virtual machine>Provisioning>Create template from virtual machine from the source virtual machine.

Virtual machine>Inventory> Create from a template that already exists in the virtual machine folder.

Resource>Assign virtual machine to resource pool on the destination Esxi host, cluster, or resource pool.

Datastore>Allocate space on all datastores where the template is being created.

Procedure to Clone a Virtual Machine to a Template

  • Start Clone Virtual Machine To Template wizard.
Clone Virtual Machine To Template
  • Enter a name for the template and a datacenter or folder to deploy it in on the Select a name and folder page.

The name of the files and folders on the disk is determined by the template name. The template files are named win16tmp.vmdk, win16tmp.nvram, and so on if the template is entitled win16tmp. The names of the files in the datastore do not change when you update the template name.

Folders are used to hold virtual machines and templates for various groups within an organization, and they can be assigned rights. You can place all virtual machines and templates in a datacenter and organize them differently if you desire a flatter hierarchy.

  • Select a host or a cluster resource for the template on the Select a compute resource page.

The results of the compatibility checks are displayed in the Compatibility pane.

Important: If you’re cloning a virtual machine with an NVDIMM device and virtual PMem hard disks, the destination host or cluster must have PMem resources available. Otherwise, you will be unable to complete the work.

If the cloned VM does not have an NVDIMM device but does have virtual PMem hard drives, PMem resources must be accessible on the destination host or cluster.

Otherwise, the storage policy and Datastore set for the source virtual machine’s configuration files will be applied to all of the template’s hard disks.

  • Select the datastore or datastore cluster where the template configuration files and all virtual disks will be stored on the Select storage page. Click on Next.
Clone a virtual machine that has 
vPMem hard disks
Clone a virtual machine that does 
not have vPMem hard disks

Important: When you clone an encrypted virtual machine, you can’t change the storage policy.

  • Review the template settings on the Ready to finish screen before clicking Finish.

In the Recent Tasks window, you can see how far the clone task has progressed. When the task is finished, the template is added to the inventory.

What is a VMware template?

A VMware template (also known as a golden image) is a blueprint copy of a virtual machine that may be used to clone, convert, or deploy more virtual machines.

The virtual machine’s virtual disks and settings from its.vmx configuration file are handled using permissions in a VMware template. When customizing settings and other options to generate new Windows or Linux server VMs, templates save time and prevent mistakes. They may also be used as long-term in-place VM backups and to guarantee that VMs are built and deployed consistently across an organization. A VMware template can’t be used unless it’s converted to a virtual machine.

How do I clone a VM without Vcenter?

Although virtual machine cloning is a vCenter Server-only feature, you can still get around it if you’re using unmanaged ESXi.

Today, we’ll discuss 3 workarounds which are allowing you to clone VMs when running unmanaged ESXi:

This scribble may be viewed as a thing regarding not just cloning VMs without vCenter, but also as a philosophy in general. In reality, the vSphere Web Client or PowerShell commands can do all of the actions you normally conduct in your environment through GUI. Simply consider them and, if necessary, learn the appropriate instructions. Not much else to say!

Read more > Virtulization

Leave a Comment

Your email address will not be published.