Exchange hardware migration questions

I want to migrate a stand alone exchange server to new hardware. After
reviewing the options all indications are that Iâ??m going to use the â??swingâ??
technique described in KB264879. Although in my case I have a new piece of
hardware that I want to migrate the old 2000 server too the new 2000
hardware. My plan is to join the new hardware to the existing domain,
install exchange 2000, rehome the pertinent services (OAB, RUS) then use ADUC
to do mailbox moves to the new server (100 accounts). After which time I will
change the MX record to point to the new servers IP address uninstall the old
exchange and unjoin it from the domain. I have two questions pertaining to
this plan, one being is this the best way to attempt this task?? (Front end
back end set up is not an option due to licensing.) Second how should I
handle OWA?? The whole swing thing seems very straight forward, but OWA
isnâ??t addressed?? Iâ??m relatively new to exchange and have worked mostly with
large front end back end setups where adding a new server and moving
mailboxes is pretty easy and seamless to the clients. Any suggestions or
comments would be appreciated!

Mark
Fri Sep 23 12:59:44 CDT 2005

On Fri, 23 Sep 2005 10:16:02 -0700, Padraig25
<Padraig25@discussions.microsoft.com> wrote:

>I want to migrate a stand alone exchange server to new hardware. After
>reviewing the options all indications are that I?m going to use the ?swing?
>technique described in KB264879. Although in my case I have a new piece of
>hardware that I want to migrate the old 2000 server too the new 2000
>hardware. My plan is to join the new hardware to the existing domain,
>install exchange 2000, rehome the pertinent services (OAB, RUS) then use ADUC
>to do mailbox moves to the new server (100 accounts). After which time I will
>change the MX record to point to the new servers IP address uninstall the old
>exchange and unjoin it from the domain. I have two questions pertaining to
>this plan, one being is this the best way to attempt this task?? (Front end
>back end set up is not an option due to licensing.) Second how should I
>handle OWA?? The whole swing thing seems very straight forward, but OWA
>isn?t addressed?? I?m relatively new to exchange and have worked mostly with
>large front end back end setups where adding a new server and moving
>mailboxes is pretty easy and seamless to the clients. Any suggestions or
>comments would be appreciated!

You seem to have it all pretty much to pat. Your safest (legaly
speaking) option is to create another URL to the new box and then tell
the users the new one as you do the moves.

I couldn't condone it and don't suggest it as a formal solution, but
you could always put an FE up for a couple of days as you do the move
and take it down later. I don't suppose that anyone would complain
since your swing method means that you have two servers running under
one server licence; you'd get no more time in jail for running three
under one than you would for two under one.

Do your move swiftly I suppose!

Ed
Fri Sep 23 15:07:51 CDT 2005

Consider upgrading to Exchange 2003 instead to save an upgrade and
migration.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:cbg8j1dmfc21murkdo270ghllolpfvqkjl@4ax.com...
> On Fri, 23 Sep 2005 10:16:02 -0700, Padraig25
> <Padraig25@discussions.microsoft.com> wrote:
>
>>I want to migrate a stand alone exchange server to new hardware. After
>>reviewing the options all indications are that I'm going to use the
>>"swing"
>>technique described in KB264879. Although in my case I have a new piece
>>of
>>hardware that I want to migrate the old 2000 server too the new 2000
>>hardware. My plan is to join the new hardware to the existing domain,
>>install exchange 2000, rehome the pertinent services (OAB, RUS) then use
>>ADUC
>>to do mailbox moves to the new server (100 accounts). After which time I
>>will
>>change the MX record to point to the new servers IP address uninstall the
>>old
>>exchange and unjoin it from the domain. I have two questions pertaining
>>to
>>this plan, one being is this the best way to attempt this task?? (Front
>>end
>>back end set up is not an option due to licensing.) Second how should I
>>handle OWA?? The whole swing thing seems very straight forward, but OWA
>>isn't addressed?? I'm relatively new to exchange and have worked mostly
>>with
>>large front end back end setups where adding a new server and moving
>>mailboxes is pretty easy and seamless to the clients. Any suggestions or
>>comments would be appreciated!
>
> You seem to have it all pretty much to pat. Your safest (legaly
> speaking) option is to create another URL to the new box and then tell
> the users the new one as you do the moves.
>
> I couldn't condone it and don't suggest it as a formal solution, but
> you could always put an FE up for a couple of days as you do the move
> and take it down later. I don't suppose that anyone would complain
> since your swing method means that you have two servers running under
> one server licence; you'd get no more time in jail for running three
> under one than you would for two under one.
>
> Do your move swiftly I suppose!