I want to run scripts on the replicate VM not the source, but that doesn't appear to be an option.
Heres what I'm doing:
Replicate the DC and Terminal Server to a Test ESXi box that remaps it to fake versions of our subnets. this allows them to talk to each other but not the real world. Because I can't reach anyone else or RDP to it.
What I'm wanting to do:
After the above, I want to kick off Powershell Script on the replicated VM in the Fake domain (not production). The script, will change the logon.bat not to map drives and also import a version of a GPO that allows local login for all authenticated users. I don't want this to happen in the real world, just my freshly replicated, fake network VMs.
Pre-Freeze and Post-Thaw seem to be only about executing scripts on the Production servers, not the freshly replicated ones.
Obviously I can just kick off this script once I power up the VMs, but I was hoping to automate it, so I can kick off the Replications over night, and then first thing in the morning have a fresh test environment ready. I guess it begs the question, am I doing this the hard way, and should I be using SureBack instead with test Scripts?