Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 334
  • Last Modified:

Can't Retire Old Exchange Server until IMS is gone

Hello everyone,

I have a client who is using, please don't laugh, Exchange 5.5 SP4 on an NT4 Domain - its a small shop.

(Please note I am working to migrate him to AD and Exchange 200x as per their request - But First!...)

The physical box that Exchange 5.5 SP4 resides on is "not" a PDC or BDC, it is a "Windows 2000 member server", quite old, and showing signs of failure.

The client "insisted" that I install Exchange 5.5 SP4 on another newer Windows 2000 member server, join the existing site, and move all mailboxes and services to it.

I have successfully:
Moved all Mailboxes to the new server
All "Public Folders" have been replicated to the the new server and removed from the old
All "Public Folders" show the new server as its "Home Server"
"Offline Address Book Server" is now the new server
The "Routing Recalculation Server" is now the new server and I did "Recalculate Routing" on the new server
Prior to changing the "Routing Recalculation Server" I added a new "Internet Mail Service" on the new server & changed its "Address Space" cost to "1" and the old to "10"
The "Address Space" for both are Type: SMTP, Address: *, and Scope: Organization

I have checked the gwart0.mta & gwart1.mta to confirm the new server has a value of 1 and the old server has a value of 10 on both server's .mta files.

I have a number of mailboxes that have "Custom Recipients" as "Alternate Recipients" and "Deliver messages to both recipient and alternate recipient" is checked.

I believe I am 99% ready to decommission the old server but when I "stop" the old IMS... inbound "External Email" bound for a valid mailbox gets to the mailbox but never gets forwarded to the "Alternate Recipient". Funny thing... when I restart the old IMS all messages for "Alternate Recipients" get sent.

I don't want to decommission the old exchange server until I know that turning off all of its Exchange services will result in no lost productivity.

In addition have also UNCHECKED "Disable Automatic Replies to the Internet" & restarted the IMS on both servers.

What haven't I done?

- Tom
0
mcit0331
Asked:
mcit0331
  • 3
  • 2
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So is there some Firwall routing emails ?
Where is the MX pointing to ?

- Rancy
0
 
mcit0331Author Commented:
Hello Rancy,

I have a Barracuda Appliance forwarding "external incoming - only" directly to the New Exchange Server.

Emails to external domains are sent through the gateway, much to my chagrin, by both Exchange servers instead of the new one.

- Tom
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So why not simply shut down the Old server for about 5 days and see if the new one can take the load and if any issues happen you will surely know (many a ways :))

- Rancy
0
 
mcit0331Author Commented:
Well, I finally found it. It appears that there was a registry key within the old Exchange Server called  "RerouteViaStore" (kb266260)

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIMC\Parameters\ReRouteViaStore

that was used in conjunction with an anti-virus program to ensure "all" email in or out got scanned.

Removing that registry key, restarting the "Internet Mail Service", then stopping IMS, resulted in "ALL" email going through the new server.

Thank you Rancy for all your suggestions.

- Tom
0
 
mcit0331Author Commented:
I found the answer on my own - kb266260.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now