Armitage318
asked on
Add a new DC beside Windows Server 2003
Hi,
we have a very old domain controller (bare metal) with Windows 2003 server, and we want to add a new ADD (with a more recent OS of course) and remove the old one.
Which Windows OS are eligible to do this? Can I add directly a Windows 2012 server domain controller?
At this moment I don't remember domain level (I mean: Windows 2000 or 2003).
Thank you
we have a very old domain controller (bare metal) with Windows 2003 server, and we want to add a new ADD (with a more recent OS of course) and remove the old one.
Which Windows OS are eligible to do this? Can I add directly a Windows 2012 server domain controller?
At this moment I don't remember domain level (I mean: Windows 2000 or 2003).
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
There is no need to use an intermediate dc, you can follow the steps laid out in this previous EE_PAQ which also outlines the information from the article you linked: https:/Q_28695608.html
-saige-
-saige-
According to MS it is not mandatory to run ADPREP.
Also, unless you ran ADPREP from the 2012 media, you did not ADPREP the domain for 2012, you did it for 2008. ADPREP for 2012 is handled by the Active Directory Domain Services Role wizard from the 2012 server.
Starting with Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep /forestprep and adprep /domainprep automatically run and report the results of the operations. Some organizations may prefer to run Adprep.exe separately, either in advance of an AD DS installation or simply to extend an existing AD DS schema to support new features such as the Device Registration Service in Windows Server 2012 R2. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
Also beginning with Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008 or later. The computer where you run it can be either domain-joined or in a workgroup. It includes new syntax and parameter options in order to run it remotely.
For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012 R2 and Windows Server 2012, see Changes to Adprep.exe.
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd464018(v=ws.10)
Please check this similar thread.
https://www.experts-exchange.com/questions/28593177/Upgrading-schema-to-2012-from-2003-DC.html
Also, unless you ran ADPREP from the 2012 media, you did not ADPREP the domain for 2012, you did it for 2008. ADPREP for 2012 is handled by the Active Directory Domain Services Role wizard from the 2012 server.
Starting with Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep /forestprep and adprep /domainprep automatically run and report the results of the operations. Some organizations may prefer to run Adprep.exe separately, either in advance of an AD DS installation or simply to extend an existing AD DS schema to support new features such as the Device Registration Service in Windows Server 2012 R2. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
Also beginning with Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008 or later. The computer where you run it can be either domain-joined or in a workgroup. It includes new syntax and parameter options in order to run it remotely.
For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012 R2 and Windows Server 2012, see Changes to Adprep.exe.
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd464018(v=ws.10)
Please check this similar thread.
https://www.experts-exchange.com/questions/28593177/Upgrading-schema-to-2012-from-2003-DC.html
ASKER
I just noticed this:
https://blogs.technet.microsoft.com/askds/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers/
do you recommend (if possible) using a Windows 2008 as intermediate step?