I've created some initial workflow customizations using VCAC Designer. One for BuildingMachine that invokes a couple vCO workflows with some properties, while the MachineProvisioned stub uses the InvokePowershell action to handle some SCCM post-provisioning tasks for Windows machines. Now, I'm working with VCAC plugin and have run the Install vCO Customization workflow and I run workflow to assign a vCO workflow to a blueprint and a state change workflow. The workflow gets triggered, so I know the integration is working. However, when I use VCAC Designer to load the MachineProvisioned workflow stub, I expected to see a new workflow stub for MachineProvisioned with an incremented Revision number, but I still see the old workflow that I created with the invokePowerShell action.
Should I see anything in VCAC Designer? I was half expecting to see some sort of Invoke vCO workflow wrapper, but since it isn't there, I'm unsure how my vCO workflow is getting invoked.
Until I get a substitute solution for invoking powershell, I think I'm going to have to uninstall the customization and then just use invoke vCO workflows with VCAC Designer. Or consider creating a vCO server on a Windows server instead of using the appliance (so I can run powershell from vCO if needed).
