Hi All,
this question gets asked a lot... but not definitive answer. MS articles advise not to export DC VMs, another article will mention you can export the live environment (but don't import the exported VM into the live system.... as if!) and theres heaps of stuff people have done and tried....?!!?
So, the situation. I would like to create a test environment from our production DCs to a test lab. The test lab will be a standalone machine with no network access to the production environment. I have 2012 DCs (VM's) and 2008 DCs (physical). I would like to have 1... maybe two dc's in my hyperV test lab.
What I intend to do.
1. Using the hyperV console, export the 2012 DCs to a folder.
2. Copy the folder containing the Vm export to the standalone environment.
3. Set up a virtual switch. Import the DC into hyperV and, let it grumble, seize FSMO roles, tidy the dns settings and perform general health checks.
Why do I need a lab? The main reason is testing for:
1. Migration to DFSR from FRS (After 2016 DCs v1709 - FRS is no longer supported from v1709).
2. Demotion of 2008 DCs
3. Promotion for 2016 DCs.
My question is - is there a reason why this configuration for a test lab would not work.? Taking the export via hyperV of the production DC whilst running will not cause any issues with the DC?
I've read so much on the web where people get knotted up about exporting the VM of a DC. I understand the implications concerning the USN etc etc... but this is why I'm being overly cautious and placing the copy of the VM onto a standalone machine. I will NOT be importing this dc into my production environment so is there a good reason not to perform an 'export' and export (copy) the live VM that's a DC...?
I look forward to your advice!
John