1.2.0

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.
For details about importing a package, see vCenter Orchestrator Administration Guide.
Upgrading an Installation Running on a 32-Bit Machine
If Orchestrator 4.0.1 and LCM 1.1.x are installed on a 32-bit machine, you must install Orchestrator 4.1 and
LCM 1.2 on a new 64-bit machine. You should use the same IP address and host name for the 64-bit machine
that you used for the source 32-bit machine.
To upgrade to Orchestrator 4.1 and LCM 1.2, you must export the Orchestrator configuration settings, stop the
Orchestrator server, install Orchestrator 4.1 and LCM 1.2 on a 64-bit machine, 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 “Stop the Orchestrator Server,” on page 76
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.
Stop the Orchestrator Server
Before you start upgrading to Orchestrator 4.1 and LCM 1.2, you must stop the Orchestrator server on the 32-
bit Orchestrator 4.0.1 machine.
Procedure
1 In Windows, select Start > Programs > Administrative Tools > Services.
2 Select VMware vCenter Orchestrator Server.
3 Right-click VMware vCenter Orchestrator Server and select Stop.
Lifecycle Manager Installation and Configuration Guide
76 VMware, Inc.