I'm trying to test some workflows straight from vCO and not using designer. I have no blueprints using the ExternalWFStubs.MachineProvisioned property without a value, all of mine have an ID pointing to the corresponding vCO workflow.
Previously I had tried using designer to invoke a powershell script, I stopped that after I was able to get it to run using the guest agent. Now it seems when I run a VM with a MachineProvisioned stub, I think it's trying to run that old designer state change which does not work. The error I'm seeing was giving me an error on a custom property that I'm not even using but was using in the old designer state change. I loaded the default stub and just pushed it to update, but now I'm getting an error "Cannot find file AssetCreate, version 1.0".
I'd like just completely disable using Designer if possible, it seems that the vCO integration is much better and easier to use. Anyone have an idea how to stop this from happening?