VMware roadmaps are only communicated to customers / partners under NDA by VMware employees accredited to do so. This is not the case of the vCO Team members.

As of version 4.0.2, vCO has out-of-the-box support for the entire vCenter Server 4 API, as well as generic plug-ins that provide email, SSH, database, and XML APIs, allowing you to integrate with a large number of products. Also, vCO supports other plug-ins that are available as separate downloads, for example the Microsoft (Active Directory and WMI), and VMware Infrastructure 3.5 (vCenter 2.5) plug-ins. VMware partners are also developing vCO plug-ins.

A team of vCO experts and enthusiasts including VMware and non VMware consultants, system engineers, R&D engineers from all around the globe. This site should be viewed as an unofficial enthusiast site only and all OFFICIAL details and release info should be checked on the official VMware website.

Initially, most customers who used vCO in production were running large datacenters. These are typically Service Providers, Financial and Industrial enterprise-level companies. With the increase in recent years of server capacity and of virtualization the user base has broadened within all sectors and company sizes.

vCO is owned by VMware. It is trademarked as "VMware vCenter Orchestrator".

There are a considerable number of pre-built actions that may be used to build your own workflows. The environment this table is taken from has the VC, VIM3, and Microsoft vmoapps installed: Module: com.vmware.basic com.vmware.basic createDirectory Description: Create a directory structure on the VS-O server. com.vmware.basic getFileName Description: Strip directory from filenames. Module: com.vmware.constants com.vmware.constants getDefaultCompanyName Description: Returns the company name.

This article is the first in a series of tutorials for developing a basic VM self service portal. It is meant to be educational rather than exhaustive. Other articles will follow up for supporting more advanced features and a less static configuration. Concepts covered in this article include: How to create a simple Workflow How to map inputs, outputs, and attributes How to launch a Workflow from a webview, using the vCenter Orchestrator Weboperator How to launch a Workflow from the vCenter Orchestrator Client NOTE: Webviews were deprecated and removed in vRealize Orchestrator 7.

To increase usability and acceptance of vCO we - mightycare solution - created a vCO Plugin for vSphere Client. So admins and users has a direct access to the big world of vCO workflows. Actual our Beta comes up with following features: customizable context menu for virtual machines state and parameter values for running workflows optional prompt for finished workflows with values and state (can be checked for each flow) customizable input for input parameters - predefined or prompt for input (for each parameter in each flow) all settings per user, saved in registry - roaming user friendly To make a round tool we need your input - what do you think about it - what functions do you need in a tool like this.

Are you getting started with VMware’s vCenter Orchestrator? vCO can be a challenge or a breeze to learn depending on your skill sets and what you’re trying to accomplish. It allows for the creation of very complicated workflows with minimal effort if you know where to look and are familiar with the interface. Knowing where to look can sometimes be key. I’ve launched this site in an effort to help enlighten those getting started with vCO so I welcome your feedback.

This article will describe the steps necessary to install and configure VMware vCenter Orchestrator (VCO). Parts of the configuration are often a challenge even for experienced administrators. My goal here is to help you get a functional VCO server up and running. I've even put together a step-by-step video on How to Install vCenter Orchestrator here on vCOTeam.info ! Take a look & tell your colleagues! Updated comments for vCO 4.