inconsistent clone Windows 2016 aperture in the AD role

[jhubner]

Hello, I have a problem with cloning the Windows 2016 server machine in the role of AD controller, I try to clone the virtual machine so that I can use it for testing purposes, however after cloning the machine and starting the machine I do not get into the domain unknown and public, even though the machine is in the role of controller, where could be the problem? I tested both under ESXi 6 and version 7

inconsistent Windows 2016 aperture in the AD role under ESXi 7.0

[fabio1975]

Ciao 

The need to clone the Domain Controller is to pre-create a lab environment in a closed network for testing, right?
Cloning the DC is not enough, there are additional steps.

[jhubner]

Hi Fabio,

yes it is a dedicated environment where I will restore 2 W2016 customer virtuales in the AD role and some as a fileserver and I need to test applications on it, but I can't even after cloning, what other steps are needed is not enough to just clone the system? for Windows 2008R2 this worked for me, thank you for the advice

Jan

 

[fabio1975]

Ciao 

Check this solution:

[SOLVED] Creating a Clone of a Domain Controller for a test environment - Disaster Recovery - Spiceworks

 

[jhubner]

Thank you very much Fabio for your help !! managed to solve

[fabio1975]

Ciao

Did you follow the steps indicated in the link?
If you mark it as solved

[jhubner]

Hi,

 

yes the links helped
Thank you

Jan