You can provision a machine by booting from an ISO image, then using a kickstart or autoYaSt configuration file and a Linux distribution image to install the operating system on the machine.

Log in to the vCloud Automation Center console as a tenant administrator or business group manager.

Gather the following information from your fabric administrator:


The name and location of the ISO image.


For vCenter Server integrations, the vCenter Server guest operating system version with which vCenter Server is to create the machine.


(Optional) For SCVMM integrations, the ISO, virtual hard disk, or hardware profile to attach to provisioned machines.


Your fabric administrator might have provided this information in a build profile.


Blueprint information settings control who can access a blueprint, how many machines they can provision with it, and how long to archive a machine after the lease period is over.


The build information settings determine how a machine is provisioned.


There are a number of custom properties that are required for Linux Kickstart provisioning.


Use blueprint actions and entitlements together to maintain detailed control over provisioned machines.

The blueprint is not available as a catalog item until you publish it. See Publish a Blueprint.