Hi there,
I'm struggling around with this special issue.
We have some vRO subscriptions in vRA to clear DNS-Records and AD-Computer Accounts after destroying deployments. In case of destroying something this is working fine.
But in case of reprovision we often get timing issues. If a computer account gets deleted and recreated shortly afterwards, it often happens that the "create AD Account" Job fails and and the new deployed VM joins into a wrong OU (default OU Computers) to AD where many of our necessary GPOs are not linked.
My big question is. How can vRO distinguish between reprovision and a completely unprovision (destroy)??
Because the cleanup job should only run if I give a destroy request
Or how should I setup the conditions for the subscriptions.
I've tried: VMPSMasterWorkflow32.Disposing and VMPSMasterWorkflow32.Unprovision -> both states seems to be used in reprovision AND destroy. Therefore -> useless for my purpose.
I need a condition which can differentiate between destroy and reprovision.
Does anyone have any ideas?
Many Thanks in advance