• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 545
  • Last Modified:

Exchange 2010 coexistance with Exchange 2003 server untill all mail boxes are moved to 2010

Dear Experts,

We are upgrading to Exchange 2010 in a network that has 2 exchange servers 2003. This network uses a smart host (barracuda) to get their email. The Barracuda device points to one of the exchange 2003 servers.

How can I bridge the exchange 2010 to the 2003 exchange servers so I can send and receive email? I already moved my inbox to the exchange 2010, however, I am not getting or sending my e mails. The Barracuda device shows my emails coming in and allowing them.

For your time and help many thanks. M
0
marceloNYC
Asked:
marceloNYC
  • 9
  • 6
1 Solution
 
Stelian StanCommented:
On Exchange 2010 you need to create a Send Connector. Open EMC > Organization Configuration > Hub Transport > on the right panel click on " Send Connectors" > New Send Connector
0
 
marceloNYCAuthor Commented:
We tried that and still not working.
0
 
Exchange_GeekCommented:
The only method for E2010 and E2003 would talk to each other is via RGC (routing group connector), this isn't created by default and would be required to send/receive emails between both systems. Here is the cmdlet for creating it.

New-RoutingGroupConnector -SourceTransportServer "E2k3 box name" -TargetTransportServer -E2k10 box Name" -bidrectional $True

For receiving emails from internet -ensure that Default Receive connector has "Anonymous Logon" permission checked - else E2k10 won't receive emails from outside.

For sending emails to internet -ensure that send connector has been created with IP mentioned in the smart host location.

Regards,
Exchange_Geek
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
marceloNYCAuthor Commented:
Hello Exchange_Geek. We are getting this? What I am not doing right?

The term 'New-RoutingGroupConnector' is not recognized as the name of a cmdlet, function, script file, or operable prog
ram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:26
+ New-RoutingGroupConnector <<<<  -SourceTransportServer is-ok-ms01 -TargetTransportServer - dss-ok-ms01 -bidrectional
$True
    + CategoryInfo          : ObjectNotFound: (New-RoutingGroupConnector:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
0
 
Exchange_GeekCommented:
My bad add a "s" towards end of TransportServer, so it should look like SourceTransportServers and TargetTransportServers.

Regards,
Exchange_Geek
0
 
marceloNYCAuthor Commented:
I am researching why I am getting this message when I run the command:

The term 'New-RoutingGroupConnector' is not recognized as the name of a cmdlet

If you know why, please let me know what to do.

Thanks, M
0
 
Exchange_GeekCommented:
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Hub2010.contoso.com" -TargetTransportServers "Bridgehead2003.contoso.com" -Bidirectional $true

Here is an example from MS link
http://technet.microsoft.com/en-us/library/aa998574.aspx

Precisely same as what i gave you.

Regards,
Exchange_Geek
0
 
marceloNYCAuthor Commented:
I figure it out sorry!!!!
0
 
marceloNYCAuthor Commented:
Exchange Geek, now the people that are in the 2003 servers cannot send or receive emails...
0
 
Exchange_GeekCommented:
You've got a routing group connector?

if yes, run the command

Get-RoutingGroupConnector | FL >RG.txt

Attach RG.txt to your post please.

Regards,
Exchange_Geek
0
 
marceloNYCAuthor Commented:
Here you go....
0
 
Exchange_GeekCommented:
Aite I'll go - LOL, dont see anything attached.

Regards,
Exchange_Geek
0
 
marceloNYCAuthor Commented:
Here you go again...
RG.txt
0
 
marceloNYCAuthor Commented:
I think is working now. I am confirming as we type...
0
 
Exchange_GeekCommented:
Great, however you'll need to remove a RGC that was falsely created in your environment.

Run the following cmdlet

Remove-RoutingGroupConnector "OKC Exchange 2010"

You have just created a new RGC with name "Exchange 2010 OKC" which should work for you, however the cost you've added is 10 and the original cost for the above connector is 1. You're bound to get into issues.

Regards,
Exchange_Geek
0
 
marceloNYCAuthor Commented:
Excellent solution to my problem! Thank you so much!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now