7.1
Table Of Contents
- Installing vRealize Automation
- Contents
- vRealize Automation Installation
- Updated Information
- Installation Overview
- Preparing for Installation
- Installing with the Installation Wizard
- Deploy the vRealize Automation Appliance
- Using the Installation Wizard for Minimal Deployments
- Run the Installation Wizard for a Minimal Deployment
- Installing the Management Agent
- Synchronize Server Times
- Run the Prerequisite Checker
- Specify Minimal Deployment Parameters
- Create Snapshots Before You Begin the Installation
- Scenario: Finish the Installation
- Address Installation Failures
- Set Up Credentials for Initial Content Configuration
- Using the Installation Wizard for Enterprise Deployments
- Run the Installation Wizard for an Enterprise Deployment
- Installing the Management Agent
- Synchronize Server Times
- Run the Prerequisite Checker
- Specify Enterprise Deployment Parameters
- Create Snapshots Before You Begin the Installation
- Finish the Installation
- Address Installation Failures
- Set Up Credentials for Initial Content Configuration
- The Standard Installation Interfaces
- Using the Standard Interfaces for Minimal Deployments
- Using the Standard Interfaces for Distributed Deployments
- Distributed Deployment Checklist
- Distributed Installation Components
- Disabling Load Balancer Health Checks
- Certificate Trust Requirements in a Distributed Deployment
- Configure Web Component, Manager Service and DEM Host Certificate Trust
- Installation Worksheets
- Deploy the vRealize Automation Appliance
- 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 Website 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
- Post-Installation Tasks
- 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
- Troubleshooting the vRealize Automation Appliance
- Troubleshooting IaaS Components
- 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
- Silent Installation
- Index
Openstack and PowerVC Requirements
The machines on which you install your DEMs must meet certain requirements to communicate with and
collect data from your Openstack or PowerVC instance.
Table 2‑4. DEM Host Requirements
Your Installation Requirements
All In Windows Registry, enable TLS v1.2 support for .NET
framework. For example:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFram
ework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Micros
oft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
Windows 2008 DEM Host In Windows Registry, enable TLS v1.2 protocol. For
example:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Co
ntrol\SecurityProviders\SCHANNEL\Protocols\TLS
1.2]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Co
ntrol\SecurityProviders\SCHANNEL\Protocols\TLS
1.2\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Co
ntrol\SecurityProviders\SCHANNEL\Protocols\TLS
1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
Self-signed certicates on your infrastructure endpoint host If your PowerVC or Openstack instance is not using trusted
certicates, import the SSL certicate from your PowerVC
or Openstack instance into the Trusted Root Certicate
Authorities store on each IaaS Windows server where you
intend to install a vRealize Automation DEM.
Red Hat Enterprise Virtualization KVM (RHEV) Requirements
When you use Red Hat Enterprise Virtualization for provisioning the IaaS Windows server communicates
with and collects data from that account.
Your environment must meet the following Red Hat Enterprise requirements.
n
Each KVM (RHEV) environment must be joined to the domain containing the IaaS server.
n
The credentials used to manage the endpoint representing a KVM (RHEV) environment must have
Administrator privileges on the RHEV environment. These credentials must also have sucient
privileges to create objects on the hosts within the environment.
SCVMM Requirements
Any DEM worker used to manage virtual machines through SCVMM must be installed on a host on which
the SCVMM console is already installed.
In addition, the following requirements must be met:
n
The DEM must have access to the SCVMM PowerShell module installed with the console.
Installing vRealize Automation
24 VMware, Inc.