6.2

Table Of Contents
Table 91. Virtual Machine Requirements for Custom Templates (Continued)
Requirement Description
Linux commands The following Linux commands must be available on the virtual machine:
n
wget
n
unzip
n
sha256sum
n
grep
n
sed
n
setsid
n
awk
n
ifconfig
n
apt-get
n
yum
n
chkconfig
n
dmidecode
n
perl
Optional services If you plan to remotely access the virtual machine using Linux ssh logging or Windows remote desktop for
troubleshooting or for other reasons, the OpenSSH server and client for Linux or Remote Desktop Services
(RDS) for Windows must be installed and running properly.
Important Because the boot process must not be interrupted, configure the virtual machine so that
nothing causes the virtual machine's boot process to pause before reaching the final operating system
login prompt. For example, verify that no processes or scripts prompt for user interaction when the virtual
machine starts. This requirement applies only to virtual machine templates created for the Application
Services library.
Creating Virtual Machine Templates in
vRealize Automation
To start a clone deployment in vCenter Server with a vRealize Automation blueprint, you must create a
vCenter Server virtual machine template.
A clone deployment creates a complete and independent virtual machine based on the vCenter Server
virtual machine template. A linked clone deployment references a snapshot of a virtual machine. The
deployment creates a complete and independent virtual machine based on the vCenter Server snapshot
of a virtual machine. You can set up a linked clone deployment from a clone deployment. See Iaas
Configuration for Virtual Platforms.
n
Prepare vCenter Server Windows Virtual Machine Templates
You must prepare vCenter Server Windows virtual machine templates for vRealize Automation
blueprints to create clone deployments. Application Services uses the vRealize Automation
blueprints to deploy Windows-based applications and services to the vSphere environment.
Using Application Services
VMware, Inc. 51