1 person found this helpful
I don't think you would want to add the new VM as a powershell host on creation as that would be a lot of mucking about
You could try the Guest Script Manager package - Guest script manager package - which can connect to a VM and run commands on the Guest OS.
Alternatively, you could create a single PowerShell "jumpbox" from which you could do PowerShell remoting to all created VMs. Then vRO could execute scripts on that host to deliver the config changes to the new VM after cloning.
Is there a reason why you're not using vRA for this by the way - this sort of use-case is exactly what vRA can do OOTB & in a very streamlined and flexible way. Also, you get much better support for Day 2 actions, inventory and lifecycle management, not to mention the ability to provide Self-service to your users
Thanks for the help. We do not currently own vRA, so its likely we will end up that direction. This is really our first big jump into larger scale automation. As I understand it, vRA is a separately licensed product correct?
Yes, vRA is a separate product so it would be a new licence. It does integrate with vRO though so anything you do now in vRO could still be used later. Also, the combination of the two makes a very powerful service platform for IT tasks