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
4 If manualFailoverNeeded is true, perform a manual failover.
For information about performing a manual failover, see Managing vRealize Automation.
Replacing Self-Signed Certificates with Certificates
Provided by an Authority
If you installed vRealize Automation with self-signed certificates, you might want to replace them with
certificates provided by a certificate authority before deploying to production.
For more information about updating certificates, see Managing vRealize Automation.
Changing Host Names and IP Addresses
In general, you should expect to keep the host names, FQDNs, and IP addresses that you planned for
vRealize Automation systems. Some post-installation changes are possible but can be complicated.
n
If you change the host name of the Windows machine that hosts the IaaS SQL Server database, see
Managing vRealize Automation.
n
When restoring IaaS components, renaming a host can affect the IaaS Web host, Manager Service
host, or their respective load balancers. For more information, see Managing vRealize Automation.
To change a vRealize Automation appliance host name or IP address, see the following sections.
Change the vRealize Automation Appliance Host Name
When maintaining an environment or network, you might need to assign a different host name to a
vRealize Automation appliance.
Important Renaming takes vRealize Automation offline for several minutes.
The same steps apply for standalone, master, and replica vRealize Automation appliances.
Procedure
1 In DNS, create an additional record with the new node host name.
Do not remove the existing DNS record with the old host name yet.
2 Wait for DNS replication and zone distribution to occur.
3 Log in as root to the vRealize Automation appliance command line.
4 Run the following command.
vcac-config hostname-change --host new-hostname --certificate certificate-file-
name
A certificate file is optional unless the old appliance host name was used in a certificate. If so, supply
an updated certificate that has the new host name.
Installing vRealize Automation
VMware, Inc. 135