Users Guide

Virtual Machine
A Virtual Machine is configured on top of a cluster, while building a template.
After selecting Virtual Machine on the template builder page, perform the following actions:
After selecting Virtual Machine component on the Template Builder page, perform the following actions:
1. In the Virtual Machine Component dialog box, from the Select a Component drop-down list, select
one of the following:
vCenter Virtual Machine
Clone vCenter Virtual Machine
Clone Hyper-V Virtual Machine
2. In the # of Instances box, enter the number virtual machine instances that you want to configure.
3. Under Related Components, select the components that you want to map with the virtual machine
instance. For more information about valid component combinations that can be mapped together
in a template, see Component Combinations in Templates
4. Click Continue.
5. Under Virtual Machine Settings, specify the settings that you want to configure on the virtual
machines and click Add.
For more information about the virtual machine settings, see Virtual Machine Settings
Virtual Machine settings
Virtual Machine Settings (Clone vCenter Virtual Machine)
Field Name Description
vCenter Virtual Machine
Virtual Machine OS Settings
Administrator
password
Specifiy OS administrator password that is set on the installed OS.
Confirm
administrator
password
Enter the password to confirm the administrator password.
OS Image Specifies the target repository where the OS image install files are located. The
default repositories are ESXi. The additional repositories will be shown if the user
created them on the ASM appliance.
OS Image Type Refers to the operating system types (for example: Red Hat, Linux, Windows and
so on.) that are available for deployment. The image type corresponds to the
razor “installers” that are shipped with razor and assist razor in installing a
particular type of operating system. For example, you can install Red Hat 6.1, 6.2,
6.3 images and install them all with the Red Hat image type.
Custom Installation
OS script
Refers to ASM maintained kickstart scripts or unattend.xml customer specific
scripts to be used as a part of unattend OS install.
49