At the end of the last article, we had just finished installing all of the extra administrative tools necessary for modifying the Active Directory.
My forest has a single Windows Server 2008 R2 domain controller and three sites.
I’m going to upgrade using an IT generalist scenario for a small to medium business: I want to add a Windows Server 2012 R2 domain controller in my Active Directory forest to take advantage of many new features (such as new UIs for the Recycle Bin and fine grained password policies), and I don’t want to sweat the small stuff.
This one doesn't appear on the menu; to add the tool to the Microsoft Management Console, follow these steps: You're now ready to modify the schema.
Before you do, however, make absolutely sure that you're working directly with the domain controller on which you enabled schema write access.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.
Why is upgrading your Active Directory schema so concerning? An Active Directory schema extension, which is always part of the upgrade to a new release of the Windows Server OS, is extremely difficult to reverse, and only done in the most dire circumstances.
In the intervening years since this process was introduced, however, the ADPREP process has been proven to be very reliable, and excessive worry about this process unjustified.
Therefore great attention to detail should be applied to both process and procedure. if not OK , destroy DC and remove it from config and DNS (metadata cleanup) There are other approaches.
One approach of sever that has worked for myself and colleagues with customers is as follows; Suggested Schema Update Physical Process 1. For example by doing the schema update on the Server that holds the role and not introducing a New Domain Controller into the Forest for just this action. The key to the success of a Schema Update is to ensure you THOROUGHLY test it prior to deployment in a pre-production environment.
In Windows Server 2012 and R2, Microsoft has gone a step further and streamlined and integrated the ADPREP forest and domain upgrades and DCPROMO domain controller promotion processes into one Active Directory Domain Service Configuration Wizard that takes care of everything.