In addition to configuring the vCenter Server plug-in by using the Orchestrator configuration interface, you can configure the connections to vCenter Server instances by running the vCenter Server configuration workflows in the Orchestrator client.


  1. Log in to the Orchestrator client as an administrator.
  2. Click the Workflows view in the Orchestrator client.
  3. In the workflows hierarchical list, select Library > vCenter > Configuration and navigate to the Add a vCenter Server instance workflow.
  4. Right-click the Add a vCenter Server instance workflow and select Start workflow.
  5. Type the IP address or the DNS name of the machine on which the vCenter Server instance you want to add is installed.
  6. Retain the default port value, 443.
  7. Keep the default location of the SDK to use to connect to your vCenter Server instance.
  8. Select whether you want to orchestrate the vCenter Server instance, and click Next.
  9. Select whether you want to ignore certificates warnings for the vCenter Server instances you want to add.

    If you select Yes, the vCenter Server instance certificate is accepted silently and the certificate is added to the trusted store.

  10. Select the method you want to use to manage user access on the vCenter Server system.



    Share a unique session

    Allows Orchestrator to create only one connection to vCenter Server.

    In the User name and Password text boxes, type the credentials for Orchestrator to use to establish the connection to the vCenter Server host.

    The user that you select must be a valid user with privileges to manage vCenter Server extensions and a set of custom defined privileges. Orchestrator uses these credentials to monitor the vCenter Web service, typically to operate Orchestrator system workflows.

    Session per user

    Creates a new session to vCenter Server. This might rapidly use CPU, memory, and bandwidth.

    Select this option only if your vCenter Server is in an Active Directory domain or if vCenter Server Single Sign-On is enabled.

    The user that you select must be a valid user with privileges to manage vCenter Server extensions.

    The user account that you select is also used by the policy engine to collect statistical and other data. If the user that you select does not have enough privileges, the policy engine cannot access the necessary parts of the vCenter Server inventory and thus cannot collect the necessary data.

  11. (Optional) Type the user domain.

    You must specify the user domain name only when you select to use a shared session.


    Fill this field if you are using LDAP authentication and session per user is selected.

  12. Click Submit to run the workflow.


After the workflow runs successfully, the vCenter Server instance and all vSphere objects that belong to it appear in the Inventory view.