Exchange 2000 move to new box - Microsoft Exchange

what about these: (system folder)
1. Offline Address Book Public Folder,
2. Schedule + free/busy public folder

following article will explain it more:
http://support.microsoft.com/default.aspx?kbid=307917

-anil


"Tim W." <Tim W.@discussions.microsoft.com> wrote in message
news:31DDD885-6023-4489-A59F-6C7B782A3D0F@microsoft.com...
>I am moving Exchange to a new server. The old server is failing and I need
>to
> replace it.
>
> So far I have:
>
> Added Exchange in the same forest to another server
> Created new mailbox store
> Created new public folder store
> Replicated existing public folders to new server
> Made new server default public store
> Promoted new server to a Global catalog server and assigned all FSMO roles
> to it
> Modified the recipient update service to point to the new server
> Created default virtual servers for SMTP and POP3 on the new server
> Moved about half of the mail boxes over to the new server
>
> Here is where I am having a problem. Testing the new server for incoming
> and
> outgoing mail I find that mail does not go in or out when the old server
> is
> offline. I can send and recieve mail when the old server is online but has
> the Exchange services stopped.
>
> The MX record points to a specific IP address then is "NATTED" to go to
> the
> correct server behind the firewall. I assume this should not make any
> difference because the IP address of the MX record always points to the
> public / static address. The firewall settings for POP3 and SMTP virtual
> servers have been changed to point to the new server.
>
> Mail headers seem to indicate the new server is processing the mail but,
> again when the old server goes offline the mail stops. Checking the queue
> on
> the new server while the old server is offline I see mail waiting to be
> delivered.
>
> Any suggestions? what did I miss? Do I need to modify the MX records? Is
> there somewhere I missed changing the virtual servers?
>
>

The items you mentioned were alos moved. Everything is
now on the new server. The only problem is taking down
the old server without removing Exchange. I would like to
be really sure the new server will function including
sending and recieving SMTP mail before removing the
software from the old server.

I did see the kbid 307917 and followed it as well as
other articles from other Exchange sites.

MS also has 2 articles KB 235396 Determining first
Exchange server and KB152960 Reassigning site roles after
removing the first Exchange server in an Exchange site. I
don't really want to force reassignment or manually
reassign those roles before testing.

All I am really after is to make sure the new server is
functional as soon as I take the old server down. I have
not found anywhere that allows for testing before removal.

Thanks for the input.
>-----Original Message-----
>what about these: (system folder)
>1. Offline Address Book Public Folder,
>2. Schedule + free/busy public folder
>
>following article will explain it more:
>http://support.microsoft.com/default.aspx?kbid=307917
>
>-anil
>
>
>"Tim W." <Tim W.@discussions.microsoft.com> wrote in
message
>news:31DDD885-6023-4489-A59F-
6C7B782A3D0F@microsoft.com...
>>I am moving Exchange to a new server. The old server is
failing and I need
>>to
>> replace it.
>>
>> So far I have:
>>
>> Added Exchange in the same forest to another server
>> Created new mailbox store
>> Created new public folder store
>> Replicated existing public folders to new server
>> Made new server default public store
>> Promoted new server to a Global catalog server and
assigned all FSMO roles
>> to it
>> Modified the recipient update service to point to the
new server
>> Created default virtual servers for SMTP and POP3 on
the new server
>> Moved about half of the mail boxes over to the new
server
>>
>> Here is where I am having a problem. Testing the new
server for incoming
>> and
>> outgoing mail I find that mail does not go in or out
when the old server
>> is
>> offline. I can send and recieve mail when the old
server is online but has
>> the Exchange services stopped.
>>
>> The MX record points to a specific IP address then
is "NATTED" to go to
>> the
>> correct server behind the firewall. I assume this
should not make any
>> difference because the IP address of the MX record
always points to the
>> public / static address. The firewall settings for
POP3 and SMTP virtual
>> servers have been changed to point to the new server.
>>
>> Mail headers seem to indicate the new server is
processing the mail but,
>> again when the old server goes offline the mail stops.
Checking the queue
>> on
>> the new server while the old server is offline I see
mail waiting to be
>> delivered.
>>
>> Any suggestions? what did I miss? Do I need to modify
the MX records? Is
>> there somewhere I missed changing the virtual servers?
>>
>>
>
>
>.
>

