7.4
Table Of Contents
- Installing vRealize Automation
- Contents
- vRealize Automation Installation
- Installation Overview
- Preparing for Installation
- Deploying the vRealize Automation Appliance
- Installing with the Installation Wizard
- The Standard Installation Interfaces
- Using the Standard Interfaces for Minimal Deployments
- Using the Standard Interfaces for Distributed Deployments
- Distributed Deployment Checklist
- Disabling Load Balancer Health Checks
- Certificate Trust Requirements in a Distributed Deployment
- Configure Web Component, Manager Service and DEM Host Certificate Trust
- Installation Worksheets
- Configuring Your Load Balancer
- Configuring Appliances for vRealize Automation
- Install the IaaS Components in a Distributed Configuration
- Install IaaS Certificates
- Download the IaaS Installer
- Choosing an IaaS Database Scenario
- Install an IaaS Website Component and Model Manager Data
- Install Additional IaaS Web Server Components
- Install the Active Manager Service
- Install a Backup Manager Service Component
- Installing Distributed Execution Managers
- Configuring Windows Service to Access the IaaS Database
- Verify IaaS Services
- Installing Agents
- Set the PowerShell Execution Policy to RemoteSigned
- Choosing the Agent Installation Scenario
- Agent Installation Location and Requirements
- Installing and Configuring the Proxy Agent for vSphere
- Installing the Proxy Agent for Hyper-V or XenServer
- Installing the VDI Agent for XenDesktop
- Installing the EPI Agent for Citrix
- Installing the EPI Agent for Visual Basic Scripting
- Installing the WMI Agent for Remote WMI Requests
- Silent Installation
- Post-Installation Tasks
- Configure FIPS Compliant Encryption
- Enable Automatic Manager Service Failover
- Automatic PostgreSQL Database Failover
- Replacing Self-Signed Certificates with Certificates Provided by an Authority
- Changing Host Names and IP Addresses
- Licensing vRealize Code Stream
- Installing the vRealize Log Insight Agent
- Change the VMware Remote Console Proxy Port
- Change an Appliance FQDN Back to the Original FQDN
- Configure SQL AlwaysOn Availability Group
- Add Network Interface Controllers After Installing vRealize Automation
- Configure Static Routes
- Access Patch Management
- Configure Access to the Default Tenant
- Troubleshooting an Installation
- Default Log Locations
- Rolling Back a Failed Installation
- Create a Support Bundle
- General Installation Troubleshooting
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Server Times Are Not Synchronized
- Blank Pages May Appear When Using Internet Explorer 9 or 10 on Windows 7
- Cannot Establish Trust Relationship for the SSL/TLS Secure Channel
- Connect to the Network Through a Proxy Server
- Console Steps for Initial Content Configuration
- Cannot Downgrade vRealize Automation Licenses
- Troubleshooting the vRealize Automation Appliance
- Installers Fail to Download
- Encryption.key File has Incorrect Permissions
- Directories Management Identity Manager Fails to Start After Horizon-Workspace Restart
- Incorrect Appliance Role Assignments After Failover
- Failures After Promotion of Replica and Master Nodes
- Incorrect Component Service Registrations
- Additional NIC Causes Management Interface Errors
- Cannot Promote a Secondary Virtual Appliance to Master
- Active Directory Sync Log Retention Time Is Too Short
- RabbitMQ Cannot Resolve Host Names
- Troubleshooting IaaS Components
- Prerequisite Fixer Cannot Install .NET Features
- Validating Server Certificates for IaaS
- Credentials Error When Running the IaaS Installer
- Save Settings Warning Appears During IaaS Installation
- Website Server and Distributed Execution Managers Fail to Install
- IaaS Authentication Fails During IaaS Web and Model Management Installation
- Failed to Install Model Manager Data and Web Components
- IaaS Windows Servers Do Not Support FIPS
- Adding an XaaS Endpoint Causes an Internal Error
- Uninstalling a Proxy Agent Fails
- Machine Requests Fail When Remote Transactions Are Disabled
- Error in Manager Service Communication
- Email Customization Behavior Has Changed
- Troubleshooting Log-In Errors
2 Install vRealize Automation, entering the appliance or load balancer name as usual. During
installation, import the customized certificate.
3 After installing, in DNS, create a CNAME alias of Common Name, and point it to the appliance or load
balancer VIP address.
4 Log in to the vRealize Automation appliance administrator interface as root.
https://vrealize-automation-appliance-FQDN:5480
5 Under vRA Settings > Host Settings, change the Host Name to the CNAME that you chose.
Licensing vRealize Code Stream
You can enable vRealize Code Stream by entering a vRealize Code Stream license in
vRealize Automation.
You can enter the vRealize Code Stream license in either of these locations:
n
On the Licensing page of the vRealize Automation installation wizard. For more information, see
vRealize Code Stream Installation.
n
On the Licensing tab in the vRealize Automation appliance management interface. For more
information, see Apply a vRealize Code Stream License to an Appliance.
Installing the vRealize Log Insight Agent on IaaS Servers
The Windows servers in a vRealize Automation IaaS configuration do not include the vRealize Log Insight
agent by default.
vRealize Log Insight provides log aggregation and indexing, and can collect, import, and analyze logs to
expose system problems. If you want to capture and analyze logs from IaaS servers by using
vRealize Log Insight, you must separately install the vRealize Log Insight agent for Windows.
For more information, see the VMware vRealize Log Insight Agent Administration Guide.
vRealize Automation appliances include the vRealize Log Insight agent by default.
Change the VMware Remote Console Proxy Port
If your site blocks or otherwise reserves port 8444, you can change the default proxy port used by
VMware Remote Console.
Procedure
1 Access the vRealize Automation appliance command prompt as root.
2 Open the following file in a text editor.
/etc/vcac/security.properties
3 Change consoleproxy.service.port from its default of 8444 to an unused port.
4 Save and close security.properties.
Installing vRealize Automation
VMware, Inc. 142