Moving Exchange2003 to New Hardware

KB 822945 (and/or its in TechNet) describes exactly what I'd like to do to
implement an upgraded server hardware for a client's Exchanage 2003
Enterprise system.

Three questions:

1. The article says "to move Exchange 2003 to a new computer and keep the
same server name, the new computer must have the same operating system
installed as the original computer."

The existing hardware runs Windows Server 2003 Standard SP1; the new
hardware has Windows Server 2003 Enterprise SP1 (in order to take advantage
of more than 4GB RAM). Are those considered the same or different operating
systems for the purpose of the Exchange move procedure?

2. Given that this is the only Exchange server in the organization, there's
no Site Replication Service running and the backup/restore of the Sire
Replication Service database can be ignored, correct?

3. An alternative to the KB822945 procedure is to load Exchange as a 2nd
server in same site, then move mailboxes, leave the first one up for a week
or so, and then remove Exchange from the old server. We definitely don't
want to have to touch Outlook profiles on all clients. But Outlook should
self-adjust as long as Exchange is running on the 1st server, correct?
Would would make this a better option?

Thanks,
DD

Ricardo
Thu Jun 08 11:06:02 CDT 2006



"DukieDallas" wrote:

> KB 822945 (and/or its in TechNet) describes exactly what I'd like to do to
> implement an upgraded server hardware for a client's Exchanage 2003
> Enterprise system.
>
> Three questions:
>
> 1. The article says "to move Exchange 2003 to a new computer and keep the
> same server name, the new computer must have the same operating system
> installed as the original computer."
>
> The existing hardware runs Windows Server 2003 Standard SP1; the new
> hardware has Windows Server 2003 Enterprise SP1 (in order to take advantage
> of more than 4GB RAM). Are those considered the same or different operating
> systems for the purpose of the Exchange move procedure?
>
> 2. Given that this is the only Exchange server in the organization, there's
> no Site Replication Service running and the backup/restore of the Sire
> Replication Service database can be ignored, correct?
>
> 3. An alternative to the KB822945 procedure is to load Exchange as a 2nd
> server in same site, then move mailboxes, leave the first one up for a week
> or so, and then remove Exchange from the old server. We definitely don't
> want to have to touch Outlook profiles on all clients. But Outlook should
> self-adjust as long as Exchange is running on the 1st server, correct?
> Would would make this a better option?
>
> Thanks,
> DD
>

Not sure, try these people:

http://www.synesisit.com/Prod/static/migration.jsp

Cheers

Andy
Thu Jun 08 11:47:57 CDT 2006

On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
<Ricardo@discussions.microsoft.com> wrote:

>
>
>"DukieDallas" wrote:
>
>> KB 822945 (and/or its in TechNet) describes exactly what I'd like to do to
>> implement an upgraded server hardware for a client's Exchanage 2003
>> Enterprise system.
>>
>> Three questions:
>>
>> 1. The article says "to move Exchange 2003 to a new computer and keep the
>> same server name, the new computer must have the same operating system
>> installed as the original computer."
>>
>> The existing hardware runs Windows Server 2003 Standard SP1; the new
>> hardware has Windows Server 2003 Enterprise SP1 (in order to take advantage
>> of more than 4GB RAM). Are those considered the same or different operating
>> systems for the purpose of the Exchange move procedure?
>>
>> 2. Given that this is the only Exchange server in the organization, there's
>> no Site Replication Service running and the backup/restore of the Sire
>> Replication Service database can be ignored, correct?
>>
>> 3. An alternative to the KB822945 procedure is to load Exchange as a 2nd
>> server in same site, then move mailboxes, leave the first one up for a week
>> or so, and then remove Exchange from the old server. We definitely don't
>> want to have to touch Outlook profiles on all clients. But Outlook should
>> self-adjust as long as Exchange is running on the 1st server, correct?
>> Would would make this a better option?
>>
>> Thanks,
>> DD
>>
>
>Not sure, try these people:
>
>http://www.synesisit.com/Prod/static/migration.jsp
>
>Cheers

Are you going to post this for every question?

DukieDallas
Thu Jun 08 12:21:10 CDT 2006


"Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in message
news:65lg82h93ltcoqn57c2lfng0glkq3ps83s@4ax.com...
> On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
> <Ricardo@discussions.microsoft.com> wrote:
>
<snipped>
>>
>>Not sure, try these people:
>>
>>http://www.synesisit.com/Prod/static/migration.jsp
>>
>>Cheers
>
> Are you going to post this for every question?

OK...but does anyone have answers or opinions on the questions?

DD

Eric
Thu Jun 08 14:22:43 CDT 2006

Hi Dukie,

