Installing vRealize Automation vRealize Automation 7.2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
Installing vRealize Automation You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents vRealize Automation Installation 7 Updated Information 9 1 vRealize Automation Installation Overview 11 vRealize Automation Installation Components 11 The vRealize Automation Appliance 12 Infrastructure as a Service 12 Deployment Type 14 Minimal vRealize Automation Deployments 15 Distributed vRealize Automation Deployments 16 Choosing Your Installation Method 17 2 Preparing for vRealize Automation Installation 19 Host Names and IP Addresses 19 Hardware and Virtual Machine Requirements 20 Brows
Installing vRealize Automation Address Installation Failures 40 Set Up Credentials for Initial Content Configuration 40 Using the Installation Wizard for Enterprise Deployments 41 Run the Installation Wizard for an Enterprise Deployment 41 Installing the Management Agent 42 Synchronize Server Times 44 Run the Prerequisite Checker 45 Specify Enterprise Deployment Parameters 46 Create Snapshots Before You Begin the Installation 46 Finish the Installation 46 Address Installation Failures 47 Set Up Credentials
Contents 6 Troubleshooting a vRealize Automation Installation 127 Default Log Locations 127 Rolling Back a Failed Installation 128 Roll Back a Minimal Installation 128 Roll Back a Distributed Installation 129 Create a vRealize Automation Support Bundle 130 General Installation Troubleshooting 130 Installation or Upgrade Fails with a Load Balancer Timeout Error 130 Server Times Are Not Synchronized 131 Blank Pages May Appear When Using Internet Explorer 9 or 10 on Windows 7 131 Cannot Establish Trust Relat
Installing vRealize Automation Index 6 153 VMware, Inc.
vRealize Automation Installation vRealize Automation Installation explains how to install VMware vRealize ™ Automation. Note Not all features and capabilities of vRealize Automation are available in all editions. For a comparison of feature sets in each edition, see https://www.vmware.com/products/vrealize-automation/. Intended Audience This information is intended for experienced Windows or Linux system administrators who are familiar with virtual machine technology and data center operations.
Installing vRealize Automation 8 VMware, Inc.
Updated Information The following table lists the changes to Installing vRealize Automation for this product release. Revision Description EN-002325-02 n n Added another restart in “Change the Master vRealize Automation Appliance Host Name,” on page 122 and “Change a Replica vRealize Automation Appliance Host Name,” on page 123. Added “Cannot Downgrade vRealize Automation Licenses,” on page 134. EN-002325-01 Added Configure a Datastore Cluster permission to “vSphere Agent Requirements,” on page 99.
Installing vRealize Automation 10 VMware, Inc.
vRealize Automation Installation Overview 1 You can install vRealize Automation through different means, each with varying levels of interactivity.
Installing vRealize Automation The vRealize Automation Appliance The vRealize Automation appliance is a preconfigured Linux virtual appliance. The vRealize Automation appliance is delivered as an open virtualization file that you deploy on existing virtualized infrastructure such as vSphere. The vRealize Automation appliance performs several functions central to vRealize Automation.
Chapter 1 vRealize Automation Installation Overview Manager Service The Manager Service is a Windows service that coordinates communication between IaaS DEMs, the SQL Server database, agents, and SMTP. IaaS requires that only one Windows machine actively run the Manager Service. For backup or high availability, you may deploy additional Windows machines where you manually start the Manager Service if the active service stops.
Installing vRealize Automation Virtualization Proxy Agents vRealize Automation creates and manages virtual machines on virtualization hosts. Virtualization proxy agents send commands to, and collect data from, vSphere ESX Server, XenServer, and Hyper-V hosts, and the virtual machines provisioned on them. A virtualization proxy agent has the following characteristics. n Typically requires administrator privileges on the virtualization platform that it manages.
Chapter 1 vRealize Automation Installation Overview Minimal vRealize Automation Deployments Minimal deployments include one vRealize Automation appliance and one Windows server that hosts the IaaS components. In a minimal deployment, the vRealize Automation SQL Server database can be on the same IaaS Windows server with the IaaS components, or on a separate Windows server. Figure 1‑1.
Installing vRealize Automation Distributed vRealize Automation Deployments Distributed, enterprise deployments can be of varying size. A basic distributed deployment might improve vRealize Automation simply by hosting IaaS components on separate Windows servers as shown in the following figure. Figure 1‑2. Distributed vRealize Automation Deployment Many production deployments go even further, with redundant appliances, redundant servers, and load balancing for even more capacity.
Chapter 1 vRealize Automation Installation Overview Figure 1‑3. Large Distributed and Load Balanced vRealize Automation Deployment For more information about scalability and high availability, see the vRealize Automation Reference Architecture guide. Choosing Your Installation Method The consolidated vRealize Automation Installation Wizard is your primary tool for new vRealize Automation installations. Alternatively, you might want to perform the manual, separate installation processes in some cases.
Installing vRealize Automation n You need the manual installation steps if you want to expand a vRealize Automation deployment or if the Installation Wizard stopped for any reason. Once you begin a manual installation, you cannot go back and run the Installation Wizard. 18 VMware, Inc.
Preparing for vRealize Automation Installation 2 System Administrators install vRealize Automation into their existing virtualization environments. Before you begin an installation, prepare the deployment environment to meet system requirements.
Installing vRealize Automation n In general, you should expect to keep the host names and FQDNs that you planned for vRealize Automation systems. You can change a vRealize Automation appliance host name after installation, but changing other vRealize Automation host names makes vRealize Automation unusable. n A best practice is to reserve and use static IP addresses for all vRealize Automation appliances and IaaS Windows servers.
Chapter 2 Preparing for vRealize Automation Installation Password Considerations Character restrictions apply to some passwords. The VMware vRealize ™ Automation administrator password cannot contain a trailing "=" character. Such passwords are accepted when you assign them, but result in errors when you perform operations such as saving endpoints.
Installing vRealize Automation IaaS Web Service and Model Manager Server Requirements Your environment must meet software and configuration prerequisites that support installation of the IaaS server components. Environment and Database Requirements for IaaS Your host configuration and MS SQL database must meet the following requirements. Table 2‑2. IaaS Requirements Area Requirements Host Configuration The following components must be installed on the host before installing IaaS: n Microsoft .
Chapter 2 Preparing for vRealize Automation Installation Table 2‑3. Required Configuration for Microsoft Internet Information Services IIS Component Setting Internet Information Services (IIS) modules installed n n n n n n IIS Authentication settings n n n n n n n IIS Windows Process Activation Service roles n n n n n n WindowsAuthentication StaticContent DefaultDocument ASPNET 4.
Installing vRealize Automation n No firewalls between DEM host and the Windows server, or ports opened as described in “vRealize Automation Port Requirements,” on page 26. Servers that host DEM Worker instances might have additional requirements depending on the provisioning resources that they interact with. Amazon Web Services EC2 Requirements A vRealize Automation IaaS Windows server communicates with and collects data from an Amazon EC2 account.
Chapter 2 Preparing for vRealize Automation Installation 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.
Installing vRealize Automation n The PowerShell Execution Policy must be set to RemoteSigned or Unrestricted. To verify the PowerShell Execution Policy, enter one of the following commands at the PowerShell command prompt. help about_signing help Set-ExecutionPolicy n If all DEM Workers within the instance are not on machines that meet these requirements, use Skill commands to direct SCVMM-related workflows to DEM Workers that are. The following additional requirements apply to SCVMM.
Chapter 2 Preparing for vRealize Automation Installation vRealize Automation Appliance The following ports are used by the vRealize Automation appliance. Table 2‑5. Incoming Ports for the vRealize Automation appliance Port Protocol Comments 22 TCP Optional. Access for SSH sessions 80 TCP Optional.
Installing vRealize Automation Table 2‑7. Incoming Ports for Infrastructure as a Service Components Component Port Protocol Comments 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 Infrastructure Endpoint Hosts 443 TCP Communication with IaaS components and vRealize Automation appliance over HTTPS.
Chapter 2 Preparing for vRealize Automation Installation Virtual Appliance Installation To deploy the vRealize Automation appliance, you must have the appropriate privileges on the deployment platform (for example, vSphere administrator credentials). During the deployment process, you specify the password for the virtual appliance administrator account. This account provides access to the vRealize Automation appliance management console from which you configure and administer the virtual appliances.
Installing vRealize Automation Model Manager Server Specifications Specify the Model Manager server name by using a fully qualified domain name (FQDN). Do not use an IP address to specify the server. Security vRealize Automation uses SSL to ensure secure communication among components. Passphrases are used for secure database storage. For more information see “Certificate Trust Requirements in a Distributed Deployment,” on page 63.
Chapter 2 Preparing for vRealize Automation Installation Table 2‑10. Sample Certificate Values and Commands (openssl) Certificate Authority Provides Command Virtual Appliance Entries RSA Private Key openssl pkcs12 -in path _to_.pfx certificate_file -nocerts -out key.pem RSA Private Key PEM File openssl pkcs12 -in path _to_.pfx certificate_file -clcerts -nokeys -out cert.
Installing vRealize Automation 32 VMware, Inc.
Installing vRealize Automation with the Installation Wizard 3 The vRealize Automation Installation Wizard provides a simple and fast way to install minimal or enterprise deployments. Before you launch the wizard, you deploy a vRealize Automation appliance and configure IaaS Windows servers to meet prerequisites. The Installation Wizard appears the first time you log in to the newly deployed vRealize Automation appliance. n To stop the wizard and return later, click Logout.
Installing vRealize Automation 6 Enter a unique virtual appliance name according to the IT naming convention of your organization in the Name text box, select the datacenter and location to which you want to deploy the virtual appliance, and click Next. 7 Follow the prompts until the Disk Format page appears. 8 Verify on the Disk Format page that enough space exists to deploy the virtual appliance and click Next. 9 Follow the prompts to the Properties page.
Chapter 3 Installing vRealize Automation with the Installation Wizard 13 e Power on the vRealize Automation appliance. f Wait for the machine to start, which might take up to 5 minutes. Open a command prompt and ping the FQDN to verify that the fully qualified domain name can be resolved against the IP address of vRealize Automation appliance.
Installing vRealize Automation Procedure 1 Find the SSL Certificate Fingerprint for the Management Site Service on page 36 When you install a management agent, you must validate the fingerprint of the SSL certificate for the Management Site service. 2 Download and Install the Management Agent on page 36 You install the Management Agent on the IaaS Windows server in your deployment.
Chapter 3 Installing vRealize Automation with the Installation Wizard 6 Accept the EULA and click Next. 7 Confirm or change the installation folder, and click Next. The default folder is %Program Files(x86)%\VMware\vCAC\Management Agent. 8 9 Enter Management Site Service details. Text box Input vRA appliance address https://vrealize-automation-appliance-FQDN:5480 You must include the port number. Root username The root user name for the vRealize Automation appliance.
Installing vRealize Automation After you install the Management Agent, the IaaS Windows server appears on the Installation Prerequisites page of the Installation Wizard. Synchronize Server Times Clocks on vRealize Automation servers and Windows servers must be synchronized to ensure a successful installation. Options on the Prerequisites page of the Installation Wizard let you select a time synchronization method for your virtual appliances. The IaaS host table informs you of time offsets.
Chapter 3 Installing vRealize Automation with the Installation Wizard Specify Minimal Deployment Parameters Use the vRealize Automation Installation Wizard to enter configuration settings for the minimal deployment components. Procedure u Follow the Installation Wizard pages to enter vRealize Automation appliance and IaaS Windows server FQDNs, account credentials, default tenant password, and other settings.
Installing vRealize Automation 4 Accept or change the default telemetry settings and click Next. 5 Click Next. 6 Click Finish. The installation starts. Depending on your network, installation might take up to an hour to finish. What to do next Set up vRealize Automation for initial content creation. Address Installation Failures When you install from the Installation Details page, you are informed of any issues that are preventing the installation from finishing.
Chapter 3 Installing vRealize Automation with the Installation Wizard Procedure 1 Create and enter a password for the configurationadmin account in the Password text box. 2 Reenter the password in the Confirm password text box. Make a note of the password for later use. 3 Click Create Initial Content. 4 Click Next. A configuration admin user is created and a configuration catalog item is created in the default tenant.
Installing vRealize Automation Procedure 1 Open a Web browser to the vRealize Automation appliance management interface URL. https://vrealize-automation-appliance-FQDN:5480 2 Log in with the user name root and the password you specified when the appliance was deployed. 3 When the Installation Wizard appears, click Next. 4 Accept the End User License Agreement and click Next. 5 On the Deployment Type page, select Enterprise deployment and Install Infrastructure as a Service.
Chapter 3 Installing vRealize Automation with the Installation Wizard Prerequisites n Note the vRealize Automation appliance certificate fingerprint by following the steps in “Find the SSL Certificate Fingerprint for the Management Site Service,” on page 36. n Note the user name and password of a domain account with administrator privileges on the IaaS Windows server. The Management Agent service must run under this account.
Installing vRealize Automation 9 Text box Input Management Site server certificate The SHA1 fingerprint for the Management Site Service certificate. The Management Site Service is hosted on the vRealize Automation appliance. Sample SHA1 fingerprint: DFF5FA0886DA2920D227ADF8BC9CDE4EF13EEF78 Load Click Load to load the default fingerprint. Verify that the fingerprint matches the one from the vRealize Automation appliance certificate, and select the confirmation checkbox.
Chapter 3 Installing vRealize Automation with the Installation Wizard Procedure 1 Select an option from the Time Sync Mode menu. Option Action Use Time Server Select Use Time Server from the Time Sync Mode menu to use Network Time Protocol . For each time server that you are using, enter the IP address or the host name in the Time Server text box. Use Host Time Select Use Host Time from the Time Sync Mode menu to use VMware Tools time synchronization.
Installing vRealize Automation Specify Enterprise Deployment Parameters Use the vRealize Automation Installation Wizard to enter configuration settings for the enterprise deployment components. Prerequisites Procedure u Follow the Installation Wizard pages to enter vRealize Automation appliance and IaaS Windows server FQDNs, account credentials, default tenant password, and other settings.
Chapter 3 Installing vRealize Automation with the Installation Wizard 3 Click Next. 4 Click Finish. The installation starts. Depending on your network configuration, installation can take between fifteen minutes and one hour. A confirmation message appears when the installation finishes. What to do next You are now ready to configure your deployment.
Installing vRealize Automation Set Up Credentials for Initial Content Configuration Optionally, you can start an initial content workflow for a vSphere endpoint. The process uses a local user called configurationadmin that is granted administrator rights. Procedure 1 Create and enter a password for the configurationadmin account in the Password text box. 2 Reenter the password in the Confirm password text box. Make a note of the password for later use. 3 Click Create Initial Content. 4 Click Next.
The Standard vRealize Automation Installation Interfaces 4 After running the Installation Wizard, you might need or want to perform certain installation tasks manually, through the standard interfaces. The Installation Wizard described in Chapter 3, “Installing vRealize Automation with the Installation Wizard,” on page 33 is your primary tool for new vRealize Automation installations. However, after you run the wizard, some operations still require the older, manual installation process.
Installing vRealize Automation Print out a copy of the checklist and use it to track your work as you complete the installation. Complete the tasks in the order in which they are given. Table 4‑1. Minimal Deployment Checklist Task Details Plan and prepare the installation environment and verify that all installation prerequisites are met.
Chapter 4 The Standard vRealize Automation Installation Interfaces 6 Enter a unique virtual appliance name according to the IT naming convention of your organization in the Name text box, select the datacenter and location to which you want to deploy the virtual appliance, and click Next. 7 Follow the prompts until the Disk Format page appears. 8 Verify on the Disk Format page that enough space exists to deploy the virtual appliance and click Next. 9 Follow the prompts to the Properties page.
Installing vRealize Automation 13 e Power on the vRealize Automation appliance. f Wait for the machine to start, which might take up to 5 minutes. Open a command prompt and ping the FQDN to verify that the fully qualified domain name can be resolved against the IP address of vRealize Automation appliance. Enable Time Synchronization on the vRealize Automation Appliance Clocks on the vRealize Automation server and Windows servers must be synchronized to ensure a successful installation.
Chapter 4 The Standard vRealize Automation Installation Interfaces 2 Continue past the certificate warning. 3 Log in with the user name root and the password you specified when the appliance was deployed. 4 Select vRA Settings > Host Settings. Option Action Resolve Automatically Select Resolve Automatically to specify the name of the current host for the vRealize Automation appliance. Update Host For new hosts, select Update Host.
Installing vRealize Automation 5 Select the certificate type from the Certificate Action menu. If you are using a PEM-encoded certificate, for example for a distributed environment, select Import. Certificates that you import must be trusted and must also be applicable to all instances of vRealize Automation appliance and any load balancer through the use of Subject Alternative Name (SAN) certificates.
Chapter 4 The Standard vRealize Automation Installation Interfaces 10 Click Services and verify that services are registered. Depending on your site configuration, this can take about 10 minutes. Note You can log in to the appliance and run tail -f /var/log/vcac/catalina.out to monitor startup of the services. 11 Enter your license information. a Click vRA Settings > Licensing. b Click Licensing.
Installing vRealize Automation 2 Type the following command to navigate to the VMware Tools directory. cd C:\Program Files\VMware\VMware Tools 3 Type the command to display the timesync status. VMwareToolboxCmd.exe timesync status 4 If timesync is disabled, type the following command to enable it. VMwareToolboxCmd.exe timesync enable IaaS Certificates vRealize Automation IaaS components use certificates and SSL to secure communications between components.
Chapter 4 The Standard vRealize Automation Installation Interfaces Download the vRealize Automation IaaS Installer To install IaaS on your minimal virtual or physical Windows server, you download a copy of the IaaS installer from the vRealize Automation appliance. If you see certificate warnings during this process, continue past them to finish the installation. Prerequisites n Microsoft .NET Framework 4.5.2 or later. You can download the .NET installer from the same Web page as the IaaS installer.
Installing vRealize Automation 7 Select Complete Install on the Installation Type page if you are creating a minimal deployment and click Next. Check Prerequisites The Prerequisite Checker verifies that your machine meets IaaS installation requirements. Prerequisites “Select the Installation Type,” on page 57. Procedure 1 2 Complete the Prerequisite Check. Option Description No errors Click Next. Noncritical errors Click Bypass.
Chapter 4 The Standard vRealize Automation Installation Interfaces 5 Select the authentication method. u Select Use Windows authentication if you want to create the database using the Windows credentials of the current user. The user must have SQL sys_admin privileges. u Deselect Use Windows authentication if you want to create the database using SQL authentication. Type the User name and Password of the SQL Server user with SQL sys_admin privileges on the SQL server instance.
Installing vRealize Automation 3 Click Download to retrieve the certificate from the vRealize Automation appliance. You can click View Certificate to view the certificate details. 4 Select Accept Certificate to install the SSO certificate. 5 In the SSO Administrator panel, type administrator in the User name text box and the password you defined for this user when you configured SSO in Password and Confirm password.
Chapter 4 The Standard vRealize Automation Installation Interfaces Table 4‑2. Distributed Deployment Checklist Task Details Plan and prepare the installation environment and verify that all installation prerequisites are met. Chapter 2, “Preparing for vRealize Automation Installation,” on page 19 Plan for and obtain your SSL certificates.
Installing vRealize Automation Table 4‑3. Virtual Appliances and Appliance Database Component Description vRealize Automation appliance A preconfigured virtual appliance that deploys the vRealize Automation server. The server includes the vRealize Automation console, which provides a single portal for self-service provisioning and management of cloud services, as well as authoring and administration. Appliance Database Stores information required by the virtual appliances.
Chapter 4 The Standard vRealize Automation Installation Interfaces Certificate Trust Requirements in a Distributed Deployment For secure communication, vRealize Automation relies on certificates to create trusted relationships among components. The specific implementation of the certificates required to achieve this trust depends on your environment. To provide high availability and failover support, you might deploy load-balanced clusters of components.
Installing vRealize Automation 3 Open a Microsoft Management Console window on each of the applicable host machines. Note Actual paths and options in the Management Console may differ somewhat based on Windows versions and system configurations. a Select Add/Remove Snap-in. b Select Certificates. c Select Local Computer. d Open the certificate files that you imported previously and copy the thumb prints.
Chapter 4 The Standard vRealize Automation Installation Interfaces Table 4‑7. IaaS Windows Servers Variable My Value Example Primary IaaS Web Server with Model Manager Data FQDN web.mycompany.com Primary IaaS Web Server with Model Manager Data IP address For reference only; do not enter IP addresses 123.234.1.107 Additional IaaS Web Server FQDN web2.mycompany.com Additional IaaS Web Server IP address For reference only; do not enter IP addresses 123.234.1.
Installing vRealize Automation Table 4‑9. IaaS Distributed Execution Managers Variable My Value Example DEM host FQDN dem.mycompany.com DEM host IP address For reference only; do not enter IP addresses 123.234.1.111 DEM host FQDN dem2.mycompany.com DEM host IP address For reference only; do not enter IP addresses 123.234.1.
Chapter 4 The Standard vRealize Automation Installation Interfaces 10 Configure the values on the Properties page. a Enter the root password to use when you log in to the virtual appliance console in the Enter password and Confirm password text boxes. b Select or uncheck the SSH service checkbox to choose whether SSH service is enabled for the appliance. This value is used to set the initial status of the SSH service in the appliance.
Installing vRealize Automation Configuring Your Load Balancer After you deploy the appliances for vRealize Automation, you can set up a load balancer to distribute traffic among multiple instances of the vRealize Automation appliance. The following list provides an overview of the general steps required to configure a load balancer for vRealize Automation traffic: 1 Install your load balancer. 2 Enable session affinity, also known as sticky sessions.
Chapter 4 The Standard vRealize Automation Installation Interfaces Enable Time Synchronization on the vRealize Automation appliance Clocks on the vRealize Automation appliance server and Windows servers must be synchronized to ensure a successful installation. If you see certificate warnings during this process, continue past them to finish the installation. Procedure 1 Open a Web browser to the vRealize Automation appliance management interface URL.
Installing vRealize Automation 5 Select the certificate type from the Certificate Action menu. If you are using a PEM-encoded certificate, for example for a distributed environment, select Import. Certificates that you import must be trusted and must also be applicable to all instances of vRealize Automation appliance and any load balancer through the use of Subject Alternative Name (SAN) certificates.
Chapter 4 The Standard vRealize Automation Installation Interfaces e Select the Administrator SSH login check box. Deselect the check box to disable SSH when finished. f Click Save Settings. 8 Configure the SSO settings. 9 Click Services. All services must be running before you can install a license or log in to the console. They usually start in about 10 minutes. Note You can also log in to the appliance and run tail -f /var/log/vcac/catalina.out to monitor service startup.
Installing vRealize Automation Configuring Additional Instances of the vRealize Automation Appliance The system administrator can deploy multiple instances of the vRealize Automation appliance to ensure redundancy in a high-availability environment. For each vRealize Automation appliance, you must enable time synchronization and add the appliance to a cluster.
Chapter 4 The Standard vRealize Automation Installation Interfaces Prerequisites n You must have one or more vRealize Automation appliance nodes already in the cluster, where one node is the primary node. See “Configure the Primary vRealize Automation Appliance,” on page 68. You can set a new node to be the primary node only after joining the new node to the cluster. n Verify that the load balancer is configured for use with the new vRealize Automation appliance.
Installing vRealize Automation Validate the Distributed Deployment After deploying additional instances of the vRealize Automation appliance, you validate that you can access the clustered appliances. Procedure 1 In the load balancer management interface or configuration file, temporarily disable all nodes except the node that you are testing.
Chapter 4 The Standard vRealize Automation Installation Interfaces 5 Install Additional IaaS Web Server Components on page 85 The Web server provides access to infrastructure capabilities in vRealize Automation. After the first Web server is installed, you might increase performance by installing additional IaaS Web servers.
Installing vRealize Automation 7 Verify that the certificate and its chain is trusted. If the certificate is untrusted, you see the message, This CA root certificate is not trusted. Note You must resolve the trust issue before proceeding with the installation. If you continue, your deployment fails. 8 Restart IIS or open an elevated command prompt window and type iisreset. What to do next “Download the vRealize Automation IaaS Installer,” on page 76.
Chapter 4 The Standard vRealize Automation Installation Interfaces Choosing an IaaS Database Scenario vRealize Automation IaaS uses a Microsoft SQL Server database to maintain information about the machines it manages and its own elements and policies. Depending on your preferences and privileges, there are several procedures to choose from to create the IaaS database. Note You can enable secure SSL when creating or upgrading the SQL database.
Installing vRealize Automation 4 Review the database deployment scripts as needed. In particular, review the settings in the DBSettings section of CreateDatabase.sql and edit them if necessary. The settings in the script are the recommended settings. Only ALLOW_SNAPSHOT_ISOLATION ON and READ_COMMITTED_SNAPSHOT ON are required. 5 Execute the following command with the arguments described in the table. BuildDB.
Chapter 4 The Standard vRealize Automation Installation Interfaces 3 Log in to the Windows database host with sysadmin privileges within the SQL Server instance. 4 Edit CreateDatabase.sql and replace all instances of the variables in the table with the correct values for your environment. Table 4‑12. Database Values 5 Variable Value $(DBName) Name of the database, such as vra. Database names must consist of no more than 128 ASCII characters.
Installing vRealize Automation 4 On the Log in page, supply administrator credentials for the vRealize Automation appliance and verify the SSL Certificate. a Type the user name, which is root, and the password. The password is the password that you specified when you deployed the vRealize Automation appliance. b Select Accept Certificate. c Click View Certificate. Compare the certificate thumbprint with the thumbprint set for the vRealize Automation appliance.
Chapter 4 The Standard vRealize Automation Installation Interfaces 16 Click Next. 17 Complete the Prerequisite Check. Option Description No errors Click Next. Noncritical errors Click Bypass. Critical errors Bypassing critical errors causes the installation to fail. If warnings appear, select the warning in the left pane and follow the instructions on the right. Address all critical errors and click Check Again to verify. 18 Click Install.
Installing vRealize Automation n If you previously installed other components in this environment, verify that you know the passphrase that was created. See “Security Passphrase,” on page 31. n If you are using load balancers in your environment, verify that they meet the configuration requirements. Procedure 1 If using a load balancer, disable the other nodes under the load balancer, and verify that traffic is directed to the node that you want.
Chapter 4 The Standard vRealize Automation Installation Interfaces 15 Select the certificate for this component. a If you imported a certificate after you began the installation, click Refresh to update the list. b Select the certificate to use from Available certificates. c If you imported a certificate that does not have a friendly name and it does not appear in the list, deselect Display certificates using friendly names and click Refresh.
Installing vRealize Automation 9 In the IaaS Server text box, identify the IaaS Web server component. Option Description With a load balancer Enter the fully qualified domain name and port number of the load balancer for the IaaS Web server component, web-loadbalancer.mycompany.com:443. Do not enter IP addresses. Without a load balancer Enter the fully qualified domain name and port number of the machine where you installed the IaaS Web server component, web.mycompany.com: 443.
Chapter 4 The Standard vRealize Automation Installation Interfaces Install Additional IaaS Web Server Components The Web server provides access to infrastructure capabilities in vRealize Automation. After the first Web server is installed, you might increase performance by installing additional IaaS Web servers. Do not install Model Manager Data with an additional Web server component. Only the first Web server component hosts Model Manager Data.
Installing vRealize Automation 11 Select Website on the IaaS Server Custom Install page. 12 Select a Web site from available Web sites or accept the default Web site on the Administration & Model Manager Web Site tab. 13 Type an available port number in the Port number text box, or accept the default port 443. 14 Click Test Binding to confirm that the port number is available for use. 15 Select the certificate for this component.
Chapter 4 The Standard vRealize Automation Installation Interfaces 23 Provide the passphrase used to generate the encryption key that protects the database. Option Description If you have already installed components in this environment Type the passphrase you created previously in the Passphrase and Confirm text boxes. If this is the first installation Type a passphrase in the Passphrase and Confirm text boxes. You must use this passphrase every time you install a new component.
Installing vRealize Automation 2 Right-click the setup__vrealize-automation-appliance-FQDN@5480.exe setup file and select Run as administrator. 3 Accept the license agreement and click Next. 4 On the Log in page, supply administrator credentials for the vRealize Automation appliance and verify the SSL Certificate. a Type the user name, which is root, and the password. The password is the password that you specified when you deployed the vRealize Automation appliance. b Select Accept Certificate.
Chapter 4 The Standard vRealize Automation Installation Interfaces 16 Select the certificate for this component. a If you imported a certificate after you began the installation, click Refresh to update the list. b Select the certificate to use from Available certificates. c If you imported a certificate that does not have a friendly name and it does not appear in the list, deselect Display certificates using friendly names and click Refresh.
Installing vRealize Automation Install a Backup Manager Service Component The backup Manager Service provides redundancy and high availability, and may be started manually if the active service stops. Your IaaS deployment requires that only one Windows machine actively run the Manager Service. Machines that provide the backup Manager Service must have the service stopped and configured to start manually.
Chapter 4 The Standard vRealize Automation Installation Interfaces 9 Accept the root install location or click Change and select an installation path. Even in a distributed deployment, you might sometimes install more than one IaaS component on the same Windows server. If you install more than one IaaS component, always install them to the same path. 10 Click Next. 11 Select Manager Service on the IaaS Server Custom Install page.
Installing vRealize Automation 22 Provide the passphrase used to generate the encryption key that protects the database. Option Description If you have already installed components in this environment Type the passphrase you created previously in the Passphrase and Confirm text boxes. If this is the first installation Type a passphrase in the Passphrase and Confirm text boxes. You must use this passphrase every time you install a new component. Keep this passphrase in a secure place for later use.
Chapter 4 The Standard vRealize Automation Installation Interfaces Install the Distributed Execution Managers You must install at least one DEM Worker and one DEM Orchestrator. The installation procedure is the same for both roles. DEM Orchestrators support active-active high availability. Typically, you install a single DEM Orchestrator on each Manager Service machine. You can install DEM Orchestrators and DEM workers on the same machine.
Installing vRealize Automation 13 14 Select the installation type from the DEM role drop-down menu. Option Description Worker The Worker executes workflows. Orchestrator The Orchestrator oversees DEM worker activities, including scheduling and preprocessing workflows, and monitors DEM worker online status. Enter a unique name that identifies this DEM in the DEM name text box. If you plan to use the migration tool, this name must exactly match the name you used in your vCloud Automation Center 5.2.
Chapter 4 The Standard vRealize Automation Installation Interfaces You only need this procedure if you have SCVMM endpoints and agents. Prerequisites n Know the actual path where the SCVMM console is installed. The following is the default 2012 path that you must replace in the configuration file. path="{ProgramFiles}\Microsoft System Center 2012\Virtual Machine Manager\bin" Procedure 1 Stop the DEM Worker service. 2 Open the following file in a text editor. Program Files (x86)\VMware\vCAC\Distributed
Installing vRealize Automation Enable IaaS Database Access from the Service User If the SQL database is installed on a separate host from the Manager Service, database access from the Manager Service must be enabled. If the user name under which the Manager Service will run is the owner of the database, no action is required. If the user is not the owner of the database, the system administrator must grant access. Prerequisites n “Choosing an IaaS Database Scenario,” on page 77.
Chapter 4 The Standard vRealize Automation Installation Interfaces 5 Replace Integrated Security=True; with User Id=database-username;Password=database-password; 6 Save and close the files. ManagerService.exe.config Web.config 7 Start the VMware vCloud Automation Center service. 8 Use the iisreset command to restart IIS. Verify IaaS Services After installation, the system administrator verifies that the IaaS services are running. If the services are running, the installation is a success.
Installing vRealize Automation You have the option to install a vSphere agent as part of your minimal installation, but after the installation you can also add other agents, including an additional vSphere agent. In a distributed deployment, you install all your agents after you complete the base distributed installation. The agents you install depend on the resources in your infrastructure. For information about using vSphere agents, see “vSphere Agent Requirements,” on page 99.
Chapter 4 The Standard vRealize Automation Installation Interfaces Table 4‑13. Choosing an Agent Scenario (Continued) Integration Scenario Agent Requirements and Procedures Run Visual Basic scripts as additional steps in the provisioning process before or after provisioning a machine, or when deprovisioning. “Installing the EPI Agent for Visual Basic Scripting,” on page 114 Collect data from the provisioned Windows machines, for example the Active Directory status of the owner of a machine.
Installing vRealize Automation Table 4‑14.
Chapter 4 The Standard vRealize Automation Installation Interfaces Table 4‑14. Permissions Required for vSphere Agent to Manage vCenter Server Instance (Continued) Attribute Value Permission Remove Snapshot Revert to Snapshot Disable or reconfigure any third-party software that might change the power state of virtual machines outside of vRealize Automation. Such changes can interfere with the management of the machine life cycle by vRealize Automation.
Installing vRealize Automation 9 Log in with administrator privileges for the Windows services on the installation machine. The service must run on the same installation machine. 10 Click Next. 11 Select vSphere from the Agent type list. 12 Enter an identifier for this agent in the Agent name text box. Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future.
Chapter 4 The Standard vRealize Automation Installation Interfaces 20 Click Next. 21 Click Finish. 22 Verify that the installation is successful. 23 (Optional) Add multiple agents with different configurations and an endpoint on the same system. What to do next “Configure the vSphere Agent,” on page 103. Configure the vSphere Agent Configure the vSphere agent in preparation for creating and using vSphere endpoints within vRealize Automation blueprints.
Installing vRealize Automation 6 (Optional) To require a trusted certificate for the vSphere agent, modify VRMAgent.exe.config in a text editor. In the serviceConfiguration section, set the trustAllCertificates parameter to false. trustAllCertificates = "false" Because the setting is unencrypted, you do not use a DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set trustAllCertificates false command.
Chapter 4 The Standard vRealize Automation Installation Interfaces n Verify that all XenServer or Hyper-V instances on the hosts to be managed by the agent have administrator-level credentials. n If you are using Xen pools, note that all nodes within the Xen pool must be identified by their fully qualified domain names. vRealize Automation cannot communicate with or manage any node that is not identified by its fully qualified domain name within the Xen pool.
Installing vRealize Automation 12 Enter an identifier for this agent in the Agent name text box. Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future. Important For high availability, you may add redundant agents and configure them identically. Otherwise, keep agents unique. 13 Option Description Redundant agent Install redundant agents on different servers.
Chapter 4 The Standard vRealize Automation Installation Interfaces 23 Click Finish. 24 Verify that the installation is successful. What to do next For high-availability, you can install and configure a redundant agent for your endpoint. Install each redundant agent on a separate server, but name and configure the agents identically. “Configure the Hyper-V or XenServer Agent,” on page 107.
Installing vRealize Automation Installing the VDI Agent for XenDesktop vRealize Automation uses Virtual Desktop Integration (VDI) PowerShell agents to register the XenDesktop machines it provisions with external desktop management systems. The VDI integration agent provides the owners of registered machines with a direct connection to the XenDesktop Web Interface.
Chapter 4 The Standard vRealize Automation Installation Interfaces Set the XenServer Host Name In XenDesktop, the name given to the XenServer Host on your XenDesktop server must match the UUID of the Xen Pool in XenCenter. If no XenPool is configured, the name must match the UUID of the XenServer itself. Procedure 1 In Citrix XenCenter, select your XenPool or standalone XenServer and click the General tab. Record the UUID.
Installing vRealize Automation 10 Log in with administrator privileges for the Windows services on the installation machine. The service must run on the same installation machine. 11 Click Next. 12 Select VdiPowerShell from the Agent type list. 13 Enter an identifier for this agent in the Agent name text box. Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future.
Chapter 4 The Standard vRealize Automation Installation Interfaces 22 Click Next. 23 Click Finish. 24 Verify that the installation is successful. 25 (Optional) Add multiple agents with different configurations and an endpoint on the same system. What to do next For high-availability, you can install and configure a redundant agent for your endpoint. Install each redundant agent on a separate server, but name and configure the agents identically.
Installing vRealize Automation Install the Citrix Agent External provisioning integration (EPI) PowerShell agents integrate external systems into the machine provisioning process. Use the EPI PowerShell agent to integrate with Citrix provisioning server to enable provisioning of machines by on-demand disk streaming. Prerequisites n The IaaS components, including the Manager Service and Website, are installed.
Chapter 4 The Standard vRealize Automation Installation Interfaces 12 Enter an identifier for this agent in the Agent name text box. Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future. Important For high availability, you may add redundant agents and configure them identically. Otherwise, keep agents unique.
Installing vRealize Automation What to do next For high-availability, you can install and configure a redundant agent for your endpoint. Install each redundant agent on a separate server, but name and configure the agents identically. Installing the EPI Agent for Visual Basic Scripting A system administrator can specify Visual Basic scripts as additional steps in the provisioning process before or after provisioning a machine, or when deprovisioning a machine.
Chapter 4 The Standard vRealize Automation Installation Interfaces Install the Agent for Visual Basic Scripting External provisioning integration (EPI) PowerShell agents allow integrate external systems into the machine provisioning process. Use an EPI agent to run Visual Basic Scripts as extra steps during the provisioning process. Prerequisites n The IaaS components, including the Manager Service and Website, are installed.
Installing vRealize Automation 12 Enter an identifier for this agent in the Agent name text box. Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future. Important For high availability, you may add redundant agents and configure them identically. Otherwise, keep agents unique. 13 Option Description Redundant agent Install redundant agents on different servers.
Chapter 4 The Standard vRealize Automation Installation Interfaces Installing the WMI Agent for Remote WMI Requests A system administrator enables the Windows Management Instrumentation (WMI) protocol and installs the WMI agent on all managed Windows machines to enable management of data and operations. The agent is required to collect data from Windows machines, such as the Active Directory status of the owner of a machine.
Installing vRealize Automation 7 Accept the root install location or click Change and select an installation path. Even in a distributed deployment, you might sometimes install more than one IaaS component on the same Windows server. If you install more than one IaaS component, always install them to the same path. 8 Click Next. 9 Log in with administrator privileges for the Windows services on the installation machine. The service must run on the same installation machine. 10 Click Next.
Chapter 4 The Standard vRealize Automation Installation Interfaces 18 Click Install to begin the installation. After several minutes a success message appears. 19 Click Next. 20 Click Finish. 21 Verify that the installation is successful. 22 (Optional) Add multiple agents with different configurations and an endpoint on the same system. VMware, Inc.
Installing vRealize Automation 120 VMware, Inc.
vRealize Automation Post-Installation Tasks 5 After you install vRealize Automation, there are post-installation tasks that might need your attention.
Installing vRealize Automation You can also configure FIPS from a vRealize Automation appliance console session as root, using the following commands. vcac-vami fips enable vcac-vami fips disable vcac-vami fips status 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.
Chapter 5 vRealize Automation Post-Installation Tasks 16 Restart each replica node. 17 In DNS, remove the existing DNS record with the old master host name. Change a Replica vRealize Automation Appliance Host Name When maintaining an environment or network, you might need to assign a different host name to an existing replica vRealize Automation appliance.
Installing vRealize Automation 17 Restart each replica node. Note Afterward, RabbitMQ might still show the old replica node being in the cluster, but the old host name is shown as Not Connected and is safe to ignore. 18 In DNS, remove the existing DNS record with the old replica host name. 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.
Chapter 5 vRealize Automation Post-Installation Tasks 7 Assign your local users to the tenant administrator and IaaS administrator roles. a Enter a username in the Tenant administrators search box and press Enter. b Enter a username in the IaaS administrators search box and press Enter. The IaaS administrator is responsible for creating and managing your infrastructure endpoints in vRealize Automation. Only the system administrator can grant this role. 8 Click Update.
Installing vRealize Automation 126 VMware, Inc.
Troubleshooting a vRealize Automation Installation 6 vRealize Automation troubleshooting provides procedures for resolving issues you might encounter when installing or configuring vRealize Automation.
Installing vRealize Automation Log Default Location Installation Logs C:\Program Files (x86)\vCAC\InstallLogs C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\Log WAPI Installation Logs C:\Program Files (x86)\VMware\vCAC\Web API\ConfigTool\Logfilename WapiConfiguration- IaaS Logs IaaS logs are in the following locations. Log Default Location Website Logs C:\Program Files (x86)\VMware\vCAC\Server\Website\Logs Repository Log C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Logs
Chapter 6 Troubleshooting a vRealize Automation Installation Procedure 1 If the following components are present, uninstall them with the Windows uninstaller. n vRealize Automation Agents n vRealize Automation DEM-Worker n vRealize Automation DEM-Orchestrator n vRealize Automation Server n vRealize Automation WAPI Note If you see the following message, restart the machine and then follow the steps in this procedure: Error opening installation log file.
Installing vRealize Automation Table 6‑1. Roll Back Failure Points Failure Point Action Installing Manager Service If present, uninstall vCloud Automation Center Server. Installing DEM-Orchestrator If present, uninstall the DEM Orchestrator . Installing DEM-Worker If present, uninstall all DEM Workers Installing an Agent If present, uninstall all vRealize Automation agents.
Chapter 6 Troubleshooting a vRealize Automation Installation Solution 1 Increase your load balancer timeout value to at least 100 seconds. For example, and depending on the load balancer you are using, edit the load balancer timeout setting in your ssl.conf, httpd.conf or other Web configuration file. 2 Rerun the installation or upgrade. Server Times Are Not Synchronized An installation might not succeed when IaaS time servers are not synchronized with the vRealize Automation appliance.
Installing vRealize Automation Cannot Establish Trust Relationship for the SSL/TLS Secure Channel You might receive the message "Cannot establish trust relationship for the SSL/TLS secure channel when upgrading security certificates for vCloud Automation Center." Problem If a certificate issue occurs with vcac-config.
Chapter 6 Troubleshooting a vRealize Automation Installation What to do next Configuring to use a proxy might affect VMware Identity Manager user access. To correct the issue, see “Proxy Prevents VMware Identity Manager User Log In,” on page 145. Console Steps for Initial Content Configuration There is an alternative to using the vRealize Automation installation interface to create the configuration administrator account and initial content.
Installing vRealize Automation Cannot Downgrade vRealize Automation Licenses An error occurs when you submit the license key of a lower product edition. Problem You see the following message when using the vRealize Automation administration interface Licensing page to submit the key to a product edition that is lower than the current one. For example, you start with an enterprise license and try to enter an advanced license.
Chapter 6 Troubleshooting a vRealize Automation Installation Cause The Encryption.key file has incorrect permissions or the group or owner user level is incorrectly assigned. Solution Prerequisites Log in to the virtual appliance that displays the error. Note If your virtual appliances are running under a load balancer, you must check each virtual appliance. Procedure 1 View the log file /var/log/vcac/catalina.out and search for the message Cannot write to /etc/vcac/Encryption.key.
Installing vRealize Automation 7 Run the SQL query select * from databasechangeloglock. The output should show a value of "f" for locked. 8 Start the horizon-workspace service using the command service horizon-workspace start. Incorrect Appliance Role Assignments After Failover After a failover occurs, master and replica vRealize Automation appliance nodes might not have the correct role assignment, which affects all services that require database write access.
Chapter 6 Troubleshooting a vRealize Automation Installation Solution If the management interface displays errors during promotion, temporarily exclude the node from the load balancer. Correct the node problem, for example by adding disk, before re-including it on the load balancer. Then, refresh the management interface Database page and verify that the right nodes are master and replica.
Installing vRealize Automation Troubleshooting IaaS Components The troubleshooting topics for vRealize Automation IaaS components provide solutions to potential installation-related problems that you might encounter when using vRealize Automation. Validating Server Certificates for IaaS You can use the vcac-Config.exe command to verify that an IaaS server accepts vRealize Automation appliance and SSO appliance certificates. Problem You see authorization errors when using IaaS features.
Chapter 6 Troubleshooting a vRealize Automation Installation Save Settings Warning Appears During IaaS Installation Message appears during IaaS Installation. Warning: Could not save settings to the virtual appliance during IaaS installation. Problem An inaccurate error message indicating that user settings have not been saved appears during IaaS installation. Cause Communication or network problems can cause this message to appear erroneously.
Installing vRealize Automation Failed to Install Model Manager Data and Web Components Your vRealize Automation installation can fail if the IaaS installer is unable to save the Model Manager Data component and Web component. Problem Your installation fails with the following message: The IaaS installer failed to save the Model Manager Data and Web components. Cause The failure has several potential causes.
Chapter 6 Troubleshooting a vRealize Automation Installation n Repository Service Use the following actions to check the status of the repository service. n From a Web browser, check the status of the MetaModel service: https://FQDN-or-IP/repository/data/MetaModel.svc n Check the Repository.log for errors. n Reset IIS (iisreset) if you have problems with the applications hosted on the Web site (Repository, vRealize Automation, or WAPI). n Check the Web site logs in %SystemDrive%\inetpub\logs\LogFil
Installing vRealize Automation 3 Search for the reference code in the log file to locate the associated entry. 4 Review the entries that appear above and below the associated entry to troubleshoot the problem. The associated log entry does not specifically call out the source of the problem. Uninstalling a Proxy Agent Fails Removing a proxy agent can fail if Windows Installer Logging is enabled.
Chapter 6 Troubleshooting a vRealize Automation Installation 9 Click OK. 10 Remove machines that are stuck in the Clone Workflow state. a Log in to the vRealize Automation product interface. https://vrealize-automation-appliance-FQDN/vcac/tenant-name b Navigate to Infrastructure > Managed Machines. c Right click the target machine. d Select Delete to remove the machine.
Installing vRealize Automation n ManagerLeaseAboutToExpire n ManagerLeaseExpired n ManagerReclamationExpiredLeaseModified n ManagerReclamationForcedLeaseModified n ReclamationExpiredLeaseModified n ReclamationForcedLeaseModified n VdiRegister n VdiUnregister Email templates are located in the \Templates directory under the server installation directory, typically %SystemDrive%\Program Files x86\VMware\vCAC\Server. The \Templates directory also includes XSLT templates that are no longer supp
Chapter 6 Troubleshooting a vRealize Automation Installation Cause The vRealize Automation appliance nodes do not correctly form a high availability cluster until they can resolve the short hostnames of the nodes in the cluster. Solution To allow a cluster of high availability vRealize Automation appliances to resolve short hostnames, take any of the following approaches. You must modify all appliances in the cluster. Procedure n Edit or create a search line in /etc/resolv.conf.
Installing vRealize Automation 146 VMware, Inc.
Silent vRealize Automation Installation 7 vRealize Automation includes an option for scripted, silent installation. Silent installation uses an executable that references a text-based answer file, in which you preconfigure system FQDNs, account credentials, and other settings that you typically add throughout a conventional wizard-based or manual installation. Silent installation is useful for the following kinds of deployments.
Installing vRealize Automation 2 Navigate to the following directory. /usr/lib/vcac/tools/install 3 Open the ha.properties answer file in a text editor. 4 Add entries specific to your deployment in ha.properties, and save and close the file. Alternatively, you can save time by copying and modifying an ha.properties file from another deployment instead of editing the entire default file. 5 From the same directory, start the installation by running the following command. vra-ha-config.
Chapter 7 Silent vRealize Automation Installation 7 To silently install the Management Agent, double-click InstallManagementAgent.ps1. 8 (Optional) Verify that installation has finished by locating VMware vCloud Automation Center Management Agent in the Windows Control Panel list of Programs and Features, and in the list of Windows services that are running.
Installing vRealize Automation vRealize Automation Installation Command Line Basics The vRealize Automation installation command line interface includes top-level, basic operations. The basic operations display vRealize Automation node IDs, run commands, report command status, or display the help information. To show these operations and all of their options at the console display, enter the following command without any options or qualifiers.
Chapter 7 Silent vRealize Automation Installation For a complete list of available vRealize Automation commands, log in to the vRealize Automation appliance console, and enter the following command. vra-command help The long list of command names and parameters is not reproduced in separate documentation. To use the list effectively, identify a command of interest, and narrow your focus by entering the following command.
Installing vRealize Automation Convert Between vRealize Automation Silent Properties and JSON For silent vRealize Automation CLI or API based installations, you can convert a completed properties answer file to JSON or vice versa. The silent CLI installation requires the properties file, while the API requires JSON format. Prerequisites A completed properties answer file or completed JSON file /usr/lib/vcac/tools/install/ha.properties or /usr/lib/vcac/tools/install/installationProperties.
Index A account settings, specifying 58 agents choosing the installation scenario 98 configuring Hyper-V 107 configuring vSphere agents 103 configuring XenServer 107 enabling remote WMI requests 117 Hyper-V 104 installation location and requirements 99 installing 97 installing WMI 117 installing XenDesktop 109 installing Citrix agents 112 installing EPI agent for Citrix 111 installing for Visual Basic scripting 115 installing the EPI agent for VB scripting 114 installing vSphere agents 101 Visual Basic scr
Installing vRealize Automation E Email customizations 143 Encryption.key file, setting permissions 134 Endpoints Ooenstack DEM requirements 25 PowerVC DEM requirements 25 Enterprise deployment, install with wizard 41 EPI agents, installing for Visual Basic scripting 114, 115 external provisioning integration agents 13 F failed installation, logs 127 Federal Information Processing Standard (FIPS) 121, 141 FIPS (Federal Information Processing Standard) 121, 141 H ha.
Index installation wizard, enterprise deployment 41 Installation Wizard, overview 33 installation download, troubleshooting 134 installation failure, servers out of sync 131 installation type logging in 57 selecting 57 installing browser considerations 20 configuring vCloud Automation Center Appliances 68 download IaaS installer 76 worksheet 64 internal error, adding XaaS endpoint 141 J Java requirements, for MSSQL database 22 JSON 152 K key 39 keys 134 L license key 39 licenses 134 load balancer times
Installing vRealize Automation IaaS certificates 56, 75 passphrase 31 third-party software 31 trust relationships 63 server settings, specifying 58 server requirements, IaaS or Windows server 22 service registrations 137 silent installation answer file 149 JSON converter 152 Management Agent 148 properties converter 152 use cases 147 vRealize Automation 147 snapshots, creating 39, 46 SQL, requirements 21 SQL authentication 96 SQL Server database 12 SSL 132 SSL certificates, extracting 30 support bundle, cr
