Yep, the domains are not the
same as you might think because they have the same NetBIOS name (each domain
also has its own SID) The two domains with the same cannot co-exist next to each
using the same WINS infrastructure.
The procedure is the one Tom
describes below, but I would like to apply some safety precautions and a way to
have an upgraded domain with a clean installed W2K3 DC
STARTING RESULT: 1 WNT4 domain
with one DC (PDC)
* Add a clean installed BDC
(BDC1) to the WNT4 domain and sync domain (use a desktop or something like
that)(don't forget the HW reqs)
*
Add a clean installed BDC (BDC2) to the WNT4 domain and sync domain (use a
desktop or something like that)(don't forget the HW
reqs)
*
Promote BDC1 to PDC (the old PDC will automatically be demoted to BDC) and sync
domain
*
SHUTDOWN BDC2 as a safety precaution
*
Configure the new WNT4 PDC (BDC1) with NT4 emulation and "NT4 emulation
neutralization" (see http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q298713)
(if you have some w2k/wxp based clients)
*
Set up DNS on WNT4 PDC (BDC1) for W2K3 AD
domain
*
Upgrade the new WNT4 PDC (BDC1) to W2K3. The domain will be upgraded by
AD
*
Add the new installed W2K3 BOX (W2K3DC1) to the newly upgraded domain and
configure NT4 emulation and promote it to DC using
DCPROMO
*
Transfer the roles FSMO roles to the new installed W2K3 BOX (W2K3DC1) and assign
the BOX also as GC and configure DNS and transfer it from BDC1 (and setup also
WINS and DHCP if needed)
*
Demote the BDC1 to W2K3 member server and remove it from the the domain and do
some metadata cleanup is needed (http://support.microsoft.com/kb/216498)
*
Move resources from the old PDC to W2K3DC1
*
Remove the old PDC from the AD domain and cleanup
computeraccount
*
Remove the NT4 emulation from W2K3DC1
*
Increase domain and forest functional level
*
Voila----> ready
If everything went OK and there are no problem's, BDC2 is not needed
anymore as safety precaution to return to the WNT4 domain
END RESULT: 1 W2K3 domain with
one DC (containing all FSMOs), and with the GC role, DNS role (and WINS and DHCP
if needed)
This should do it. It is not limited to this list,
there's more to it (like OU structure, GPOs, Delegation,
etc.)
Don't forget: test, test, test, test, test, test, test,
test! and test!
Regards,
Jorge
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kern, Tom
Sent: Thursday, January 13, 2005 18:13
To: [email protected]
Subject: RE: [ActiveDir] Crazy question
i
think they are 2 different domains with the same name. they have no relation to
each other.
he
should run dcpromo and demote the dc, slap NT on the new server and make it a
bdc, then demote the old pdc and promote the new bdc and upgrade to win2k3 on
the new pdc.
-----Original Message-----
From: Gary Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 13, 2005 12:09 PM
To: [email protected]
Subject: [ActiveDir] Crazy questionI have been asked this from a friend of mine and wasn't sure of the outcome even though I have told him not to go ahead. I was just interested in the implications and whether it can be done.He has a customer with an existing NT4 domain one PDC that's it. He has bought a brand new box and installed W2K3 dcpromo'd the thing and set up users, thinking he could just add the box to the existing domain and everything would be okay to migrate the users and data over.I know this sounds pretty crazy, but it got me thinking what would the implications of doing this and what is the best procedure for him at this stage. If any.Gary
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
