VMware vCenter Orchestrator Applicance-5.5.3

vCenter Orchestrator (vCO) 5.5 – Part 1 Deploying the Virtual Appliance

vCenter Orchestrator (vCO) is a product which allows you to create tasks and automated workflows which and be run directly within vSphere Web Client or the vCenter Orchestrator Client.

There are a number of pre-made workflows to get your started, and the number of tasks you can perform is quite amazing. Any task that can be performed in vCenter can be automated through vCO, and thats just the start. Add some Active Directory integration, API’s and other 3rd party plugin’s.

Workflows can be anything from simple workflows that contain a single task to say create a virtual machine, to complicated workflows containing many tasks that might build an entire solution and integrate with 3rd party plugins.

One of the best things about vCO is it’s included with vCenter Server and it’s free!

Here are high levels of the VCO 5.5 configuration Guides will cover.

  • vCenter Orchestrator (vCO) 5.5 – Part 1 Deploying the Virtual Appliance
  • vCenter Orchestrator (vCO) 5.5 – Part 2 Configuring vC
  • vCenter Orchestrator (vCO) 5.5 – Part 3 Using vCO and Running a Workflow


The latest version of vCenter Orchestrator (vCO) is 5.5.1 and has come on leaps and bounds since I originally saw it. This is my first proper look into vCO, it’s features and it’s going to take some time getting used to it. Not because it’s difficult to use, more because the possibilities seem quite endless and understanding what cool things are possible might take some time to discover. However I did find it difficult to find a decent resource to quickly get it up and running and hopefully this blog will address that for others.


vCO can be deployed in a number of ways, all achieve the same end solution and integrate with vSphere Web Client and Single Sign On.

  • Installed on a Windows Server (Co-installed with vCenter Server)
  • Installed on a Windows Server (Standalone)
  • Virtual Appliance


Production deployments such use a SQL server (not SQL express or the embedded DB in the appliance).

I’m going to use the virtual appliance and the embedded PostgreSQL database in my lab. I had to choose one and as I understand vCO so far there are no gotcha’s using the VA so I thought I’d go for that.

The virtual appliance weighs in at 2vCPU, 3GB vRAM and 12GB vDisk (Thick provisioned)

1. You may have noticed the vCenter Orchestrator plugin within the vSphere Web Client. Following the vCO icon takes you into vCenter Orchestrator with 0 vCO servers and no workflows.


2. Download the vCO Server Virtual Appliance

3. Deploy the vCO .ova template to the ESXi host or cluster.




4. Select the .ova file, Next.



5. Check the vCO version and size on disk, Next.




6. Accept the EULA (Click Accept), Next.




7. Give the vCO VA a name (I chose VCO1), select a DC or folder, Next.




8. Select Thick or Thin provisioned disk and the datastore to deploy to, Next.


9. Select the network to connect to and choose IP protocol IPv4, Next.

10. Enter a complex password (8 chars, include UPPER, lower, number and spec!al char)

11. Enter the Default GW, mask, IP address and DNS server IP.




12. Review your settings, tick “Power on after deployment” and Click Finish!




13. You will see the “Deploy OVF template” task run, this will take several minutes.

14. While you wait for it to deploy create a DNS A record for your vCO appliance
(e.g. vco.mvp.local)





15. Once the vCO virtual appliance has finished deploying it will power on.

Checking the console you will see that the appliance has booted and has the correct IP address, we are now ready to configure the appliance and vCO.


Note: Check you can ping the DNS name you created earlier (e.g. vco.mvp.local)



1. Now you have the vCO appliance deployed, powered on and it has an IP address (plus the DNS A record you created)



2. Open your web browser to <ip address or FQDN> ” port 8283



3. Login with Username: VMware

Password: <The Password Set During OVF Deployment>


4. Now you are logged into the vCO Configuration page, here we need to make a number of configurations before vCO will work.


5. First go to Network –> SSL Trust manager

6. You want to import from URL your vCenter and SSO certificates so you can connect to them later on in the config


e.g. https://vcenter01.mvp.local and https://vcenter01.mvp.local:7447



7. You will be prompted to accept the certificate. Click Import.




8. You will now see your certificates within the SSL Trust Manager




9. Go to Authentication

You can use either SSO or LDAP Authenication. in below example, We will use LDAP Authenication.


10. Select “LDAP Authenication”

(*For SSO Authenication you can us below administrator@vsphere.local.

*Enter your SSO server details (e.g.,https://vcenter01.mvp.local:7447 your SSO administrator (this might be administrator@vsphere.local and  SSO administrators password)


11. Click Register Orchestrator.



13. Now you need to select a “vCO Admin – domain and group” you can manage vCO (this could be vsphere.local Administrators, or your Domain Admins group if configured in SSO)


14. Click Update Orchestrator Configuration, all the dots next to the config items will turn green indicating that config is complete.


15. Go to vCenter Server

16. We need to add a vCenter Server so browse to the New vCenter Server Host tab and enter the details of a vCenter Server, Click Apply Changes.

17. Check your vCenter Server has been added in the Hosts tab.

18. Go to Licenses

19. Select “Use vCenter Server license” and enter your vCenter server details

20. Go to Plug-ins

21. Ensure the plugins are enabled, enter your SSO user and Click Apply changes

22. Go to Network

23. In the IP Address box select the IP address that the vCO service should bind to and Click Apply

24. Go to Startup Options

25. Under vCO Server, Click “Restart service”.

This will restart the vCO service, binding the vCO service to the correct network interface and also set the SSO authentication.

  • vCenter Orchestrator (vCO) 5.5 – Part 3 Using vCO and Running a Workflow

vcosnaphshot30daysRemove old snapshots 30 days. 


snapshotremoveworkflowsnapshotremovalworkflow2Vcenter Tasks Show Snapshot are remove based on VCO Remove Old snapshots -< 30 days criteria-  

VMware vCenter Orchestrator Applicance 


Leave a Reply

Your email address will not be published. Required fields are marked *