If you upgrade Orchestrator by upgrading vCenter Server 5.0 or later to vCenter Server 6.0, the vco_export.zip archive, located at %VMWARE_CIS_HOME%/vco might not get created automatically and your configuration might not be migrated.

Problem

During the export phase of the upgrade, Orchestrator upgrade script collects configuration files and data, and stores them in the vco_export.zip archive. In some cases the archive might not be created automatically and must be created manually if you want to preserve the data after the update.

During an export, Orchestrator accesses the Windows registry to find the necessary data. If Orchestrator cannot access that data, the automatic export does not occur.

Procedure

  1. Create the vco_export.zip archive manually with the necessary data, and save it to %VMWARE_CIS_HOME%/vco.

    The export archive must contain the following files:

    File

    Location

    Description

    Plug-in DAR files

    • On Orchestrator 5.5.x: install_directory\VMware\Orchestrator\app-server\plugins

    • On Orchestrator 5.1 or earlier: install_directory\VMware\Orchestrator\app-server\server\vmo\plugins

    A copy of the plug-in .dar files. During the import phase, plug-ins are not downgraded. Orchestrator imports only the plug-in configuration but a .dar file is not substituded by an earlier version. If a source plug-in is not installed on the destination system, it is imported and disabled. Source plug-ins might not be verified for Orchestrator 6.0.1 and might cause errors.

    vmo_config.zip

    The location varies. After you export the file, you receive a message with the location of the file.

    This file has the same content as the .vmoconfig file generated by the Orchestrator Configuration's Export Configuration option found on the General tab.

    Properties files

    • On Orchestrator 5.5.x: install_directory\VMware\Orchestrator\app-server\conf

    • On Orchestrator 5.1 or earlier: install_directory\VMware\Orchestrator\app-server\server\vmo\conf

    All of the .properties files located in the folder. The folder may also include custom defined properties. The file sso.properties is present only if the source system is configured to use Single Sign-On.

    jssecacerts

    On Orchestrator 4.2.x: install_directory\VMware\Orchestrator\jre\lib\security\jssecacerts

    This file is included only in Orchestrator 4.2.x. In later versions, the file is a part of vmo_config.zip. It contains the Certificate Authorities certificates, which are imported through the Orchestrator configuration interface.

  2. Use the archive to migrate your configuration.
    1. Log in to the Orchestrator configuration interface as vmware.
    2. On the General tab, click Import Configuration.
    3. Type the password you used when exporting the configuration.

      This step is not necessary if you have not specified a password.

    4. Browse to select the vco_export.zip file.
    5. Select whether to override the Orchestrator internal certificate and network settings.

      Select the check box only if you want to restore your Orchestrator configuration and the vco_export.zip file is the backup file of the same Orchestrator configuration.

      If you import the configuration to duplicate the Orchestrator environment, for example for scaling purposes, leave the check box unselected. Otherwise you might have problems with the certificates when Orchestrator tries to identify against vCenter Server, vCenter Single Sign-On or the vSphere Web Client.

    6. Click Import.