Link to home
Start Free TrialLog in
Avatar of pauljnye
pauljnyeFlag for Afghanistan

asked on

Windows Server 2012 Active Directory removal for license key

We have two virtual domain controllers running Windows server 2012 Eval edition. Both have active directory and replication to each other. We need to add the license key to both machines, but according to Microsoft, AD can't be present when the code is added to change the version from eval mode. Are there any issues to be aware of when removing AD for the license key addition and then putting it back on? We will still have one AD server running while the other is not, and then vice versa.

Thanks.
Avatar of Nick Rhode
Nick Rhode
Flag of United States of America image

Explained in here:  http://technet.microsoft.com/en-us/library/jj574204.aspx

Scroll down to convert eval to full.
Avatar of pauljnye

ASKER

Yes, thats the page that says...

"If the server is a domain controller, you cannot convert it to a retail version. In this case, install an additional domain controller on a server that runs a retail version and remove AD DS from the domain controller that runs on the evaluation version"

So our concern is what could be the pitfalls to temporarily removing AD to convert the edition from eval to paid? Removing AD and adding it back sounds a bit scary? Will there be repercussions? What could happen to NTFS shares on this server?
ASKER CERTIFIED SOLUTION
Avatar of Nick Rhode
Nick Rhode
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Presuming the hypervisor isn't an eval version - can you create a new VM, register it and promote it to a DC?

Leave it for a few days/week and transfer the FSMO roles as NRhode mentioned.

Demote one of the other DC's, register and then re-register if you wish.....although if you are on Hyper-V 2012 you may want to just look at DC Cloning once you've registered the first DC and just decommission and delete the 2 evals (I usually delete the instance a while after they've been turned off just to make sure everything is OK).
Good answer given Microsoft's inability to provide an easy solution in this case