7.3
Table Of Contents
- Installing vRealize Automation
- Contents
- vRealize Automation Installation
- Updated Information
- 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
- Removing a vRealize Automation Appliance from a Cluster
- Licensing vRealize Code Stream
- Installing the vRealize Log Insight Agent
- Change an Appliance FQDN Back to the Original FQDN
- Configure SQL AlwaysOn Availability Group
- 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
n
The credentials used to manage the endpoint representing an SCVMM instance must have
administrator privileges on the SCVMM server.
The credentials must also have administrator privileges on the Hyper-V servers within the instance.
n
To provision machines on an SCVMM resource, the vRealize Automation user who is requesting the
catalog item must have the administrator role within the SCVMM instance.
n
Hyper-V servers within an SCVMM instance to be managed must be Windows 2008 R2 SP1 Servers
with Hyper-V installed. The processor must be equipped with the necessary virtualization
extensions .NET Framework 4.5.2 or later must be installed and Windows Management
Instrumentation (WMI) must be enabled.
n
To provision a Generation-2 machine on an SCVMM 2012 R2 resource, you must add the following
properties in the blueprint.
Scvmm.Generation2 = true
Hyperv.Network.Type = synthetic
Generation-2 blueprints should have an existing data-collected virtualHardDisk (vHDX) in the
blueprint build information page. Having it blank causes Generation-2 provisioning to fail.
For additional information about preparing your SCVMM environment, see Configuring vRealize
Automation.
Certiļ¬cates
vRealize Automation uses SSL certificates for secure communication among IaaS components and
instances of the vRealize Automation appliance. The appliances and the Windows installation machines
exchange these certificates to establish a trusted connection. You can obtain certificates from an internal
or external certificate authority, or generate self-signed certificates during the deployment process for
each component.
For important information about troubleshooting, support, and trust requirements for certificates, see
VMware Knowledge Base article 2106583.
Note vRealize Automation supports SHA2 certificates. The self-signed certificates generated by the
system use SHA-256 With RSA Encryption. You might need to update to SHA2 certificates due to
operating system or browser requirements.
You can update or replace certificates after deployment. For example, a certificate may expire or you may
choose to use self-signed certificates during your initial deployment, but then obtain certificates from a
trusted authority before going live with your vRealize Automation implementation.
Installing vRealize Automation
VMware, Inc. 33