To create custom virtual machine templates to use in Application Services, verify that certain software and virtualization requirements are met and that certain Linux and Windows commands are available.

Table 1. Virtual Machine Requirements for Custom Templates



Operating system

For current version requirements for your release, see the Support Matrix in vRealize Automation documentation at

  • Red Hat Enterprise Linux

  • Windows Server

  • CentOS

  • SUSE Linux Enterprise

  • Ubuntu


Install JRE 1.7.0.

Windows agent bootstrap service

Download the http://Application_Director_IP/agent/ file from the Application Services virtual appliance.

To install the agent bootstrap service on a Windows-based virtual machine template, see Prepare vCenter Server Windows Virtual Machine Templates.

vRealize Automation guest agent

For Windows templates, download the following file from the vRealize Automation Appliance management console installation page.


The file includes the vRealize Automation guest agent for Windows and Linux, but you need to download the file only for a Windows template. For a Linux template, the file is downloaded automatically.

To install the Windows and Linux guest agent in a template, see Prepare vCenter Server Windows Virtual Machine Templates and Prepare vCenter Server Linux Virtual Machine Templates.

Supported Windows scripting

Application Services supports scripting with Windows CMD, PowerShell 2.0, and BeanShell 1.3.0.

Supported Linux scripting

Application Services supports scripting with Bash and BeanShell 1.3.0.

Linux commands

The following Linux commands must be available on the virtual machine:

  • wget

  • unzip

  • sha256sum

  • grep

  • sed

  • setsid

  • awk

  • ifconfig

  • apt-get

  • yum

  • chkconfig

  • dmidecode

  • 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.


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.