Upgrade to W2K3 AD with E2K3 already installed

From: Bob Williamson (Bob_at_Bscw.net)
Date: 07/07/04 

Date: Wed, 7 Jul 2004 08:32:48 -0700

I am running E2K3 on W2K with W2K AD (now thats a mouth full). I am
planning on upgrading my DCs to W2K3 in th next couple of weeks. NOTE: My
E2K3 server is not on a DC.

I have read numerous posts about upgrading my W2K DCs to W2K3 with the
"mangling" complications of Exchange and am a bit concerned. Anytime the
word mangling is used in reference to AD it concerns me to say the least

There are numerous references to Q325379. I have also been offered the
technique listed at the bottom of this post.

My question is, has anyone actually been through this? If so, how did it
go?

Thanks,
Bob

Alternative technique for DC upgrade

As you may know that the key point to adding a Windows Server 2003 DC to
Windows 2000 domain, you should run Adprep /foresetprep and /domainprep.

I suggest you refer to following article about upgrading:
325379 How to upgrade Windows 2000 domain controllers to Windows Server
2003 http://support.microsoft.com/default.aspx?scid=KB;EN-US;325379

After Windows Server 2003 DC is joined to Windows 2000 Domain, transfer
FSMO, Global Catalog to the Windows Server 2003.

For detailed steps, please refer to:
HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801
HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690
HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

Considering the Exchange issue, you should pay attention to following
potins:

1. Make sure that ALL Windows 2000 domain controllers are running SP3 or
later before you begin the upgrading process.
2. After you follow the steps above to run ADPREP /Forestprep and
/Domainprep, because forestprep will break some exchange schema, you should
fix Exchange server attributes.

For more information, please refer to:
314649 Windows Server 2003 adprep /forestprep Command Causes Mangled
Attributes http://support.microsoft.com/?id=314649

- On Exchange server 2000, re-run Exchange 2000 setup /Forestprep.
- Re-run Exchange 2000 setup /DomainPrep.
- Click Control Panel -> Add or Remove Programs.
- Select Microsoft Exchange, and click Change/Remove.
- Choose Reinstall under Action, and follow the wizard.

3. Before you migrate to Exchange server 2003, it's recommended that you
check the following articles first:

822178 Overview of Dependencies and Requirements for Exchange Server 2003
http://support.microsoft.com/?id=822178
822179 Overview of Operating System and Active Directory Requirements for
http://support.microsoft.com/?id=822179
822942 Considerations When You Upgrade to Exchange Server 2003
http://support.microsoft.com/?id=822942

4. Install Exchange 2003 on the new Windows 2003 domain controller, and
join the existing Exchange 2000 organization.

Note: It's highly recommended that you follow the steps in Exchange 2003
deployment tools. The wizard is very helpful and provides detailed steps on
how to install Exchange server 2003 in various scenarios. To use deployment
tools, run the setup program at the root folder of the Exchange 2003
installation CD.

Relevant Pages

  • Re: Upgrade to W2K3 AD with E2K3 already installed
    ... you would don't has problem because the mangled problem appear migrating AD ... > planning on upgrading my DCs to W2K3 in th next couple of weeks. ... Global Catalog to the Windows Server 2003. ... > Considering the Exchange issue, you should pay attention to following ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: Upgrading from 2000 Server w/ Exchange 5.5
    ... "I'm assuming that Exchange 2000 schema updates have not been applied to the ... your first step would be to get some hardware and install Windows Server ... test that DNS is correctly configured and is replicating ...
    (microsoft.public.windows.server.general)
  • RE: Migrating from NT to Win2K3 AD. Exchange 5.5 Considerations?
    ... Exchange 5.5 is supported in a Windows Server 2003 ... Windows Server 2003 environment. ...
    (microsoft.public.exchange.admin)
  • RE: Problem with creating email-enabled objects and SMTP addresses
    ... > An Exchange Server could not be found in the domain. ... > Windows Server 2003 SP1 ... > delegated as Exchange View Only Administration ...
    (microsoft.public.exchange.admin)
  • Re: migrating from windows 2000 to windows 2003 AD
    ... I will be downing my primary DC (all FSMO roles etc) and rejoing a W2K3 DC. ... > Exchange Server to Windows Server 2003 Domain, If I am off-base on that, ... > later before you begin the upgrading process. ...
    (microsoft.public.windows.server.migration)
Loading