7.0

Table 2‑6. Incoming Ports for Infrastructure as a Service Components
Component Port Protocol Comments
SQL Server instance 1433 TCP MSSQL
Manager Service 443* TCP Communication with IaaS components and vRealize Automation
appliance over HTTPS
vRealize Automation appliance 443 TCP Communication with IaaS components and vRealize Automation
appliance over HTTPS
* Any virtualization hosts managed by proxy agents must also have TCP port 443 open for incoming
traffic.
Table 2‑7. Outgoing Ports for Infrastructure as a Service Components
Component Port Protocol Comments
All 53 TCP, UDP DNS
All 67, 68, 546,
547
TCP, UDP DHCP
All 123 TCP, UDP Optional. NTP.
Manager Service 443 TCP Communication with vRealize Automation appliance over
HTTPS
Website 443 TCP Communication with Manager Service over HTTPS
Distributed Execution
Managers
443 TCP Communication with Manager Service over HTTPS
Proxy agents 443 TCP Communication with Manager Service and virtualization hosts
over HTTPS
Guest agent 443 TCP Communication with Manager Service over HTTPS
Manager Service, Website 1433 TCP MSSQL
Microsoft Distributed Transaction Coordinator Service
In addition to verifying that the ports listed in the previous tables are free for use, you must enable
Microsoft Distributed Transaction Coordinator Service (MS DTC) communication between all servers in
the deployment. MS DTC requires the use of port 135 over TCP and a random port between 1024 and
65535.
The Prerequisite Checker validates whether MS DTC is running and that the required ports are open.
User Accounts and Credentials Required for Installation
You must verify that you have the roles and credentials to install vRealize Automation components.
vCenter Service Account
If you plan to use a vSphere endpoint, you need a domain or local account that has the appropriate level
of access configured in vCenter.
Installing vRealize Automation
VMware, Inc. 23