Both options are valid when you are attempting to move Exchange data to a
new server. However, I would probably recommend the second option where you
would bring up a second Exchange server and move data to it. This limits
the amount of downtime in the environment since you do not have to take the
original server offline for any time. If you move mailboxes using the Move
Mailbox wizard (Exchange Tasks->Move Mailbox) then you will not have to do
anything with the existing user's profile as long as the original server is
online. The profile will get updated when the user attempts to open their
mailbox - it will first attempt to connect to the old server but will get
redirected to the new server and anytime after that point it will continue
to go to the new server. This redirection will not work if the old server
is offline, that's why it's important to keep the old server up a week or so
to allow your users to log into their mailbox. Once you're ready to
decommission the old server, follow this KB:

822931 How to remove the first Exchange Server 2003 computer from the
administrative group
http://support.microsoft.com/default.aspx?scid=kb;EN-US;822931

Hope this helps!
--
Eric Tam, MCSE, MCSA
Microsoft Exchange Support

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.
"DukieDallas" <rangerlax@sbcglobal.net> wrote in message
news:uEwZw$xiGHA.4512@TK2MSFTNGP02.phx.gbl...
>
> "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in
> message news:65lg82h93ltcoqn57c2lfng0glkq3ps83s@4ax.com...
>> On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
>> <Ricardo@discussions.microsoft.com> wrote:
>>
> <snipped>
>>>
>>>Not sure, try these people:
>>>
>>>http://www.synesisit.com/Prod/static/migration.jsp
>>>
>>>Cheers
>>
>> Are you going to post this for every question?
>
> OK...but does anyone have answers or opinions on the questions?
>
> DD
>
>

DukieDallas
Thu Jun 08 15:19:06 CDT 2006

Thank you, Eric. I was leaning that way anyway.

Out of curiosity, when you say "both options are valid," were you including
an answer to my question #1 - whether Svr2003 Standard and Svr2003
Enterprise would be considered the same operating system for the purposes of
the KB 822945 procedure?

Thank you for the advice.

DD

"Eric Tam [MSFT]" <ericta@online.microsoft.com> wrote in message
news:%23zqyrDziGHA.1260@TK2MSFTNGP05.phx.gbl...
> Hi Dukie,
>
> Both options are valid when you are attempting to move Exchange data to a
> new server. However, I would probably recommend the second option where
> you would bring up a second Exchange server and move data to it. This
> limits the amount of downtime in the environment since you do not have to
> take the original server offline for any time. If you move mailboxes
> using the Move Mailbox wizard (Exchange Tasks->Move Mailbox) then you will
> not have to do anything with the existing user's profile as long as the
> original server is online. The profile will get updated when the user
> attempts to open their mailbox - it will first attempt to connect to the
> old server but will get redirected to the new server and anytime after
> that point it will continue to go to the new server. This redirection
> will not work if the old server is offline, that's why it's important to
> keep the old server up a week or so to allow your users to log into their
> mailbox. Once you're ready to decommission the old server, follow this
> KB:
>
> 822931 How to remove the first Exchange Server 2003 computer from the
> administrative group
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;822931
>
> Hope this helps!
> --
> Eric Tam, MCSE, MCSA
> Microsoft Exchange Support
>
> 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.
> "DukieDallas" <rangerlax@sbcglobal.net> wrote in message
> news:uEwZw$xiGHA.4512@TK2MSFTNGP02.phx.gbl...
>>
>> "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in
>> message news:65lg82h93ltcoqn57c2lfng0glkq3ps83s@4ax.com...
>>> On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
>>> <Ricardo@discussions.microsoft.com> wrote:
>>>
>> <snipped>
>>>>
>>>>Not sure, try these people:
>>>>
>>>>http://www.synesisit.com/Prod/static/migration.jsp
>>>>
>>>>Cheers
>>>
>>> Are you going to post this for every question?
>>
>> OK...but does anyone have answers or opinions on the questions?
>>
>> DD
>>
>>
>
>

Eric
Sat Jun 10 15:43:24 CDT 2006

That should be okay, especially since we would move from Std -> Ent version
of the same OS.

