How can you start vCenter Orchestrator workflows ?

Workflows can be started as follows: By the vCO system service using the vCO scheduler By the vCO Administrator using the vCenter Orchestrator Client By an external application using the vCO SOAP Web service API By an end user using a Web browser: Using an existing Web portal through a URL Using the standard vCO Weboperator Web view Using a custom Web view that you create using the vCO Web toolkit

How does vCenter Orchestrator ship ?

vCO is installed (but not configured or started) as part of the vCenter server installation (since vCenter 4.0). It is also available available as a separate download for Lifecycle Manager (LCM) customers.

How is vCenter Orchestrator licensed ?

It is licensed with vCenter. Technically it requires you to have a valid vCenter license key. Depending on the vCenter License Edition, vCO will run in Player mode allowing you to run but not edit workflows, or in Server mode, allowing you to run and edit workflows. vCO runs in Player mode with the vCenter Essential and vCenter Foundation licenses, and runs in Server mode with the Standard and higher licenses.

Is vCenter Orchestrator a new product ?

Not really. vCO has been around for several years and has been re-branded a few times. It has been known as: VMware vRealize Orchestrator (vRO) - a component of the vRealize Suite VMware vCO - a component of vCenter that has been available since VMware vCenter 4 (released March, 30 2009) VMO - VMware Orchestrator. (until version 3.2). VMO was underlying platform of VMware Lifecycle Manager (released March, 30 2008) Dunes VS-O - Virtual Service Orchestrator (until version 3.