Hi, we are running vCenter 5.0 and want to utilise Orchestrator. I initally installed Orchestrator 5.5 on our vCenter Server and everything looked great but I wasn't getting any results when running workflows. I then checked the interoperability matrix and it suggests that with vCenter 5.0 it is only compatible with Orchestrator 5.1.0.
Is this correct? I installed Orchestrator 5.1.0 and the difference between that and 5.5 is incredible! There are loads of workflows already created for use in vCO 5.5 but none in vCO 5.1.
Is anyone running vCenter 5.0 with Orchestrator 5.5? Many thanks.
p.s. we are unable to upgrade our vCenter at this moment in time.
There is not such a difference between the number of workflows between 5.1 and 5.5. Most of the additional plug-ins are available as separate downloads.
I suspect that if you see very little amount of workflows it is because the 5.1 packages did not deploy. To fix this in the vCO configuration / troubleshooting tab use the Reinstall the plug-ins when the server starts link and restart the service. This will force the workflows to get redeployed.
Thanks for the reply. I reinstalled the plug-ins but there's still not many workflows compared to v5.5. All I can see is:
Library
Locking
Display all locks
Locking test
Locking test (x5)
Release all locks
Orchestrator
Tasks
Create recurrent task
Create task
Workflows
Start workflows in a series
Start workflows in parallel
Troubleshooting
Export logs and application settings
Workflow documentation
Get documentation for workflow
Get documentation for workflow category
XML
Samples XML (Address Book)
Append address book stylesheet information
Create address book CSS
Create address book DTD
Create address book XML
Full address book test
Samples XML (Simple)
Create a simple XML document
Find element in document
Modify XML document
Within 5.5 I had workflows I could run such as: Find all VMs modified in x date, Find all snapshots, etc etc
The vCenter workflows that you are mentioning are in vCO 5.1. If they do not appear in the list it means that your vCenter plug-in does not deploy properly. Make sure you have the last built available on the communities document page and that you forced resintallation of plug-ins + server start.