6.2

Table Of Contents
Cause
There are multiple possible causes for common clone and linked clone blueprint problems.
Table 415. Causes for Common Clone and Linked Clone Blueprints Problems
Problem Cause Solution
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.
n
Verify that your fabric
administrator created a
reservation for your business
group on the compute resource
containing the templates.
n
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.
n
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.Customi
zeGuestOSDelay. The value must
be in HH:MM:SS format. If the value
is not set, the default value is one
minute (00:01:00).
Publish a Blueprint
Blueprints are saved in the draft state and must be manually published before you can configure them as
catalog items.
You need to publish a blueprint only once. Any changes you make to a published blueprint are
automatically reflected in the catalog.
IaaS Configuration for Virtual Platforms
VMware, Inc. 156