<div>
yes. join, and it will be just another DC in the environment.
</div>


IT Administrator

John Crawford

<div>
* &quot;<i>2003DC joining existing 2000 domain</i>&quot;: no, you can <b>not</b> join a DC to another domain.<br />
* You can install the 2003 and join it as <b>member</b> server to the 2000 AD.<br />
* If you want to promote the 2003 to a DC, you <b>have</b> to prepare the AD for the 2003 DC before being able to promote.<br />

<pre><code class="code-1 nolinks" id="code-20-42713407-1"><span>adprep.exe /forestprep</span>
<span>adprep.exe /domainprep</span>
</code></pre>
That said, and you probably know that this has to be asked: why do you want &nbsp;to install a 15 year old OS that's long out of support? Even 2008R2 will be out of extended support in a little over 1 year. Mainstream support of Server 2012R2 has already ended.
</div>


COG Lead Engineer

Shaun Vermaak

<div>
If the person is still running a windows 2000 based AD, 2003 is an update that might meet the vendor requirements ....... of supported platform.<br />
there are no updates available for 2003 unless the SPs were previously obtained, or exist in a WSUS server ....... If this is a rapid transition from 2000 through to 2012.<br />
2012 can be added to a 2003 AD domain. do not recall whether 2008 can be added to a 2000....
</div>


<div>
oBdA<br />
<br />
Yes ok, that was my intent, for the fresh install 2003 server to be a member, then run in parallels and promot after moving databases.
</div>


<div>
oBdA<br />
<br />
To answer, I'm assuming 2008 and later <b>cannot</b> be joined as member of a 2000 DC.
</div>


<div>
arnold<br />
<br />
I have no intention of trying to upgrade a virtual machine or even bare metal for that matter. What I want is to join 2003 (or 2008 12 etc) as a member in parallel. Then move my databases to cluster or NAS, then promote 2003 to valid DC status so it can replicate with 2000, then I can get ride of the 2000 DC's on the network.
</div>


<div>
Not speaking from personal experience here, but Microsoft says it's possible even for Server 2008 R2:<br />
Prepare a Windows 2000 or Windows Server 2003 Domain for a Domain Controller That Runs Windows Server 2008 or Windows Server 2008 R2<br />
<a href="https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754670(v%3dws.10)" rel="ugc">https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754670(v%3dws.10)</a>
</div>


<div>
I am assuming the adprep command line procedures update active directory database files on the Master Controller 2000DC (meaning insert 2003 cd or DVD into master controller and execute adprep commands) so as to be compatible with 2003 server.
</div>


<div>
No, it updates the AD Schema to support the newer versions.
</div>


<div>
Gecko odds, &nbsp;a me,ber server can be added to 2000 2003, 2008, 2012,2016<br />
<br />
The issue deals with based on the AD/Forest version and which OS version can function as a DC,<br />
Often the DCs can be two versions out, 2000 2093,2008<br />
2003, 2008,2012.<br />
<br />
I stil do not understand what you are after, a cluster requires at least two .......<br />
<br />
<br />
The DBs might not need to be touched for DC server ...
</div>


<div>
As I said in prior comment, I have a 2000DC I want to retire, I do not want to upgrade the virtual machine. What I want is to see if I can add a 2003 server as a <b>Member</b>, then move accounting databases off the 2000 DC and put on another server, NAS, cluster whatever, replicate at least once maybe twice, then promote the 2003 server to Master DC (I think this is the vernacular) then decommission the 2000DC.<br />
<br />
The manual in the box and Microsoft articles keep pushing to upgrade the 2000 DC, &nbsp;If this technology is designed to be fault tolerant and allow other member DC, then I should be able to do it this way.
</div>


<div>
You are transitioning from One to he other, <br />
One way us to upgrade in place the existing which you seem to interpret any comment as a suggestion to do just that.<br />
The other is to create a new VM running Windows (2003,2008) if you install 2008, you need to add the file services for Windows 2003 (ntfrs which is needed for sysvol/netlogon replication)<br />
Add it as another dc. Allow the replication to complete, dcdiag, repadmin once the new has all the info, and the replication is complete, you can transfer all the roles from the old DC, to the new DC. You would need to make sure all existing member servers point their DNS records to the new server as prinary.<br />
At this point, the old DC can be retired (first, power off the VM) to make sure the environment operates ......<br />
You can then decom(demote the old DC to a member server)<br />
<br />
You can now elevate the new ad/forest level to the highest level of that os 2003/2008 which ever is higher.<br />
Transition the sysvol from ntfrs to dfs-r for future simpler transition.
</div>


<div>
arnold<br />
<br />
Thanks, actually you suggested upgrading in place twice! Getting Started Windows Server 2003 Enterprise Manual: &nbsp;Chapters 3 - Getting ready for an upgrade; AND Chapter 4 - &nbsp;Running Setup for an Upgrade, you have <b>pages and pages</b> of text telling, instructing to upgrade a in-place system. Exactly what I don't need. <br />
<br />
<b>Some Good News:</b> I do see in chapter 3 &quot;Preparing for Upgrades in a Domain Containing Windows 2000 Domain Controller: <b>Second Bullet Point Reads:</b> Install Windows Server 2003, Enterprise Edition, on a <b>member server</b> in the domain and start the active directory installation wizard.... &nbsp;Im doing that now too see what options are available to become a member...
</div>


<div>
oBdA<br />
<br />
Thanks for being clear, Ok so during installation I DO NOT join WORKGROUP, but become a member of existing domain, right?<br />
<br />
Then as you said, command line executions as required. <br />
<br />
I going through this step by step, I'm mostly the &quot;put out the fire&quot; guy so I run cable, virtualize servers, install video securitiy, anything but I want to know and document active directory differences from 2000 all the way to 16.
</div>


<div>
Even if you &quot;join&quot; a workgroup during setup, you can always join it to the domain later. Domain join is not bound to the OS installation.
</div>


<div>
<div class="content wysiwyg-content">
I have a small windows 2000 domain controller and want to install 2003 server (new Virtual Box) to eventually replace old VM. I do not (as manuals explain) want to upgrade 2000 DC, can't I just add the 2003 server to the existing 2000 domain, run both in parallel, then promote 2003 and decommission 2000 DC?<br />
<br />
Options I see:<br />
1. Join an existing domain (2003DC joining existing 2000 domain)<br />
2. Create a new Child Domain, new Domain Tree, new forest (This does not look like what I want)
</div>
</div>


I have a small windows 2000 domain controller and want to install 2003 server (new Virtual Box) to eventually replace old VM. I do not (as manuals explain) want to upgrade 2000 DC, can't I just add the 2003 server to the existing 2000 domain, run both in parallel, then promote 2003 and decommission 2000 DC?

Options I see:
1. Join an existing domain (2003DC joining existing 2000 domain)
2. Create a new Child Domain, new Domain Tree, new forest (This does not look like what I want)

Adding (Not upgrade 2000DC) 2003 Server is existing 2000 domain.

Installation is the act of making a computer program program ready for execution. Because the process varies programs often come with a specialized program responsible for doing whatever is needed for their installation. Installation may be part of a larger software deployment process. Cross platform installer builders that produce installers for Windows, Mac OS X and Linux include InstallAnywhere, InstallBuilder and Install4J. Installers for Microsoft Windows include Windows Installer, InstallShield, and Wise Installation Studio; free installer-authoring tools include NSIS, IzPack, Clickteam, InnoSetup, InstallSimple and WiX. Mac OS X includes Installer, and also includes a separate software updating application.

Installation

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.