7.2

n
In general, you should expect to keep the host names and FQDNs that you planned for
vRealize Automation systems. You can change a vRealize Automation appliance host name after
installation, but changing other vRealize Automation host names makes vRealize Automation
unusable.
n
A best practice is to reserve and use static IP addresses for all vRealize Automation appliances and IaaS
Windows servers. vRealize Automation supports DHCP, but static IP addresses are recommended for
long-term deployments such as production environments.
n
You apply an IP address to the vRealize Automation appliance during OVF or OVA deployment.
n
For the IaaS Windows servers, you follow the usual operating system process. Set the IP address
before installing vRealize Automation IaaS.
Hardware and Virtual Machine Requirements
Your deployment must meet minimum system resources to install virtual appliances and minimum
hardware requirements to install IaaS components on the Windows Server.
For operating system and high-level environment requirements, including information about supported
browsers and operating systems, see the vRealize Automation Support Matrix.
The Hardware Requirements table shows the minimum conguration requirements for deployment of
virtual appliances and installation of IaaS components. Appliances are pre-congured virtual machines that
you add to your vCenter Server or ESXi inventory. IaaS components are installed on physical or virtual
Windows 2008 R2 SP1, or Windows 2012 R2 servers.
An Active Directory is considered small when there are up to 25,000 users in the OU to be synced in the ID
Store conguration. An Active Directory is considered large when there are more than 25,000 users in the
OU.
Table 2‑1. Hardware Requirements
vRealize Automation appliance
for Small Active Directories
vRealize Automation appliance for Large
Active Directories
IaaS Components (Windows
Server).
n
4 CPUs
n
18 GB memory
n
60 GB disk storage
n
4 CPUs
n
22 GB memory
n
60 GB disk storage
n
2 CPUs
n
8 GB memory
n
30 GB disk storage
Additional resources are
required when you are include
an SQL Server on a Windows
host.
Browser Considerations
Some restrictions exist for browser use with vRealize Automation.
n
Multiple browser windows and tabs are not supported. vRealize Automation supports one session per
user.
n
VMware Remote Consoles provisioned on vSphere support a subset of vRealize Automation-supported
browsers.
For operating system and high-level environment requirements, including information about supported
browsers and operating systems, see the vRealize Automation Support Matrix.
Installing vRealize Automation
20 VMware, Inc.