Were you even able in 7.1 to skip an initial power on? If so, I'm not sure in later versions this is something you can avoid as it's built into the provisioning process. You could always call some extensibility after it's on to power it off.
In 7.1 was no initial power on at basicVmWorkflow. I think in 7.1 it only was at the cloneWorkflow.
Yes i know that i can power off the machine but this is not the nice way ^^ (and i would interrupt the PXE Boot)
For any interested people, here is the solution:
You need an addition event subscription with event topic Machine provisioning with the condition "Data->Lifecycle state->Lifecycle state event" EQUALS "BasicVmWorkflow.CreatingMachine.EVENT.OnCreatingMachineComplete" and maybe a second condition if u dont want it for all your Blueprints. In the associated workflow, set the workflowNextState parameter to BuildComplete and put it as output parameter. Now the initial power on event will be bypassed and the machine will not turn on at this point.
Is this solution supported by vmware?
It's just EBS modification, so yes. You need to be familiar with EBS, however, and ensure you don't blow up all your other provisioning processes.
yes it is. It's a guidance from VMware engineering i got.
ups wrong account. sry
Is this avaialble in vra 7.3 ?
I'm trying to do the same in vRA 7.5 and a multi-machine blueprint.
My idea is that I'd like to have a component based on a clone with a really normal deployment and other components which should just be containers with disks and network but not started yet. The customer will start them later when the setup of that cloned vm is finished only.
As far as I understood, I just have to setup the event subscription correctly and make sure that for blueprint's components that need to bypass initial power on they run a workflow that output workflowNextState="BuildComplete".
I can confirm that I see in the log that the workflow is triggerd and it is as simple as that :
I can also confirm that EBS is working at blueprint's level because the cloned component machine trigger well the EBS.MachineProvisioned workflow.
What part of the magic sauce am I missing ?
All component vm are running after my deployment is complete.