Side-by-side Upgrade

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: ScottT (anonymous_at_discussions.microsoft.com)
Date: 02/13/04 

Date: Fri, 13 Feb 2004 13:45:56 -0800

Hello,

I have an NT 4.0 domain and plan to upgrade to Win2003
Active Directory. Do you see any problems with this plan:

1. Prevent all changes to SAM database.
2. Take one of my NT 4.0 BDCs offline.
3. Promote offline BDC to PDC.
4. Upgrade offline PDC to Win2003 AD.
5. Remove NT 4.0 PDC from network and insert Win2003 PDC.

Upgrading this way allows me to avoid long downtime of NT
4.0 PDC.

Do you forsee any problems with this plan?

Thanks,
ScottT

 

Relevant Pages

  • Re: NT to win2003 AD upgrade
    ... > I want to pull my BDC offline, promote it to PDC, upgrade it to 2003. ... please direct all replies ONLY to the Microsoft public newsgroup ...
    (microsoft.public.windows.server.active_directory)
  • RE: Migrate DNS from NT4 -> w2k3
    ... I think it is no way and no need to replicate DNS data manually like your ... Once you upgrade to domain 2003 and integrade DNS with AD, ... | The plan is: ... | - Promote it to PDC ...
    (microsoft.public.windows.server.migration)
  • Re: Migration from a single NT PDC to a new 2003 AD DC
    ... > currently a single NT PDC. ... So let me break down my plan: ... you are upgrading then it is wise to have at least one production BDC ... When you upgrade you must upgrade the PDC first as ...
    (microsoft.public.windows.server.migration)
  • Re: Migration from a single NT PDC to a new 2003 AD DC
    ... >> currently a single NT PDC. ... >> backup plan. ... > you are upgrading then it is wise to have at least one production BDC ... When you upgrade you must upgrade the PDC first as ...
    (microsoft.public.windows.server.migration)
  • RE: Retire PDC after upgrade
    ... you may not replication failure in the Event logs. ... | Thread-Topic: Retire PDC after upgrade ... | had the old PDC offline for about 2 weeks, and it looks like I'm done ...
    (microsoft.public.windows.server.migration)