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
As you may know, Active Directory provides authentication and authorization mechanisms as well as framework from within other related services that can be deployed. As an LDAP compliant database, it contains most commonly used objects such as users, computers, and groups which can be organized into organizational units or OUs by any number of logical or business needs. Group Policy Objects or GPOs are then linked to OUs to centralize the settings for various users or computers across an organization. Part of the quandaries that IT professionals face is taking advantage of nuances provided in Active Directory in newer server offerings such as Windows Server 2012. As detailed in Pierre's post, "Windows Server 2012 Active Directory – What’s New?", Active Directory provided in Windows Server 2012 is provided impactful enhancements. Yet some organizations choose not to migrate due to reasons of uncertainty.
This Step-By-Step, suggestion online via the IT Professionals Community of Greater Toronto, is to help deal with that uncertainty and provide guidance for IT professionals looking to migrate their organizations Active Directory offering from Windows Server 2003 to 2012.
Transferring the Flexible Single Master Operations (FSMO) Role
Changing the Active Directory Domain Controller
Changing the Schema Master
Add the Active Directory Schema Console from MMC
Change the Schema Master
Once completed, open the Active Directory Users and Computers console to verify that the Active Directory database successfully replicated to your new Windows Server 2012 computer. Be aware that the database replication may take some time depending on the number of objects in Active Directory.
Removing the 2003 Windows Server from the Global Catalog Server
All that's left is to demote the old 2003 Windows server by first adding the new 2012 Windows Server as the Primary DNS, followed by running DCPROMO to demote the old 2003 Windows server.
Great info! Is there a similar article on going from 2008R2 AD to 2012?
Brian - Working on it now. Hope to have it up soon.
That'S great !
I plan to do that in my organization, mooving form AD 2003 to AD 2012, but I have to " transfert the server name and the IP address of my old 2003 server" to the 2012 server.
How could I do That ?
Albert - Can I ask why the naming convention and IP need to be kept the same?