When you export the system configuration, a vmo_config_dateReference.vmoconfig file is created locally on the machine on which the Orchestrator server is installed. It contains all the Orchestrator configuration data.


Some of the configuration files that are created during the export are empty. For example, the server configuration data is not exported because the startup options for the Orchestrator server are unique for each machine where the Orchestrator server is installed. These empty files must be reconfigured, even when a working configuration was previously imported.

Settings Not Saved During Configuration Export




Manually imported licenses are not exported. They are stored in the Orchestrator database.


The server configuration is reset to Unknown. You must install the Orchestrator server as a Windows service again.

Settings Saved During Configuration Export




The key used to encrypt the sensitive data. If the file is not valid, the sensitive data hashes stored in the database become unusable.


The maximum number of completed events and workflows recorded, and the Web view development and configuration.


The IP binding address and the TCP ports used by the different elements of the Orchestrator server.


The database configuration.


The certificates added as trusted authorities.


The LDAP server configuration.


The log settings information.


The list of disabled plug-ins and the account name.

Mail plug-in

The SMTP host, SMTP port, user name, password, sender's name, and sender's email address.

vCenter Server plug-in

The vCenter Server plug-in configuration.

Each vCenter Server plug-in has an ID element , for example <guid>36907986-d951-4f9a-9542-c561f4b94c3f</guid>, which is used as an identifier of the vCenter Server instance.

In case you do not use the export for backup purposes, make sure that you change the unique ID of the vCenter Server plug-in.


The details about the vCenter Server host on which Orchestrator verifies the license key.


The certificates added as trusted authorities.


The internal private key generated for each Orchestrator server instance. It is used as an identifier. The vCenter Server plug-in uses this key to register to the vCenter Server instances and uses it for logging in to the vCenter Server instances. If the key changes, the vCenter Server plug-in cannot log in anymore.