1.2.0
Table Of Contents
- Lifecycle Manager Installation and Configuration Guide
- Contents
- About This Book
- Introducing LCM
- Installing and Configuring Orchestrator
- Orchestrator Components Setup Guidelines
- Install Orchestrator
- Configuring Orchestrator
- Check Configuration Readiness
- Log In to the Orchestrator Configuration Interface
- Change the Default Password
- Revert to the Default Password for Orchestrator Configuration
- Configure the Network Connection
- Change the Default Configuration Ports on the Orchestrator Client Side
- Import the vCenter SSL Certificate
- Configuring LDAP Settings
- Password Encryption and Hashing Mechanism
- Configure the Database Connection
- Server Certificate
- Configure the Default Plug-Ins
- Import the vCenter Server License
- Start the Orchestrator Server
- Export the Orchestrator Configuration
- Import the Orchestrator Configuration
- Configure the Maximum Number of Events and Runs
- Change the Web View SSL Certificate
- Define the Server Log Level
- Maintenance and Recovery
- Controlling Orchestrator Access
- Installing and Configuring LCM
- Installing LCM
- Configuring LCM
- Check Configuration Readiness
- Initial Configuration of Lifecycle Manager
- Configure the LCM Web View
- Set Approval Requirements
- Configure Archiving Settings
- Change Authorization Groups
- Change the Naming Convention for Virtual Machines
- Enable Email Notifications
- Configure Email Notification Content
- Configure Currency and Date Formats
- Upgrading Orchestrator and LCM
- Uninstall LCM and Orchestrator
- Index
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.2, import the configuration settings, upgrade the
infrastructure, configure the vCenter Server plug-in, and start the Orchestrator server.
IMPORTANT Because LCM 1.1.x uses the VMware Infrastructure 3.5 plug-in and LCM 1.2 uses the vCenter
Server 4.1 plug-in, your environment's configuration is not migrated automatically. You must manually copy
the configuration of the VMware Infrastructure 3.5 plug-in and replicate it when you configure the vCenter
Server 4.1 plug-in.
To complete the upgrade, you must perform these procedures:
1 “Export the Orchestrator Configuration,” on page 50
2 Chapter 12, “Uninstall LCM and Orchestrator,” on page 79
3 Chapter 5, “Install Orchestrator,” on page 25
4 “Install Lifecycle Manager,” on page 65
5 “Import the Orchestrator Configuration,” on page 51
6 “Upgrading the vCenter Server Environment,” on page 77
7 “Configure the vCenter Server 4.1 Plug-In,” on page 46
8 “Start the Orchestrator Server,” on page 48
CAUTION You must perform the procedures in this exact order. If you start the Orchestrator server before you
complete the other procedures, your infrastructure elements might become unlinked. For instructions about
relinking unlinked elements, see the vCenter Lifecycle Manager Administration Guide.
Upgrading the vCenter Server Environment
If you are using a VirtualCenter 2.5 environment or a version of vCenter Server earlier than 4.0 Update 2, you
must upgrade to vCenter Server 4.1 or vCenter Server 4.0 Update 2. If you are using vCenter Server 4.0 Update
2, the upgrade to vCenter Server 4.1 is optional.
For detailed upgrade instructions, see the vSphere Upgrade Guide.
Chapter 11 Upgrading to Orchestrator 4.1 and LCM 1.2
VMware, Inc. 77