Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
With the end of support for Windows Server 2003 creeping towards us, many IT professionals has taken an interest in our previous post entitled Step-By-Step on Active Directory migration from Windows Server 2003 to Windows Server 2012 R2. Others who are currently running Windows Server 2008 R2 have notably been a little more relaxed but have too taken an interest in what Windows Server 2012 R2 and its inherent gateway to the cloud capability and with good reason. If you were lucky enough to attend TechEd 2014 you have come to understand the importance of what Azure has to offer and how it can enable the organization you support. As mentioned, Windows Server 2012 R2 provides a great first step towards cloud adoption. In addition to this the ability to allow your organization to take advantage of capabilities such as Active Directory Recycle Bin improvements, DHCP failover, Dynamic Access Control, Hyper-V replication and much more.
This Step-By-Step was created to ease IT professionals into this enablement. Migrating Active Directory off your existing Windows 2008 R2 server and onto a new Windows 2012 R2 server will serve a small step for your IT department and a giant leap for your organization.
Step 1: Preparing your existing forest via the adprep command
Insert the Windows Server 2012 DVD into the DVD drive of the Windows Server 2008 R2 AD DS.
Open command prompt, and type adprep /forestprep and press enter.
Check the Schema version of AD DS (After adprep) by running regedit, navigating to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NTDS\Parameters and noting the current Schema version.
Step 2: Promoting the Windows Server 2012 Server domain controller
Step 3: Verify the new Windows Server 2012 Domain Controller
Step 4: Transferring the Flexible Single Master Operations (FSMO) Role
Step 5: Removing the Windows 2008 R2 domain controller
Now that you have successfully dabbled in taking advantage of Windows Server 2012 R2, why not invest a little more time to learn the further advantages your organization's new server offering can enable. Visit Microsoft Virtual Academy and complete the What's New in Windows Server 2012 R2 Jump Start and get your head in the clouds.
Good information but the title is very misleading, a domain migration is not the same thing as adding a newer AD server and migrating the roles over.
I m doing my studies in IT network,and this information is usefull
Very Nice Explanation ...Its very useful for me
Britt: Please explain. Seems like adding a newer AD server and migrating the roles over (and removing the old server) is exactly what a domain migration is. What am I missing?
Thanks a lot!, Very good article.