7.1

Silent vRealize Automation Installation Answer File
Silent vRealize Automation installations require that you prepare a text-based answer le in advance.
All newly deployed vRealize Automation appliances contain a default answer le.
/usr/lib/vcac/tools/install/ha.properties
To perform a silent installation, you must use a text editor to customize the seings in ha.properties to the
deployment that you want to install. The following examples are a few of the seings and information that
you must add.
n
Your vRealize Automation or suite license key
n
vRealize Automation appliance node FQDNs
n
vRealize Automation appliance root user account credentials
n
IaaS Windows server FQDNs that will act as Web nodes, Manager Service nodes, and so on
n
vRealize Automation service user credentials, a domain account with administrator privileges on the
IaaS Windows servers
n
Load balancer FQDNs
n
SQL Server database parameters
n
Proxy agent parameters to connect to virtualization resources
n
Whether the silent installer should aempt to correct missing IaaS Windows server prerequisites
The silent installer can correct many missing Windows prerequisites. However, some conguration
problems, such as not enough CPU, cannot be changed by the silent installer.
To save time, you can reuse and modify an ha.properties le that was congured for another deployment,
one where the seings were similar. Also, when you install vRealize Automation non-silently through the
Installation Wizard, the wizard creates and saves your seings in the ha.properties le. The le might be
useful to reuse and modify for silently installing a similar deployment.
The wizard does not save proprietary seings to the ha.properties le, such as passwords, licenses, or
certicates.
The vRealize Automation Installation Command Line
vRealize Automation includes a console-based, command line interface for performing installation
adjustments that might be required after initial installation.
The command line interface (CLI) can run installation and conguration tasks that are no longer available
through the browser-based interface after initial installation. CLI features include rechecking prerequisites,
installing IaaS components, installing certicates, or seing the vRealize Automation host name to which
users point their Web browser.
The CLI is also useful for advanced users who want to script certain operations. Some CLI functions are
used by silent installation, so familiarity with both features reinforces your knowledge of
vRealize Automation installation scripting.
Chapter 7 Silent vRealize Automation Installation
VMware, Inc. 141