All Windows servers that host IaaS components must meet certain requirements. Address requirements before you run the vRealize Automation Installation Wizard or the standard Windows-based installer.
- Place all IaaS Windows servers on the same domain. Do not use Workgroups.
- Each server needs the following minimum hardware.
- 2 CPUs
- 8 GB memory
- 40 GB disk storage
A server that hosts the SQL database together with IaaS components might need additional hardware.
- IaaS Windows servers and the SQL Server database host must be able to resolve one another by NETBIOS name. If necessary, add the NETBIOS names to the /etc/hosts file on each IaaS Windows server and the SQL Server database host, and restart the machines.
- Because of the hardware resource demand, do not deploy on VMware Workstation.
- Install Microsoft .NET Framework 3.5.
- Install Microsoft .NET Framework 4.5.2 or later.
A copy of .NET is available from any vRealize Automation appliance:
If you use Internet Explorer for the download, verify that Enhanced Security Configuration is disabled. Navigate to res://iesetup.dll/SoftAdmin.htm on the Windows server.
- Install Microsoft PowerShell 3.0 or 4.0, based on your version of Windows.
Note that some vRealize Automation upgrades or migrations might require an older or newer PowerShell version, in addition to the one that you are currently running.
- For any deployment larger than a minimal one, set IaaS Windows servers to the English locale.
- If you install more than one IaaS component on the same Windows server, plan to install them to the same installation folder. Do not use different paths.
- IaaS servers use TLS for authentication, which is enabled by default on some Windows servers.
Some sites disable TLS for security reasons, but you must leave at least one TLS protocol enabled. This version of vRealize Automation supports TLS 1.2.
- Enable the Distributed Transaction Coordinator (DTC) service. IaaS uses DTC for database transactions and actions such as workflow creation.
Note: If you clone a machine to make an IaaS Windows server, install DTC on the clone after cloning. If you clone a machine that already has DTC, its unique identifier is copied to the clone, which causes communication to fail. See Error in Manager Service Communication.
Also enable DTC on the server that hosts the SQL database, if it is separate from IaaS. For more about DTC enablement, see VMware Knowledge Base article 2038943.
- Verify that the Secondary Log On service is running. If desired, you may stop the service after installation is complete.