#acl merlyn:read,write All:read <> = Migration ActiveDomain Controller Windows2003 32bit to Windows2008R2 = * https://social.technet.microsoft.com/wiki/contents/articles/2903.active-directory-high-level-steps-to-upgrade.aspx == 1. Schema upgrade == The new object classes and attributes for the Windows Server 2003 R2 schema update are defined in a file named Sch31.ldf, which is located in the \cmpnents\R2\adprep folder on the Windows Server 2003 R2 Disc 2 (not in the \I386 folder of the Windows Server 2003 R2 Disc 1). You can view Windows Server 2003 R2 .ldf files in a text editor, but under no circumstances should their contents be modified. Modification of the .ldf files can cause irreversible changes and forest-wide failure. Use the Adprep command to make all schema updates. Do not use import tools such as LDIFDE to import the Windows Server 2003 R2 .ldf files. * https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc755834%28v%3dws.10%29 == 2. Verify the schema version == {{{ dsquery * cn=schema,cn=configuration,dc=sivarajan,dc=com -scope base -attr objectVersion The following table lists the Active Directory Schema and the corresponding Object Version: Active Directory Object Version Windows 2000 13 Windows 2003 30 Windows 2003 R2 31 Windows 2008 44 Windows 2008 R2 47 Windows 8 Beta 52 Windows 2012 56 Windows 2012 R2 69 Windows 2016 87 Windows 2019 88 }}} == 3. Add new server == Install new server with a correct version of OS and join this server to the existing domain.. == 4. Promote server to DC == Perform DCPRMO on this server and select Additional Domain Controller for an existing Domain option. Beginning with Windows Server 2012, you can install AD DS using Windows PowerShell the Install-ADDSDomainController command. Reference http://technet.microsoft.com/en-us/library/cc753720(WS.10).aspx Jump http://technet.microsoft.com/en-us/library/hh472162#BKMK_PS Jump Note - If you are using Active Directory Integrated (ADI) DNS, it will get replicated as part of the Active Directory replication. == 5. Transfer FSMO off decomissioned servers == If you are planning to decommission the old servers, you need to transfer FSMO roles, DHCP, etc to the new server. Note - You can identify the FSMO role DC information using Netdom /Query FSMO command. References * FSMO - http://support.microsoft.com/kb/324801 Jump * DHCP - http://support.microsoft.com/kb/962355/en-us Jump == 6. Remove old dc == You can remove (demote) a domain controller using DCPROMO command and again, since WS2012 also possible with PowerShell. References * http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx Jump * http://technet.microsoft.com/en-us/library/hh472163#BKMK_RemovePS Jump