--
Eric Tam, MCSE, MCSA
Microsoft Exchange Support

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.
"DukieDallas" <rangerlax@sbcglobal.net> wrote in message
news:OO5FLjziGHA.4284@TK2MSFTNGP05.phx.gbl...
> Thank you, Eric. I was leaning that way anyway.
>
> Out of curiosity, when you say "both options are valid," were you
> including an answer to my question #1 - whether Svr2003 Standard and
> Svr2003 Enterprise would be considered the same operating system for the
> purposes of the KB 822945 procedure?
>
> Thank you for the advice.
>
> DD
>
> "Eric Tam [MSFT]" <ericta@online.microsoft.com> wrote in message
> news:%23zqyrDziGHA.1260@TK2MSFTNGP05.phx.gbl...
>> Hi Dukie,
>>
>> Both options are valid when you are attempting to move Exchange data to a
>> new server. However, I would probably recommend the second option where
>> you would bring up a second Exchange server and move data to it. This
>> limits the amount of downtime in the environment since you do not have to
>> take the original server offline for any time. If you move mailboxes
>> using the Move Mailbox wizard (Exchange Tasks->Move Mailbox) then you
>> will not have to do anything with the existing user's profile as long as
>> the original server is online. The profile will get updated when the
>> user attempts to open their mailbox - it will first attempt to connect to
>> the old server but will get redirected to the new server and anytime
>> after that point it will continue to go to the new server. This
>> redirection will not work if the old server is offline, that's why it's
>> important to keep the old server up a week or so to allow your users to
>> log into their mailbox. Once you're ready to decommission the old
>> server, follow this KB:
>>
>> 822931 How to remove the first Exchange Server 2003 computer from the
>> administrative group
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;822931
>>
>> Hope this helps!
>> --
>> Eric Tam, MCSE, MCSA
>> Microsoft Exchange Support
>>
>> 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.
>> "DukieDallas" <rangerlax@sbcglobal.net> wrote in message
>> news:uEwZw$xiGHA.4512@TK2MSFTNGP02.phx.gbl...
>>>
>>> "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in
>>> message news:65lg82h93ltcoqn57c2lfng0glkq3ps83s@4ax.com...
>>>> On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
>>>> <Ricardo@discussions.microsoft.com> wrote:
>>>>
>>> <snipped>
>>>>>
>>>>>Not sure, try these people:
>>>>>
>>>>>http://www.synesisit.com/Prod/static/migration.jsp
>>>>>
>>>>>Cheers
>>>>
>>>> Are you going to post this for every question?
>>>
>>> OK...but does anyone have answers or opinions on the questions?
>>>
>>> DD
>>>
>>>
>>
>>
>
>

DukieDallas
Sat Jun 10 20:56:59 CDT 2006

Thanks again, Eric.

"Eric Tam [MSFT]" <ericta@online.microsoft.com> wrote in message
news:%23Aa0F6MjGHA.3440@TK2MSFTNGP02.phx.gbl...
> That should be okay, especially since we would move from Std -> Ent
> version of the same OS.
>
> --
> Eric Tam, MCSE, MCSA
> Microsoft Exchange Support
>
> 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.
> "DukieDallas" <rangerlax@sbcglobal.net> wrote in message
> news:OO5FLjziGHA.4284@TK2MSFTNGP05.phx.gbl...
>> Thank you, Eric. I was leaning that way anyway.
>>
>> Out of curiosity, when you say "both options are valid," were you
>> including an answer to my question #1 - whether Svr2003 Standard and
>> Svr2003 Enterprise would be considered the same operating system for the
>> purposes of the KB 822945 procedure?
>>
>> Thank you for the advice.
>>
>> DD
>>
>> "Eric Tam [MSFT]" <ericta@online.microsoft.com> wrote in message
>> news:%23zqyrDziGHA.1260@TK2MSFTNGP05.phx.gbl...
>>> Hi Dukie,
>>>
>>> Both options are valid when you are attempting to move Exchange data to
>>> a new server. However, I would probably recommend the second option
>>> where you would bring up a second Exchange server and move data to it.
>>> This limits the amount of downtime in the environment since you do not
>>> have to take the original server offline for any time. If you move
>>> mailboxes using the Move Mailbox wizard (Exchange Tasks->Move Mailbox)
>>> then you will not have to do anything with the existing user's profile
>>> as long as the original server is online. The profile will get updated
>>> when the user attempts to open their mailbox - it will first attempt to
>>> connect to the old server but will get redirected to the new server and
>>> anytime after that point it will continue to go to the new server. This
>>> redirection will not work if the old server is offline, that's why it's
>>> important to keep the old server up a week or so to allow your users to
>>> log into their mailbox. Once you're ready to decommission the old
>>> server, follow this KB:
>>>
>>> 822931 How to remove the first Exchange Server 2003 computer from the
>>> administrative group
>>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;822931
>>>
>>> Hope this helps!
>>> --
>>> Eric Tam, MCSE, MCSA
>>> Microsoft Exchange Support
>>>
>>> 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.
>>> "DukieDallas" <rangerlax@sbcglobal.net> wrote in message
>>> news:uEwZw$xiGHA.4512@TK2MSFTNGP02.phx.gbl...
>>>>
>>>> "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in
>>>> message news:65lg82h93ltcoqn57c2lfng0glkq3ps83s@4ax.com...
>>>>> On Thu, 8 Jun 2006 09:06:02 -0700, Ricardo
>>>>> <Ricardo@discussions.microsoft.com> wrote:
>>>>>
>>>> <snipped>
>>>>>>
>>>>>>Not sure, try these people:
>>>>>>
>>>>>>http://www.synesisit.com/Prod/static/migration.jsp
>>>>>>
>>>>>>Cheers
>>>>>
>>>>> Are you going to post this for every question?
>>>>
>>>> OK...but does anyone have answers or opinions on the questions?
>>>>
>>>> DD
>>>>
>>>>
>>>
>>>
>>
>>
>
>