7.1

Table Of Contents
Table 429. Causes for Common Clone and Linked Clone Blueprints Problems (Continued)
Problem Cause Solution
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.CustomizeGuestOSDe
lay to increase the time delay.
Verify that you have added the
custom property
VirtualMachine.Admin.Custo
mizeGuestOSDelay. The value
must be in HH:MM:SS format. If
the value is not set, the default
value is one minute (00:01:00).
Linked clone provisioning fails
when using SDRS
When using linked clone provisioning and SDRS,
the new machine must reside on the same
cluster. A provisioning error occurs if the source
machine's disks are on one cluster and you
request to provision a machine on a dierent
cluster.
When using SDRS and linked
clone provisioning, provision
machines to the same cluster as
the linked clone source. Do not
provision to a dierent cluster.
Clone or linked clone blueprint
provisioning fails because the
template on which the clone is
based cannot be found
It is not possible to provision machines from a
blueprint that is cloned from a template that no
longer exists.
vRealize Automation runs data collection
periodically, default every 24 hours. If a template
is removed, the change is not reected until the
next data collection and so it is possible to create
a blueprint based on a non-existent template.
Redene the blueprint using an
existing template and then
request provisioning.
As a precaution and as
applicable, you can run data
collection before dening the
clone or linked clone blueprint.
Adding Network and Security Properties to a Machine Component
Non-vSphere machine components do not have a Network or Security tab. You can add network and
security options to non-vSphere machine components in the blueprint design canvas by using custom
properties.
The Network & Security components are only available for use with vSphere machine components.
For machine components that do not have a Network or Security tab, you can add network and security
custom properties, such as VirtualMachine.Network0.Name, to their Properties tab in the blueprint canvas.
NSX load balancer properties are only applicable to vSphere machines.
You can dene custom properties individually or as part of an existing property group by using the
Properties tab when conguring a machine component in the design canvas. The custom properties that you
dene for a machine component pertain to machines of that type that are provisioned from the blueprint.
For information about the available custom properties, see Custom Properties Reference.
Scenario: Create a vSphere CentOS Blueprint for Cloning in Rainpole
Using your IaaS architect privileges, you create and publish a basic blueprint for cloning vSphere CentOS
machines.
You are here
Configure
Tenant
Configure IaaS
Resources
Design On-
Demand Services
Configuring vRealize Automation
268 VMware, Inc.