Disk provisioning and folder names change when deploying a VM from template
Article ID: 319980
Updated On:
Products
Issue/Introduction
Symptoms:
Deploying VM from a downloaded template changes the disk provisioning.
During upload of the template to a datastore the name of the folder changes.
Example:
Source VM Template has "Thick Provisioning Lazy Zero".
The template is downloaded and re-uploaded on Datastore.
When deploying from the Downloaded Template on VMFS 5 Datastore, the disk changes to "Thick Provisioning Eager Zeroed".
When deploying from the Downloaded Template on VMFS 6 Datastore, the disk changes to "Thin provisioning".
Additionally, during upload of the template, the name of the folder changes.
Cause
It is not a supported workflow to download templates and re-upload them for deploying VMs.
Resolution
Workaround:
Use the OVF workflow to export and deploy the VM:
Additional Information
The template name as well as the disk provisioning changes when the template is downloaded and uploaded to the datastore and VMs are deployed from the uploaded template.
Feedback
