Re: Upgrading from Ex5.5 to Ex2003

  • From: Tee Darling <tee.darling77@xxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 18 Feb 2005 08:41:24 -0500

Your best bet would be to do the Swing Upgrade as you have stated,
where by you setup and configure Exchange 2003 in and existing site
and then move the mailboxes from Exchange 5.5 to the Exch Server 2003.

But before you move the mailboxes from the 5.5 server, make sure that
you have Exchange Server 2003 SP1 installed and all the hotfixes after
SP1 came out for Exchange Server 2003. You should be alright after


On Fri, 18 Feb 2005 11:38:49 +0100, Uchay <uchay@xxxxxxxxxxx> wrote:
> Hello Everyone,
> My company is about to upgrade our Exchange server but the upgrade method is
> giving us headaches. I'll like some advice regarding which method would be
> less problematic for us. A month ago we tried an in-place upgrade of Ex5.5
> to Ex2000 which failed forcing us to rollback to Ex5.5. Based on advice
> received we have decided to upgrade directly to Ex2003 bypassing Ex2000.
> In-Place upgrade - we upgrade the existing 5.5 server to Ex2003.
> or
> Swing Upgrade - we deploy an Ex2003 server into the existing site, and move
> mailboxes from the Ex5.5 to it; upgrade the old Ex5.5 server and move the
> mailboxes back.
> My organization has a single site; double server configuration with just
> over 2000 mailboxes and we are running a mixed-mode Windows domain.
> Help please.------------------------------------------------------
> List Archives:
> Exchange Newsletters:
> Exchange FAQ:
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking:
> Leading Network Software Directory:
> No.1 ISA Server Resource Site:
> Windows Security Resource Site:
> Network Security Library:
> Windows 2000/NT Fax Solutions:
> ------------------------------------------------------
> You are currently subscribed to this Discussion List as:
> Tee.Darling77@xxxxxxxxx
> To unsubscribe visit
> Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: