|
So my organization recently decided to migrate from Exchange 2003 to Exchange 2007. Easy enough, right? We purchased a new server with tons of RAM, and lotsa processing power. Loaded up Windows Server 2003 x64, and finally popped in the Exchange 2007 CD
The one thing I learned from this experience: Just because you know Exchange 2003 does not mean you know Exchange 2007. It is INSANELY different. I'm sure it's for the better, but the learning curve is steep. So, when you introduce an Exchange 2007 server to your 2003 environment, it does some funny stuff in ESM. First of all it creates it's own routing group. This newly created routing group should not be modified in any form or fashion!
A couple of notes regarding '07:
- SMTP should NOT be installed prior to the Exchanghe install
- NNTP should NOT be installed prior to the Exchange install
So the install completed successfully. I created a test mailbox on the new '07 server. Tried testing mailflow between '03 and '07. FAILED MISERABLY!
If you find yourself in this situation, the routing group connector that is supposed to be installed automatically, probably did NOT get installed. This should be easy enough to fix, right? Just create a new connector in ESM, right? WRONG!
In order to fix this, you need to log on to the '07 server, launch Exchange Management Shell, and feed it the following command:
New-RoutingGroupConnector -Name "Routing Group Name" -SourceTransportServers "FQDN of Exchange '07 server" -TargetTransportServers "FQDN of Exchange '03 Server" -Cost 100 -Bidirectional $true -PublicFolderReferralsEnabled $true
This should get the mail flowing to and from both servers. Obviously I still have a lot to learn, and will be posting more on this topic, as this is currently the biggest learning curve yet with MS Exchange
|