When creating a linked clone or clone blueprint, machine or templates are missing. Using your shared clone blueprint to request machines fails to provision machines.


When working with clone or linked clone blueprints, you might encounter one of the following problems:

  • When you create a linked clone blueprint, no machines appear in the list to clone, or the machine you want to clone does not appear.

  • When you create a clone blueprint for a business group, no templates appear in the list of templates to clone, or the template you want does not appear.

  • When machines are requested by using your shared clone blueprint, provisioning fails.


There are multiple possible causes for common clone and linked clone blueprint problems.

Table 1. Causes for Common Clone and Linked Clone Blueprints Problems




Machines missing

You can only create linked clone blueprints by using machines you manage as a tenant administrator or business group manager.

A user in your tenant or business group must request a vSphere machine. If you have the appropriate roles, you can do this yourself.

Templates missing

If you are creating a clone blueprint for a business group, then you only see templates that exist on compute resources on which the business group has a reservation.

  • Verify that your fabric administrator created a reservation for your business group on the compute resource containing the templates.

  • If your endpoints are clustered and contain multiple compute resources, verify that your IaaS administrator added the cluster containing the templates to your fabric group.

  • For new templates, verify that IT placed the templates on the cluster included in your fabric group.

Provisioning failure with a shared blueprint

For shared blueprints, no validation is available to ensure that the template you select exists in the reservation used to provision a machine from your shared clone blueprint.

Consider using entitlements to restrict the blueprint to users who have a reservation on the compute resource where the template exists. For more information about entitlements, see Tenant Administration.

Provisioning failure with a guest agent

The virtual machine might be rebooting immediately after the guest operating system customization is completed, but before the guest agent work items are completed, causing provisioning to fail. You can use the custom property VirtualMachine.Admin.CustomizeGuestOSDelay to increase the time delay.

Verify that you have added the custom property VirtualMachine.Admin.CustomizeGuestOSDelay. The value must be in HH:MM:SS format. If the value is not set, the default value is one minute (00:01:00).