Lifecycle Manager Installation and Configuration Guide vCenter Lifecycle Manager 1.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.
Lifecycle Manager Installation and Configuration Guide 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 © 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About This Book 7 Introducing LCM 1 Understanding LCM 11 Lifecycle Manager Process 11 Lifecycle Manager Terminology 13 Role-Based User Interface 13 User Roles and Permitted Tasks 14 LCM Administrator 14 Lifecycle Manager Architecture 15 2 LCM Installation Process 17 3 System Requirements 19 Hardware Requirements for Orchestrator 19 Operating Systems Supported by Orchestrator Supported Directory Services 20 Supported Browsers 20 Database Requirements 20 19 Installing and Configuring Orchestra
Lifecycle Manager Installation and Configuration Guide Password Encryption and Hashing Mechanism 38 Configure the Database Connection 39 Server Certificate 41 Configure the Default Plug-Ins 44 Import the vCenter Server License 47 Start the Orchestrator Server 48 Export the Orchestrator Configuration 50 Import the Orchestrator Configuration 51 Configure the Maximum Number of Events and Runs 52 Change the Web View SSL Certificate 53 Define the Server Log Level 53 7 Maintenance and Recovery 55 Change the Si
Contents Upgrading the vCenter Server Environment 77 12 Uninstall LCM and Orchestrator 79 Index 81 VMware, Inc.
Lifecycle Manager Installation and Configuration Guide 6 VMware, Inc.
About This Book The Lifecycle Manager Installation and Configuration Guide provides information about installing and configuring ® VMware vCenter Lifecycle Manager (LCM). Intended Audience This book is intended for administrators who are installing and configuring LCM. The information in this guide is written for experienced system administrators who are familiar with virtual machine technology.
Lifecycle Manager Installation and Configuration Guide Services provides offerings to help you assess, plan, build, and manage your virtual environment. To access information about education classes, certification programs, and consulting services, go to http://www.vmware.com/services. 8 VMware, Inc.
Introducing LCM VMware, Inc.
Lifecycle Manager Installation and Configuration Guide 10 VMware, Inc.
Understanding LCM 1 VMware vCenter Lifecycle Manager (LCM) automates the process of creating virtual machines and removing them from service at the appropriate time. Using LCM, you can perform the following tasks: n Handle and process virtual machine requests in a Web user interface. n Automatically place servers based on their location, organization, environment, service level, or performance levels. When a solution is found for a set of criteria, the machine is automatically deployed.
Lifecycle Manager Installation and Configuration Guide Figure 1-1.
Chapter 1 Understanding LCM Lifecycle Manager Terminology LCM uses specific terminology to describe lifecycle events and attributes. Commission The creation of a requested virtual machine. The commission time is submitted during the request process. Decommission The requested machine reaches the end of its life. A decommission date is submitted during the request process. The decommissioned machine can be archived or deleted.
Lifecycle Manager Installation and Configuration Guide User Roles and Permitted Tasks Every LCM user role can perform a certain set of tasks. The LCM Administrator can perform all tasks. Table 1-1 describes how roles are mapped to tasks. Tasks marked with an O can be performed only by the owner of the request. Table 1-1.
Chapter 1 Understanding LCM Lifecycle Manager Architecture LCM is powered by VMware vCenter Orchestrator 4.1. Orchestrator is a development and process-automation platform that provides a library of extensible workflows for creating and running automated, configurable processes to manage the VMware vCenter infrastructure. You can use Orchestrator to create custom workflows that you can run from LCM.
Lifecycle Manager Installation and Configuration Guide Orchestrator Plug-Ins After you install LCM, you must configure the following Orchestrator plug-ins: n vCenter Server 4.1 For adding vCenter Server instances. n vCenter Lifecycle Manager For configuring the Lifecycle Manager database. n Networking For configuring the networking database. n Mail For configuring email notifications. 16 VMware, Inc.
2 LCM Installation Process You must install and configure LCM by using both the Orchestrator configuration interface and the LCM interface. Before installing LCM, you must install and configure vCenter Orchestrator. You must use the Orchestrator configuration interface to configure the components that are related to the engine, such as the database, network, server certificate, and so on. These components must be configured correctly so that LCM functions properly.
Lifecycle Manager Installation and Configuration Guide 18 VMware, Inc.
System Requirements 3 Your system must meet the technical requirements that are necessary to install and configure VMware vCenter Orchestrator and VMware vCenter Lifecycle Manager. Because LCM runs as an Orchestrator plug-in, the hardware requirements and the supported operating systems are the same for both products.
Lifecycle Manager Installation and Configuration Guide Supported Directory Services LCM requires a working LDAP server on your infrastructure. LCM supports these directory service types. n Windows Server 2003 Active Directory n Windows Server 2008 Active Directory n Sun Java Directory Server Enterprise Edition (DSEE) Version 6.3 Supported Browsers The LCM user interface requires a Web browser. You must use one of the following browsers to connect to LCM.
Installing and Configuring Orchestrator VMware, Inc.
Lifecycle Manager Installation and Configuration Guide 22 VMware, Inc.
Orchestrator Components Setup Guidelines 4 To enhance the availability and scalability of your Orchestrator setup, install Orchestrator on a server different from the server on which vCenter Server runs. Separating Orchestrator from vCenter Server makes it possible to adjust the operating system to meet the specific recommendations for each service.
Lifecycle Manager Installation and Configuration Guide The way in which your database is set up can affect Orchestrator performance. Install the database on a virtual machine other than the one on which Orchestrator is installed. This method avoids the JVM and DB server having to share CPU, RAM, and IOs. Storing your database plug-ins in a database separate from the one that Orchestrator uses allows more modularity when upgrading the system.
5 Install Orchestrator You can install vCenter Orchestrator 4.1 only on a 64-bit operating system platform. If you run the installer in a 32-bit environment, the installation quits with a message stating that there was an error loading the Java VM. In production environments, and to enhance the scalability of your vCenter Orchestrator setup, install Orchestrator on a dedicated Microsoft Windows server. Prerequisites Make sure that your hardware meets the Orchestrator system requirements.
Lifecycle Manager Installation and Configuration Guide 7 Click Install to complete the installation process. 8 Click Done to close the installer. What to do next Check the status of the configuration service and start it if necessary. See “Check Configuration Readiness,” on page 28. 26 VMware, Inc.
Configuring Orchestrator 6 You must use the Orchestrator Web Configuration tool to configure the components that are related to the Orchestrator engine, such as network, database, server certificate, and so on. The correct configuration of these components ensures the proper functioning of Lifecycle Manager or any other applications running on the Orchestrator platform.
Lifecycle Manager Installation and Configuration Guide Check Configuration Readiness Before you start configuring Orchestrator, you can check whether the Web configuration service is ready. Procedure 1 In Windows, select Start > Programs > Administrative Tools > Services. 2 Select VMware vCenter Orchestrator Configuration. 3 If the status is not Started, right-click VMware vCenter Orchestrator Configuration and select Start.
Chapter 6 Configuring Orchestrator Change the Default Password You must change the default password to avoid potential security issues. Prerequisites The VMware vCenter Orchestrator Configuration service must be running. CAUTION To avoid potential exploitation of the administrative credentials, change the nonsecure password when you first access the configuration interface. Retaining the default password might cause serious security issues in a production environment and is a common cause of data breach.
Lifecycle Manager Installation and Configuration Guide Configure the Network Connection When you install Orchestrator, the IP address for your server is set as not set. To change this, you must configure the network settings used by Orchestrator. Prerequisites System administrators must make sure that the network provides a fixed IP, which is obtained by using a properly configured DHCP server (using reservations) or by setting a static IP.
Chapter 6 Configuring Orchestrator Table 6-1. VMware vCenter Orchestrator Default Configuration Ports (Continued) Port Number Protocol Source Target Description Data port 8244 TCP vCO Client vCO Server The port used to access all Orchestrator data models, such as workflows and policies. It is part of the Jboss Application server infrastructure. HTTP server port 8280 TCP end-user Web browser vCO Server The port used by the Orchestrator Server to connect to the Web frontend through HTTP.
Lifecycle Manager Installation and Configuration Guide Table 6-3. Internal JBoss Server Ports (Continued) Port Number Description 4445 JBoss pooled invoker 4446 Remoting server service connector 8083 Dynamic class/resource loader Change the Default Configuration Ports on the Orchestrator Client Side When you change the default network ports in the Orchestrator configuration interface, your changes are applied only on the Orchestrator server side.
Chapter 6 Configuring Orchestrator 4 5 Load the vCenter SSL certificate in Orchestrator from a URL address or file. Option Description Import from URL Enter URL of the vCenter server: https://your_vcenter_server_IP_address Import from file Obtain the server certificate file. Usual locations are: n C:\Documents and Settings\AllUsers\ApplicationData\VMware \VMware VirtualCenter\SSL\rui.crt n /etc/vmware/ssl/rui.crt Click Import. A message confirming that the import is successful appears.
Lifecycle Manager Installation and Configuration Guide Generate the LDAP Connection URL The LDAP service provider uses a URL address to configure the connection to the directory server. To generate the LDAP connection URL, you must specify the LDAP host, port, and root. The supported directory service types are Active Directory and Sun Java System Directory Server. Procedure 1 Log in to the Orchestrator configuration interface as vmware. 2 Click LDAP.
Chapter 6 Configuring Orchestrator 9 (Optional) Select the Use SSL check box to activate encrypted certification for the connection between Orchestrator and LDAP. If your LDAP uses SSL, you must first import the SSL certificate and restart the Orchestrator Configuration service. See “Import the LDAP Server SSL Certificate,” on page 35. 10 (Optional) Select the Use Global Catalog check box to allow LDAP referrals when the LDAP client is Active Directory.
Lifecycle Manager Installation and Configuration Guide 6 Click Startup Options. 7 Click Restart the vCO configuration server to restart the Orchestrator Configuration service after adding a new SSL certificate. The imported certificate appears in the Imported SSL certificates list. You activated secure connection between Orchestrator and your LDAP server. What to do next You must enable SSL on the LDAP tab in the Orchestrator configuration interface.
Chapter 6 Configuring Orchestrator 3 Define the User lookup base. This is the LDAP container (the top level domain name or organizational unit) where Orchestrator searches for potential users. a Click Search and type the top-level domain name or organizational unit. Searching for company returns dc=company,dc=org and other common names containing the search term. If you type dc=company,dc=org as a search term, no results are found.
Lifecycle Manager Installation and Configuration Guide 5 (Optional) To filter the attributes that the search returns, select the Filter attributes check box. Selecting this check box makes searching in LDAP faster. However, you might need to use some extra LDAP attributes for automation later. 6 (Optional) Select the Ignore referrals check box to disable referral handling. When you select the check box, the system does not display any referrals.
Chapter 6 Configuring Orchestrator Table 6-5. Encryption and Hashing Algorithms Algorithm Description Password Based Encryption (part of Java 2 SDK 1.4) Generates an encryption key from a password. PBE stores and checks the hash value of the password. For more information, see the Java Cryptography Extension Reference Guide on java.sun.com. Message Digest 5 algorithm Generates a 128-bit cryptographic message digest value, usually expressed as a 32 digit hexadecimal number.
Lifecycle Manager Installation and Configuration Guide 5 To build or update the table structure for Orchestrator, install or update the database. Option Description Install the database Configures a new database. Update the database Uses the database from your previous Orchestrator installation. After the database is populated, you can reset the database access rights to db_dataread and db_datawrite. 6 Click Apply changes.
Chapter 6 Configuring Orchestrator Server Certificate The server certificate is a form of digital identification that is used with HTTPS to authenticate Web applications. Issued for a particular server and containing information about the server’s public key, the certificate allows you to sign all elements created in Orchestrator and guarantee authenticity.
Lifecycle Manager Installation and Configuration Guide Create a Self-Signed Server Certificate Installing Orchestrator requires that you create a self-signed certificate. You can create a self-signed certificate to guarantee encrypted communication and a signature for your packages. However, the recipient cannot be sure that the self-signed package you are sending is in fact a package issued by your server and not a third party claiming to be you.
Chapter 6 Configuring Orchestrator What to do next You can import this certificate on other servers. Export a Server Certificate The server certificate private key is stored in the vmo_keystore table of the Orchestrator database. In case you lose or delete this key, or if you bind the Orchestrator server to a different database, the content of the exported packages signed with this certificate will become unavailable. To ensure that packages are decrypted on import, you must save this key to a local file.
Lifecycle Manager Installation and Configuration Guide 6 (Optional) Import your Orchestrator configuration. 7 Create a new self-signed certificate or import one. 8 Reimport your packages. a Click the Packages view in the Orchestrator client. b From the drop-down menu, select Import package. c Browse to select the package to import and click Open. d Click Import or Import and trust provider. e Click Import checked elements.
Chapter 6 Configuring Orchestrator 5 (Optional) To disable a plug-in, deselect the check box next to it. This action does not remove the plug-in file. 6 Click Apply changes. On the Plug-ins tab, the red triangle changes to a green circle to indicate that the component is now configured correctly. The first time the server boots, it installs the selected plug-ins. What to do next You can now configure the settings for Mail, SSH, and vCenter 4.1 plug-ins.
Lifecycle Manager Installation and Configuration Guide 5 Click Apply changes. The host is added to the list of SSH connections. 6 (Optional) Configure an entry path on the server. a Click New root folder. b Enter the new path and click Apply changes. The SSH host is available in the Inventory view of the Orchestrator smart client. Configure the vCenter Server 4.1 Plug-In Orchestrator uses the vCenter Web Service API to control vCenter Server.
Chapter 6 Configuring Orchestrator Remove a Plug-In You can disable an Orchestrator plug-in from the Plug-ins tab, but this action does not remove the plug-in file from the Orchestrator server file system. To remove the plug-in file, you must log in to the machine on which the Orchestrator server is installed and remove the plug-in file manually. Prerequisites Log in to the machine on which the Orchestrator server is installed.
Lifecycle Manager Installation and Configuration Guide 3 On the vCenter Server License tab, enter the details about the vCenter Server host on which Orchestrator must verify the license key. a In the Host text box, type the IP address or the DNS name of the vCenter Server host. b In the Port text box, leave the default value, 443. c (Optional) Select the Secure channel check box to establish a secure connection to the vCenter Server host. d In the Path text box, use the default value, /sdk.
Chapter 6 Configuring Orchestrator A message states that the service is started successfully. The Orchestrator server status appears at the bottom of each configuration tab and is one of the following: n Running n Not available n Stopped To see the Orchestrator server status, update the page by clicking the Refresh link. What to do next You can save and export the Orchestrator configuration file so that it can be imported later if needed. See “Export the Orchestrator Configuration,” on page 50.
Lifecycle Manager Installation and Configuration Guide Unwanted Server Restarts You might experience unwanted server restarts if you have activated the service watchdog utility. Problem In certain circumstances, if the response time exceeds the watchdog timeout period, the watchdog utility can falsely detect a JVM error, which causes a server restart.
Chapter 6 Configuring Orchestrator Table 6-7. Settings Not Saved During Configuration Export File Description certificate Certificates are not exported. Most certificates are stored in the Orchestrator database. However, the vCenter Server certificate is not stored in the database. You must store it in a separate location, or import it again when you import an Orchestrator configuration. licenses Manually imported licenses are not exported. They are stored in the Orchestrator database.
Lifecycle Manager Installation and Configuration Guide Configure the Maximum Number of Events and Runs You can define the maximum number of events stored in the database and the maximum number of workflow runs. Each event corresponds to a change in the state of a workflow or policy and is stored in the database. When the maximum number of events set for a workflow or policy is reached, the database deletes the oldest event to store the new event.
Chapter 6 Configuring Orchestrator Change the Web View SSL Certificate Orchestrator provides an SSL certificate that controls user access to Web views, such as LCM. You can configure Orchestrator to use a different SSL certificate to control access to Web views. For example, you can change the LCM SSL certificate if your company security policy requires you to use their SSL certificates. Procedure 1 Create an SSL certificate by running the keytool Java utility at the command prompt.
Lifecycle Manager Installation and Configuration Guide Option Description ALL Events are not filtered. All events are written to the log file. OFF No entries are written to the log file and no log updates are made. NOTE The log displays messages of the selected level and all higher levels. If you select the INFO level, all INFO messages and higher level messages (INFO, WARN, ERROR, and FATAL) are written to the log file. 4 Click Apply changes.
Maintenance and Recovery 7 The Troubleshooting tab in the Orchestrator configuration interface allows you to perform several bulk operations related to workflows and tasks. You can use the Troubleshooting tab to globally reset the server and remove all traces of previous runs. Table 7-1 lists the possible bulk operations. NOTE Before you click a troubleshooting option, make sure the Orchestrator server is stopped. Table 7-1.
Lifecycle Manager Installation and Configuration Guide Change the Size of Server Logs If a server log regenerates multiple times a day, it becomes difficult to determine what causes problems. To prevent this, you can change the default size of the server log. The default size of the server log is 5MB. Procedure 1 Open the log4j.xml file. The log4j.xml file is in the following location: installation_directory\VMware\Orchestrator\app-server \server\vmo\conf 2 Open the log4j.
Chapter 7 Maintenance and Recovery Troubleshooting Orchestrator If you are unable to access the Orchestrator configuration interface or a Web view, such as LCM, you can try restarting the Orchestrator services to troubleshoot the situation. Restart the Orchestrator Server You can restart the Orchestrator server if you are unable to access LCM. Procedure 1 In Windows, select Start > Programs > Administrative Tools > Services. 2 Select VMware vCenter Orchestrator Server.
Lifecycle Manager Installation and Configuration Guide 58 VMware, Inc.
Controlling Orchestrator Access 8 You can control access to Orchestrator to improve security. This chapter includes the following topics: n “Disable Access to the Orchestrator Client by Nonadministrators,” on page 59 n “Disable Access to Workflows from Web Service Clients,” on page 60 Disable Access to the Orchestrator Client by Nonadministrators When using LCM, the best practice is to limit access to the Orchestrator client only to administrators.
Lifecycle Manager Installation and Configuration Guide Disable Access to Workflows from Web Service Clients To prevent malicious attempts from Web service clients to access sensitive servers, you can configure the Orchestrator server to deny access to Web service requests. By default, Orchestrator permits access to workflows from Web service clients. You disable access to workflows from Web service clients by setting a system property in the Orchestrator configuration file, vmo.properties.
Installing and Configuring LCM VMware, Inc.
Lifecycle Manager Installation and Configuration Guide 62 VMware, Inc.
9 Installing LCM After you have installed vCenter Orchestrator, you can install vCenter Lifecycle Manager. This chapter includes the following topics: n “Installation Prerequisites,” on page 63 n “Install Lifecycle Manager,” on page 65 n “Configuring LCM Database Options,” on page 65 Installation Prerequisites Make sure that your system meets the installation prerequisites before you install LCM on Microsoft Windows. Table 9-1.
Lifecycle Manager Installation and Configuration Guide Table 9-1. Installation Prerequisites (Continued) Component Description LCM database Choose one of the following approaches: Use the same database as Orchestrator. Use a separate database for LCM (recommended). NOTE Because of CPU and memory usage, you should consider hosting the LCM database and the Orchestrator server on different machines on a local network with low latency.
Chapter 9 Installing LCM Install Lifecycle Manager You must install LCM through the Orchestrator configuration interface. Procedure 1 Log in to the Orchestrator configuration interface. http://orchestrator_server:8282 2 On the General tab, click Install Application. 3 Browse to select the LCM .vmoapp file. CAUTION If you are running Orchestrator on Windows Server 2008, you must manually rename the file extension to .vmoapp. When you download the .
Lifecycle Manager Installation and Configuration Guide Configure the Networking Database Plug-In The networking database table contains data related to the management of the IP addresses. Procedure 1 Log in to the Orchestrator configuration interface. http://orchestrator_server:8282 2 3 On the Networking tab, select the database connection type. Option Description Same as vCO Select this option to store LCM networking data in the Orchestrator database.
Configuring LCM 10 You must configure LCM before you can use it. The configuration process involves setting up the virtual machine naming convention, specifying groups, and selecting date and currency formats. You can also configure role-based attributes.
Lifecycle Manager Installation and Configuration Guide Initial Configuration of Lifecycle Manager You must complete the initial configuration of LCM when you run LCM for the first time. Procedure 1 Go to http://orchestrator_server:8280/vmo/lifecycle to log in to LCM for the first time. You need to log in with the credentials of a user who is a member of the administrator group that is selected in Orchestrator. 2 (Optional) Edit the default virtual machine naming convention.
Chapter 10 Configuring LCM Set Approval Requirements Virtual machines are decommissioned on the date selected by the requester when requesting the machine. LCM notifies the owner of the virtual machine five days before the decommissioning date with the option to request an extension. You can specify whether approval is required when virtual machines are requested, extended, or modified. Procedure 1 Log in to LCM as an administrator. 2 Click the Configuration view. 3 Click Edit Approval Modes.
Lifecycle Manager Installation and Configuration Guide 4 Under Management Groups, select or type appropriate values for the groups. 5 Under Requester Groups, select or type appropriate values for the groups. 6 Click Submit. Change the Naming Convention for Virtual Machines You can change the naming convention for a virtual machine. The default is lcm-####. Procedure 1 Log in to LCM as an administrator. 2 Click the Configuration view. 3 Click Edit Base Name.
Chapter 10 Configuring LCM 4 Click a notification ( ) in the left pane. The details about the notification appear in the right pane. 5 Click Edit. 6 For each notification, specify whether to enable it, who the recipients are, what appears in the Subject field, and a default email body text.
Lifecycle Manager Installation and Configuration Guide 72 VMware, Inc.
Upgrading Orchestrator and LCM VMware, Inc.
Lifecycle Manager Installation and Configuration Guide 74 VMware, Inc.
Upgrading to Orchestrator 4.1 and LCM 1.2 11 If you are using LCM 1.1.x and Orchestrator 4.0.1, you can upgrade to LCM 1.2 and Orchestrator 4.1. You must upgrade both LCM and Orchestrator. LCM 1.1.x is not compatible with Orchestrator 4.1, and LCM 1.2 is not compatible with Orchestrator 4.0.1.
Lifecycle Manager Installation and Configuration Guide Procedure 1 Create a package that contains all the Orchestrator elements that you created or edited. 2 Export the package. The upgrade procedure cannot affect the Orchestrator elements that you modified or created. What to do next Upgrade Orchestrator and restore the configuration data. In the Orchestrator client application, import the package that contains your custom elements and confirm the import of elements with lower version numbers.
Chapter 11 Upgrading to Orchestrator 4.1 and LCM 1.2 Upgrading an Installation Running on a 64-Bit Machine If Orchestrator 4.0.1 and LCM 1.1.x are installed on a 64-bit machine, you can install Orchestrator 4.1 and LCM 1.2 on the same machine. To upgrade to Orchestrator 4.1 and LCM 1.2, you must export the Orchestrator configuration settings, uninstall the existing installation, install Orchestrator 4.1 and LCM 1.
Lifecycle Manager Installation and Configuration Guide 78 VMware, Inc.
Uninstall LCM and Orchestrator 12 You can remove LCM from your system by uninstalling Orchestrator. You can remove the Orchestrator client and server components from your system by using the Windows Add or Remove Programs utility from the Control Panel. Prerequisites Save the Orchestrator system settings to a local file. For details, see “Export the Orchestrator Configuration,” on page 50. Procedure 1 From the Windows Start menu, select Settings > Control Panel > Add or Remove Programs.
Lifecycle Manager Installation and Configuration Guide 80 VMware, Inc.
Index A administrator tasks 14 approval modes 69 architecture 15 archiving settings 69 authorization groups 69 availability 23 B base name 70 C certificate database 43 changing the Orchestrator Lookup port 32 configuration config files 50 database connection 39, 40 default plug-ins 44 export configuration settings 50 import configuration settings 51 LCM database plug-ins 65 LDAP settings 36 network connection 30 configuration maximums 24 configuring LCM 67 Orchestrator 27 D data migration tool, back up
Lifecycle Manager Installation and Configuration Guide L LCM check configuration readiness 67 components 15 configuration 67 LCM Administrator 14 LCM Approver 13 LCM IT Staff 13 LCM overview 11 LCM Requester 13 LCM Tech Requester 13 LCM Web view, configuration 68 LDAP browsing credentials 36 connection URL 34 lookup paths 36 SSL certificate 35 LDAP errors 525 38 52e 38 530 38 531 38 532 38 533 38 701 38 773 38 775 38 license, importing vCenter Server license 47 lifecycle process overview 11 load balancing
Index reset current version 55 suspend tasks 55 U uninstalling 79 upgrading backing up database 75 infrastructure 77 Orchestrator and LCM installed on a 32-bit machine 76 Orchestrator and LCM installed on a 64-bit machine 77 stop Orchestrator server 76 upgrading Orchestrator and LCM 75 vCenter Server compatibility 15 vCenter Server plug-in 15 VirtualCenter 2.
Lifecycle Manager Installation and Configuration Guide 84 VMware, Inc.
