RE: 2 x DC, 2 sites and NT4 servers same domain HELP

Hello,

Thanks for your post.

I understand you want to upgrade NT PDC and BDC to 2k3. If I have
misunderstood, please feel free to let me know.

Based on my experience, you are right that first upgrade PDC to 2k3 and
then BDC. Between the sites, we recommend you using AD integrated DNS.
This make the Windows 2k3 domain between the two sites maintain a same DNS
database. It would perform a synchronization every a period of time.
Additional, the additional Windows 2k3 DC at the remote site would have a
replica AD database with the Windows 2k3 PDC. So all the user and computer
account information reside in the same AD database.

For your current situation, we highly recommend a "not in place" upgrade
path for security purpose.

As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend. :)

Performing a "not in place" upgrade
======================

1.Install NT 4.0 BDC on the new box.

2.Promote the BDC to the PDC, which demotes the PDC to a BDC.

3.Do a full backup of the former PDC and remove it from the
network.

4.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the
following KB:

325857 How To Expand the Boot Partition During a Windows Server
2003 Upgrade
http://support.microsoft.com/?id=325857

5.Use the Windows Server 2003 Active Directory wizard to turn on
the Active Directory service. The Active Directory service imports the
existing user accounts, groups, and other settings from the PDC.

How to Verify an Active Directory Installation
http://support.microsoft.com/default.aspx?scid=kb;en-us;298143

6.Run for a test period.

7.If desired you can do a clean installation of Windows Server 2003
on the former PDC, and bring it online as an Active Directory domain
controller.

8.Transfer all Flexible Single-Master Operation (FSMO) roles to the
new Windows Server 2003 domain controller.

9.Verify all directory information has replicated.

Verify successful replication to a domain controller

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Opera
tions/00e7f86b-ccd3-4cb8-9a01-bf747241b500.mspx

10.Demote the first domain controller to a member server, and
remove from the domain.

Then perform the same steps above to upgrade the BDC in site 2. Meanwhile,
I suggest you designate the BDC to be global catalog servers so that the
BDC can perform the GC role in site 2. You can designate other domain
controllers to be global catalog servers if they are needed. For more info
related GC, please refer to:

Domain Controller Roles
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechR
ef/c7ea7ed1-4241-4794-9ce8-471da6a3a727.mspx

I suggest you check the following KB articles to migrate to Win2k3 from NT4:

Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
Directory
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4domt
oad.mspx

Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx

About your concern of that after having setup the first DC on a new server,
how do you then join the second DC and NT servers to the domain, please
don't worry about it.

You can join the second DC just as add an additional server in domain as
following:

Create an additional domain controller
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serve
rHelp/4aae5014-fbce-42dc-b5f7-e1dde3072f38.mspx

You can add NT servers to win2k3 domain. However, we do not recommend you
doing so because there are many functions and GPOs in win2k3 domain cannot
be used and applied on them.

HTH!

Thanks & Regards

Amanda Wang [MSFT]

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================================

--------------------
>Thread-Topic: 2 x DC, 2 sites and NT4 servers same domain HELP
>thread-index: AcVXjZP9GqjW4ywjSLiGDyaoZwEM7w==
>X-WBNR-Posting-Host: 82.68.91.165
>From: =?Utf-8?B?bWFobWFk?= <mahmad@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: 2 x DC, 2 sites and NT4 servers same domain HELP
>Date: Fri, 13 May 2005 00:30:03 -0700
>Lines: 15
>Message-ID: <9B95562D-08AD-4AFD-9445-796D556F198E@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10157
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Hi,
>
>We are currently running NT PDC and member server at site one, at site two
>we have a BDC. The connection for the two sites is via VPN ADSL.
>
>So what i would like to know is can i setup both the new Win 03 servers a
>DC's with AD, each site will do their own DNS and DHCP, but have the same
>users and computers db and after having setup the first DC on a new
server,
>how do i then join the second and DC and NT servers to the domain.
>
>Thanks for all your help
>
>Mo
>
>
>

.

Relevant Pages

  • NT 4.0 PDC upgrade to Win Server 2003 DC but needs to be rebuilt
    ... If you are truly going to upgrade, ... the new box setup as a BDC. ... after a replication take the old PDC offline ... >Windows Server 2003. ...
    (microsoft.public.windows.server.migration)
  • Re: This Seemed too easy
    ... yes in place upgrade. ... promoted it to pdc, then threw the 2003 CD in the new box, and did the ... > Windows Server MVP ... >> besides not being about to promote the bdc to a pdc, ...
    (microsoft.public.windows.server.migration)
  • Re: Windows NT4 to 2003 In-place server upgrade issues
    ... machine as the PDC ... Run 2003 setup and choose upgrade ... Take at least one BDC Offline (In case of UPGRADE FAILURE you always can ... Add new server as NT4.0 BDC ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT4 Server to Windows 2003 Server
    ... > 2 If NOT, can I format and install NT on the new server, make it a BDC on ... > the domain, then take it off line and upgrade it to a PDC, THEN upgrade to ... Promote to PDC while it is online with the existing PDC. ... > server to replace it. ...
    (microsoft.public.windows.server.migration)
  • RE: NT4.0 to 2003
    ... I'd give up on the idea of installing NT on the new server unless ... Promote it to the PDC ... Upgrade the temp PDC to Server 2003 and have it be the first AD Domain ... Assuming you go the round about way I'm suggesting you won't be installing ...
    (microsoft.public.windows.server.migration)