This article applies to the steps needed to migrate to a new Exchange 2003
server, even though it indicates it is for Exchange 2003.
822931 How to remove the first Exchange 2003 Server computer from the
http://support.microsoft.com/?id=822931

The step that appears to be missing is migrating any connectors. In this
case it sounds like you only need to re-route SMTP (internet) mail flow.
There are two parts to this as you know. Re-routing incoming SMTP mail and
re-routing outbound SMTP mail.

Re-routing incoming SMTP mail:
========================
Since your MX record points to the public IP address of your firewall, you
would need to change where SMTP traffic (port 25) is routed on the firewall
so that it goes to the private IP address of your new Exchange server.

Re-routing outbound SMTP mail:
=======================
1] If you already have an SMTP connector created for your routing group you
will simply need to designate only the new server as a bridgehead server.
This will force all outbound internet Email to go out of this server.
2] If you do not have an SMTP connector created for your routing group, you
will need to create an SMTP Connector on your new Exchange server per:
265293 How to Configure the SMTP Connector in Exchange
http://support.microsoft.com/?id=265293
-Be sure to designate only the new server as a bridgehead server. This will
force all outbound internet Email to go out of this server.
3] After you have removed the old Exchange 2000 server from your
Organization you will be able to remove the Routing Group connector if you
want. Outbound internet email will flow out of your remaining Exchange 2000
server via the SMTP virtual server.


--
Hope that helps,
Rand Williams

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Tim W." <anonymous@discussions.microsoft.com> wrote in message
news:04da01c4b1f7$214b7bd0$a301280a@phx.gbl...
> The items you mentioned were alos moved. Everything is
> now on the new server. The only problem is taking down
> the old server without removing Exchange. I would like to
> be really sure the new server will function including
> sending and recieving SMTP mail before removing the
> software from the old server.
>
> I did see the kbid 307917 and followed it as well as
> other articles from other Exchange sites.
>
> MS also has 2 articles KB 235396 Determining first
> Exchange server and KB152960 Reassigning site roles after
> removing the first Exchange server in an Exchange site. I
> don't really want to force reassignment or manually
> reassign those roles before testing.
>
> All I am really after is to make sure the new server is
> functional as soon as I take the old server down. I have
> not found anywhere that allows for testing before removal.
>
> Thanks for the input.
>>-----Original Message-----
>>what about these: (system folder)
>>1. Offline Address Book Public Folder,
>>2. Schedule + free/busy public folder
>>
>>following article will explain it more:
>>http://support.microsoft.com/default.aspx?kbid=307917
>>
>>-anil
>>
>>
>>"Tim W." <Tim W.@discussions.microsoft.com> wrote in
> message
>>news:31DDD885-6023-4489-A59F-
> 6C7B782A3D0F@microsoft.com...
>>>I am moving Exchange to a new server. The old server is
> failing and I need
>>>to
>>> replace it.
>>>
>>> So far I have:
>>>
>>> Added Exchange in the same forest to another server
>>> Created new mailbox store
>>> Created new public folder store
>>> Replicated existing public folders to new server
>>> Made new server default public store
>>> Promoted new server to a Global catalog server and
> assigned all FSMO roles
>>> to it
>>> Modified the recipient update service to point to the
> new server
>>> Created default virtual servers for SMTP and POP3 on
> the new server
>>> Moved about half of the mail boxes over to the new
> server
>>>
>>> Here is where I am having a problem. Testing the new
> server for incoming
>>> and
>>> outgoing mail I find that mail does not go in or out
> when the old server
>>> is
>>> offline. I can send and recieve mail when the old
> server is online but has
>>> the Exchange services stopped.
>>>
>>> The MX record points to a specific IP address then
> is "NATTED" to go to
>>> the
>>> correct server behind the firewall. I assume this
> should not make any
>>> difference because the IP address of the MX record
> always points to the
>>> public / static address. The firewall settings for
> POP3 and SMTP virtual
>>> servers have been changed to point to the new server.
>>>
>>> Mail headers seem to indicate the new server is
> processing the mail but,
>>> again when the old server goes offline the mail stops.
> Checking the queue
>>> on
>>> the new server while the old server is offline I see
> mail waiting to be
>>> delivered.
>>>
>>> Any suggestions? what did I miss? Do I need to modify
> the MX records? Is
>>> there somewhere I missed changing the virtual servers?
>>>
>>>
>>
>>
>>.
>>