I was trying to build a workflow for rebuilding a desktop/virtual machine for full-clone desktop pool. VMware article here mentions that
When you rebuild a virtual machine, the virtual machine is deleted and then cloned with the same virtual machine name and the AD computer accounts are reused. All user data or settings from the previous virtual machine are lost and the new virtual machine is created using the desktop pool template.
I am trying to achieve the same using a workflow. What I did in Workflow is:
Getting the same customizationSpec and Template from vSphere and start the cloning process with exact details. However, the machine then created doesn't register itself in Horizon Pool. Any suggestions what can i do here?
Looking at your image there I can't help notice one problem (always suggest the simplest fix first is a personal maxim so no insult intended here 😊)
In your screengrab, the workflow does not execute the "Add unmanaged Machine" workflow at all? The script step "Prepare inputs for..." just runs directly to the "Stop Workflow" icon so that's what will happen
As I say, if you're already done this, please ignore me 😉
Thanks for reply and suggestion. Yes I have already tried that. Thing is this workflow can only add Machines to a Manual Desktop Pool and in my case the pool type is Full-Clone Automated Desktop Pool. That's the reason its sideways now.