Re: Move from Exchange 2000 to 2003

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

From: Steven Halsey [MSFT] (Stevhal_at_Online.Microsoft.com)
Date: 06/24/04


Date: Thu, 24 Jun 2004 10:48:23 -0700

Sorry, forgot about the front end issue.
Yes, you must upgrade the front end server first in the Admin Group.
So that leaves 2 options, a simple one and a complex one:

The simple one: Upgrade your existing Front End server to Exchange 2003, it
should work with no issues. You could try setting up a lab to test out for
any issues but I know there isn't always time or resources for this, so you
might just have to upgrade the Front End.

The complex one: If you are in Native Mode Exchange this should work
however it will leave you with some odd items after the migration.
If you are in mixed Mode Exchange you probably can't use this approach.
You could create a new Administrative Group for Exchange 2003, apply the
same delegate permissions as you had for the old Admin Group.
Install your new Hardware to this new Administration Group, and let the
routing Group be the old Routing Group For your old Administration Group.
Move All the Users, public Folders Etc to the new Exchange 2003 servers
Retire the Old Exchange 2000 Servers.

Now If you have a small number of routing Groups or good network (T1+)
between your routing groups You can create a new Routing Group in the New
Admin Group, move the servers to the New Routing Group and migrate all your
connectors in other routing groups to point to the new Routing Group, and
remove the old Routing Group and Admin Group (so long as it does not contain
the Public Folder Information, if it does contain the PF then I think you'll
have to keep the old ADmin Group and Routing Group and don't create a new
one.)

Or you could keep the old Admin Group Empty of servers, and let it host the
Routing Group. Which would be the less work, but leaves you potentially
with this odd Admin Group hanging out in your Organization (should have no
ill effects, just kinda weird containing only a Routing Group and no
servers).

-- 
Steven Halsey
Stevhal@online.microsoft.com
Microsoft Exchange
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"VMCspam" <anonymous@discussions.microsoft.com> wrote in message 
news:20e0601c459ef$269dfb40$a101280a@phx.gbl...
> We have an existing 2000 Front End Server.
> Unfortunately, when installing Exchange 2003 to new
> equipment, it recognizes the existing 2000 FE server and
> instructs us to upgrade that server first.  However, we
> don't want to upgrade the Exchange environment that is
> running on existing hardware and would rather install
> 2003 on only new equipment.  How can we get around this?
>
>
>>-----Original Message-----
>>Sounds like a great plan.  You can look at the
> Deployment tools and it will
>>give you some specific steps.
>>Otherwise installing Exchange 2003 on new servers and
> moving the mailboxes
>>and public folders over should work.
>>Follow this KB when you are looking to retire your old
> Exchange 2000 servers
>>http://support.microsoft.com/default.aspx?scid=kb;en-
> us;822931&Product=exch2003
>>
>>
>>-- 
>>Steven Halsey
>>Stevhal@online.microsoft.com
>>Microsoft Exchange
>>
>>Please do not send email directly to this alias.  This
> alias is for
>>newsgroup purposes only.
>>
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>
>>
>>
>>"vmcspam" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:2031901c45952$741e0010$a601280a@phx.gbl...
>>>I am having difficulty locating documentation / best
>>> pratices for moving from Exchange 2000 to Exchange
> 2003.
>>> We have new equipment in house to house the new
>>> environment.  Does anyone have any suggestions?  We
> were
>>> thinking about install Exchange 2003 to the new servers
>>> and into the same site, then manually moving the users
> to
>>> the new servers.
>>>
>>> Thanks!
>>
>>
>>.
>> 


Relevant Pages

  • Re: 3 E2k3 servers, 1 admin group - want seperate smtp connectors for
    ... If you have 3 physical sites with Exchange servers but they're all in the ... same Routing Group, Exchange sees them as being in one Site. ... Site - servers within the same Routing Group route messages directly to each ... the servers to the appropriate RG, and create SMTP Connectors in each RG. ...
    (microsoft.public.exchange.setup)
  • Re: Ex5.5 --> Ex2003 Migration questions
    ... servers while still in mixed mode. ... > Currently we have an Exchange 5.5 organization with four sites. ... > other sites and IMC for smtp connection). ... > And is it true that one Routing group will automatically built for every ...
    (microsoft.public.exchange.design)
  • Re: Routing Groups/Connectors
    ... Microsoft Exchange Server 2003 Transport and Routing Guide ... Now Setup - In the BridgeHead Server selection, I add added all 3 servers. ... them and move the servers into a single Routing Group. ... Routing Group Connector configuration). ...
    (microsoft.public.exchange.admin)
  • RE: Routing issues - 2 exchange 2003 servers
    ... >mail back and forth from the exchange 5.5 servers to the ... >Pacific's routing group when it got added didn't get ... >be created to communicate with the Chicago server?? ... This is normally not required as your two Exchange 5.5 servers should have ...
    (microsoft.public.exchange.connectivity)
  • Re: Globalevents error
    ... This is a mixed mode Exchange organization (both Exchange 2003 and ... We have three 5.5 servers remaining which we are in the process ... we have public folder connection agreements ... globalevents folder having the errors was a newly created admin group ...
    (microsoft.public.exchange.admin)