Re: Exchange 5.5 to 2003

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

From: Mark Arnold [MVP] (mark_at_mvps.org)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 17:17:39 +0000

Yes, I've just re-read the post about 1 server rather than simply 1
domain.
OK.
Get a temporary workstation class machine and introduce it as an NT4
BDC. Promote it to PDC and upgrade it to Windows 2003. Voila, one AD
domain in mixed mode with Exchange 5.5 on the BDC.

Introduce your new Exchange server and make it a member server.
Configure the ADC and connection agreements.
Do the Exchange migration ad you have already read.

Final steps are the decision on whether or not to format the (now) BDC
and rebuild as a W2K3 DC (is it supported HCL wise etc?) or whether to
upgrade the current W2K3 member server to a DC and then transfer all
the FSMO roles.

What are your constraints? Can you have two boxes or do you need to go
with one box only?

On Mon, 14 Feb 2005 08:43:07 -0800, "Brandon Hatok"
<BrandonHatok@discussions.microsoft.com> wrote:

>Thanks for the reply Mark. I thought an in-place upgrade from Exchange 5.5 to
>2003 was not supported (KB Article ID: 822942). Would I have to go to
>Exchange 2000 first and then to 2003? Do you know of any whitepapers that
>describe this process?
>
>Thanks Again,
>Brandon
>
>"Mark Arnold [MVP]" wrote:
>
>> On Mon, 14 Feb 2005 07:35:03 -0800, "Brandon Hatok"
>> <BrandonHatok@discussions.microsoft.com> wrote:
>>
>> >We have 1 server running NT4.0 domain with Exchange 5.5. Looking to upgrade
>> >to 2003. This is what I have read and plan to do:
>> >Add a new 2003 machine to network.
>> >Install AD to JOIN THE NT4.0 DOMAIN
>> >Use AD Migration Tool to clone accounts from 4.0 to AD.
>> >Install ADC to sync. AD and NT4.0 domain
>> >Forestprep & Domainprep 2k3 machine
>> >Install Exchange 2k3
>> >Move mailboxes from NT4 to 2k3 machine
>> >Move public folders from NT4 to 2k3
>> >Remove SRS
>> >Remove Exchange 5.5
>> >
>> >Has anyone been through this before and have any thoughts of what I need to
>> >be aware of?
>> >
>> >Thanks
>>
>> Any reason you don't simply want to upgrade the NT4 domain to 2003?
>> You can upgrade NT4 to 2003 (on the PDC) and then introduce a new DC,
>> transfer the FSMO roles and retire the originally upgraded box, either
>> to decomission it or to rebuild it to a clean state?
>>

Relevant Pages

  • Re: windows 2003 adv server
    ... > the BDC and upgrade to PDC.Then Upgrade the PDC agin to ... > windows 2003 server DC. ... >>running a DC with Exchange? ...
    (microsoft.public.win2000.advanced_server)
  • Re: Splitting Domain Controller & Exchange 2003 from a single server
    ... watch out for this that you keep the "BDC" (Running both Exchange and AD) ... It is also a GC, EXCHANGE 2003 server, File Server, VPN ... XENA - This is just a second domain controller for redundancy. ...
    (microsoft.public.win2000.active_directory)
  • RE: NT4-->W2K3 Upgrade, Domain Change Revisted
    ... The domain name can be changed in Windows NT4. ... Stop all BackOffice services such as Exchange, SQL Server, and IIS. ... is necessary for each BDC to successfully change to the new domain name. ... If the name can be changed during upgrade it would save ...
    (microsoft.public.windows.server.migration)
  • Re: FSMO roles and BDC.
    ... It isn't a BDC unless it is running NT rather than Win2000+. ... I know I was using wrong terminology but the DC that has the FSMO roles is a win2k server and the other DC is win2k server and it also has exchange2003. ... To reiterate what herb said, Exchange on a DC, while supported, is NOT considered a best practice. ... Now I've seen some people recommend no more than one GC and others recommend every DC is a GC. ...
    (microsoft.public.windows.server.general)
  • RE: 2 x DC, 2 sites and NT4 servers same domain HELP
    ... I understand you want to upgrade NT PDC and BDC to 2k3. ... Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active ...
    (microsoft.public.windows.server.migration)