# VMware - VM Templates Copies

In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to VM Essentials, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be synced into VM Essentials.

If all the vCenters are added as Clouds into VM Essentials and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in VM Essentials. This means that as you deploy to the various vCenter Clouds in VM Essentials using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.

VM Essentials supports VMware Content Libraries storing VM templates and syncing into VM Essentials, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.

NOTE

VM templates are a **Datacenter** level object. The same process above applies to a single VMware cloud with multiple logical datacenters. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
