Exchange 5.5 to Exchange 2003

From: CIRO (CIRO_at_discussions.microsoft.com)
Date: 02/23/05 

Date: Tue, 22 Feb 2005 16:27:02 -0800

This is my situation:
1 NT 4.0 SP6 - PDC
1 NT 4.0 SP6 - BDC + File Server + Printer Server
1 NT 4.0 SP6 - Exchange 5.5 Server + Proxy Server

I will migrate all to a new Active Directory Domain using the following steps:
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.
5.Promote the Windows Server 2003 to be a DC. The Active Directory service
imports the existing user accounts, groups, and other settings from the PDC.
6.Run for a test period.
7.Do a clean installation of Windows Server 2003 on the other new box, and
bring it online as an additional DC.
8.Transfer all Flexible Single-Master Operation (FSMO) roles to the new DC.
9.Verify all directory information has replicated.
10.Demote the first DC to a member server, and remove from the domain.

My idea is to:
a)Make one WIN2003 server the DC + SMTP Gateway (via Symantec prod.) +
Proxy (via Symantec prod.)
b)Make another WIN2003 server the Exchange 2003 server + File Server +
Print server.
I was referred to this newsgroup regarding the following:
"I notice you also want to do an Exchange migration. Please post it in the
microsoft.public.exchange.setup newsgroup since they are the experts in
Exchange and will provide the most accurate information on this issue.
Best regards,
Frances He - Microsoft Online Partner Support"

QUESTION
1) Are there any issues using either the "move the mailboxes" or the "swing
upgrade" methods when migrating from an Exch. 5.5 to an Exch. 2003 after the
above mentioned scenario is fulfilled?
2) Any specific I would actually want to do before fulfilling the above
mentioned scenario?

Thanks, in advance!

Relevant Pages

  • Re: Old Win NT domain to W3K AD setup - where to start?
    ... This would create a new domain on the Win 2k3 server. ... In Win 2k or Win 2k3 there is no such thing as a BDC, ... You don't demote a NT 4.0 PDC to BDC, you promote a NT 4.0 BDC to PDC and ... How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003-Based ...
    (microsoft.public.windows.server.setup)
  • RE: please help, a complex migration/upgrade scenario
    ... Windows Server 2003 cannot be a BDC in a WinNT 4 domain. ... the NT4 BDC to PDC, then the original PDC will be demote to BDC ... Since Exchange 5.5 is running on the WinNT BDC, ...
    (microsoft.public.windows.server.migration)
  • RE: Changing from Windows NT4.0 pdc server to new windows 2003 server
    ... It is OK to upgrade NT PDC to win2k3 and keep other BDCs since win2k3 can ... The Active Directory service imports the existing ... Migrating Windows NT Server 4.0 Domains to Windows Server 2003 ...
    (microsoft.public.windows.server.migration)
  • RE: Win NT to Win2k3 Upgrade
    ... ok followed the route where i made a bdc then upgraded to pdc. ... It launches but it does not give me the option to upgrade. ... > 5.Use the Windows Server 2003 Active Directory wizard to turn on the Active ...
    (microsoft.public.windows.server.migration)
  • Re: Migration to SBS 2003
    ... the PDC to a BDC. ... >Upgrade the new PDC to Windows Server 2003. ... turn on the Active Directory service. ... Active Directory domain controller. ...
    (microsoft.public.backoffice.smallbiz2000)