Hi,
I created multiple blueprints in vCAC6 and some of them are Windows blueprints. Therefore to follow our company standards, we need to get vCAC to create the AD computer account before the Customization Specification from vCenter kicks in.
Using this blog: https://chris-alleaume.squarespace.com/blog/2014/1/24/running-vco-workflows-from-vcac-during-the-provisioning-of-a-virtual-machine
I added the "Create a computer in an organizational unit" workflow from the AD plugin to kick in on the ExternalWFStubs.MachineProvisioned using "Assign a state change workflow to a blueprint"
It does add the required inputs in the Blueprints Customs properties. But it seems that it required Static entries or a "Prompt user" type.
The 3 Customs properties required are, Domain Name, Computer Name and OU. Domain Name and OU can be static as it will be per Blueprints. But Computer Name needs to be whatever vCAC named the requested machine. Can I use something like ["VirtualMachineID"] as I dont want to prompt the user.
Or do I need to modify the Create a computer in an organizational unit workflow in vCO ?
Right now, if I type a value for domain name and computer name. It fails saying : "Workflow "WFStubMachineProvisioned" failed with the following exception: Error executing vCenter Orchestrator workflow: Cannot execute workflow : Unable to convert object, 'OU=Workstations,OU=vCAC,OU=xxxxxxx,OU=xxxxIntegrators,DC=xxxx,DC=LAB' plugin unexcepted exception : Bad type syntax 'string'"
In vCAC 5.2 we used to launch a powershell script using DesignCenter but we want to leverage vCO as much as possible instead of using powershell.
Screenshot:
Thank you
Alex