You can use the Orchestrator configuration interface 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 applications running on the Orchestrator platform.

The Orchestrator Web Configuration tool is installed with Orchestrator standalone. To use the tool, you must first start the Orchestrator Configuration Service.

To use Orchestrator, you must start the Orchestrator server service and then start the Orchestrator client.

To use Orchestrator through the vSphere Web Client, you must configure Orchestrator to work with the same vCenter Single Sign-On instance to which both vSphere Web Client and vCenter Server are pointing. You must also ensure that Orchestrator is registered as a vCenter Server extension. You register Orchestrator as a vCenter Server extension when you log in as a user who has the privileges to manage vCenter Server extensions. For more information, see Configure the vCenter Server Plug-In.

When you log in as an administrator, you can modify the configuration settings as required by your organization. For instructions about how to start the Orchestrator Server service, see Start the Orchestrator Configuration Service and Start the Orchestrator Server. For more information about starting the Orchestrator client and using it, see Using the VMware vRealize Orchestrator Client.

When you install Orchestrator standalone, the Orchestrator server is also automatically configured to work, but you have to define a connection to a vCenter Server system if you plan to run workflows over the objects in your vSphere inventory. You can configure a connection to a vCenter Server system by running a workflow in the Orchestrator client. See Using VMware vRealize Orchestrator Plug-Ins.

The default Orchestrator database (embedded database) and LDAP (embedded LDAP) settings are not suitable for a production environment.

Preconfigured Software

User Group (if any) and User


Embedded Database

User: vmware


Embedded LDAP

User group: vcoadmins

User: vcoadmin

By default the vcoadmin user is set up as an Orchestrator administrator.


To use Orchestrator in a production deployment, you must set up a separate database instance, set up an LDAP or vCenter Single Sign-On server, and configure Orchestrator to work with them.


LDAP authentication is deprecated.

To configure the Orchestrator server, you can run configuration workflows by using the Orchestrator client or the REST API. For information about configuring Orchestrator by using the Configuration plug-in workflows, see Using VMware vRealize OrchestratorPlug-Ins. For more information about configuring Orchestrator by using the REST API, see Configuring Orchestrator by Using the Configuration Plug-In and the REST API.


When you configure Orchestrator, ensure that the clocks of the Orchestrator server machine and the Orchestrator client machine are synchronized.