asked on

Removing Routing Groups...

I have upgraded my exchange 2000 environment to 2007. During the migration I added the remote bridgehead connector for my old exchange 2000 server. I never removed this connector before decomissioning the old server. I now get messaged locked up in that queue trying to be delivered to the old server.

I went to the command shell to remove the connector but how do I know which connector to remove? There are 5 of them in there. They have very generic names some are named the same name as the exchange 2007 server and others are named the same as my domain. Is there a way to get more detailed information on these connectors?

Second question is should I have any at all? I know I need my SMTP connector in the hub transport section. But these connectors here through the shell, (I'm using the get-routinggroups cdmlet) seem to be connecting me to other servers. I no longer have any other servers. So i should be able to remove all of these connectors, correct?

Thanks

Name                      SourceRoutingGroup         TargetRoutingGroup
----                      ------------------         ------------------
LMHA1600                  First Routing Group        Exchange Routing Group ...
LMHA1600                  Exchange Routing Group ... First Routing Group
1600ex                    First Routing Group        Exchange Routing Group ...
1600ex                    Exchange Routing Group ... First Routing Group

Open in new window

rfranta

ASKER

Ok this seems to be getting worse. I read that I will not need any routing connectors in 2007 so I ws removing them But now since I have 2 each with the same names when I go to remover them i get the following error. Remove-RoutingGroupConnector : The operatio 00ex' matches multiple entries. At line:1 char:29 + remove-routinggroupconnector <<<< 1600ex How can I get more details on the RGC's to delete them. Name SourceRoutingGroup TargetRoutingGroup ---- ------------------ ------------------ LMHA1600 First Routing Group Exchange Routing Group ... LMHA1600 Exchange Routing Group ... First Routing Group 1600ex First Routing Group Exchange Routing Group ... 1600ex Exchange Routing Group ... First Routing Group

ASKER CERTIFIED SOLUTION

EurodataSystems

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rfranta

ASKER

Hi Steve thanks for your reply.

You are correct I did not decomission the old one correctly and I'm kicking myself now getting asll the little qwerks corrected.

I will follow your advice and give this a try

rob

pablomosca

FYI.. I had a similar issue when migrating from Exchange 2003 to 2007. I had 2 "Exchange 2007 RGC" I followed Steve's advice renaming the connector using adsiedit and so far all is working fine.

I'm not sure what this error is or what it was caused by or if it was even causing any issues. My system was working fine even though this error came up once in a while. Odd...

FYI the error I was getting in the Windows Event logs that led me to do this is listed below..

Process powershell.exe (EMS) (PID=5028). Configuration object CN=Exchange 2007 RGC1,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TSI2,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=TSI2,DC=local read from SAN-FILE-01.TSI2.local failed validation. Partially valid object will be returned. Set event logging level for Validation category to Maximum to get additional events about each failure.