Orchestrator and VIX Plugin Workflow

[BackOfficeTeam]

Hi Guys

I am having two working workflows:

• Clone and sysprep
  
• Copy Files, Run a Script, Delete Directory, Reboot
  

So when I run first workflow (Clone and Sysprep) it’s finished successfully

When I run ( Copy Files, Run a Script, Delete Directory, Reboot) it’s also finished successfully

But when I add workflow (Copy Files, Run a Script, Delete Directory, Reboot) to the workflow (Clone and sysprep ) it always failed on the beginning of the workflow (Copy Files, Run a Script, Delete Directory, Reboot)

Error message is The virtual machine needs to be powered on.:3006

Workflow Screenshots :

Clone and Sysprep

Copy Files, Run a Script, Delete Directory, Reboot

Any Ideas ?

[tschoergez]

Hi!

I cannot test your workflows right now, but:

Where exactely does the error occur? Inside the clone or the copy files workflow?

What's the meaning of the last "Power on" Decision element? (Why do you run a shutdown guest if poweron is false?)

Did you bind the right workflow attribute to the copy... workflow?

Can you monitor manually if the virtual machine is running?

Regards,

Joerg

[BackOfficeTeam]

When I run First Workflow (Clone and Sysprep) without (Copy files workflow) it finished successfully

When I run Second Workflow (Copy file) and chose any VM it is working fine

It is failing when I copy workflow (copy file) to the workflow (Clone and Sysprep) – in this case (Clone and sysprep) will finished successfully then it will start (Copy file) and it will failed

Error message is The virtual machine needs to be powered on.:3006

Vm is power on and VM tools are ok

All attributes are ok

According to my story everything is ok but I am still having a problem J

Why do you run a shutdown guest if poweron is false?)

If there’s  any problems during sysprep it will shutdown VM

Can you test my workflows maybe you will find something that I miss

[tschoergez · Accepted solution]

Hi!

If I see right, you bound the wrong VcVirtualMachine to the Copy Files....-Workflow:

You don't need the workflow-input-parameter "vm", but the result of the cloning task: tempNewVM

When you bind this workflow-attribute to the copy-files workflow element it should work.

Regards,

Joerg

[BackOfficeTeam]

Thanks Champ that fix problem