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

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

0
rfranta
Asked:
rfranta
  • 2
1 Solution
 
rfrantaAuthor Commented:
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
0
 
EurodataSystemsCommented:
You didn't decommission your old server properly. I assume that Active Directory still knows about it.

The error happens when you manually create a Routing Group Connector in Exchange 2007 with the parameter "-Bidirectional $true" which is what Technet gives an an example. The Installation of Exchange 2007 creates individual routing connectors for each direction with different names.

You can use Get-RoutingConnector |fl to show the full details of the routing connectors, but that's not going to help you in your quest to remove them. For that you need to use adsiedit.msc from Windows Support Tools. If they're not installed, then install them from the Windows 2003 CD.

You can delete the connectors in adsiedit, but I'd suggest that you simply rename them and then go back to Exchange Management Shell (because when you make changes with adsiedit, you are directly modifying Active Directory - delete the wrong thing here and you'll have a world of pain).

The containers that your connectors are in are as follows:
(Start adsiedit.msc and expand Configuration. Then expand as appropriate)

CN=Configuration,
CN=Services,
CN=Microsoft Exchange,
CN=<Your Exchange Org>,
CN=<Exchange 2000/2003 site>,
CN=Routing Groups,
CN=<Exchange 2000/2003 routing group>,
CN=Connections

CN=Configuration,
CN=Services,
CN=Microsoft Exchange,
CN=<Your Exchange Org>,
CN=Exchange Administrative Group (FYDIBOHF23SPDLT),
CN=Routing Groups,CN=Exchange Routing Group (DWBGZMFD01QNBJR),
CN=Connections

I'd suggest appending a 1 to the ones under the Exchange 2000/2003 routing group and a 2 to the ones under the Exchange 2007 routing group.

Back in Exchange Management Shell use Get-RoutingConnector to return the list of routing connectors.
Then use Remove-RoutingConnector and (when asked) specify the Identity as per the list. Repeat as necessary.

As for your second question, no, you don't need them any more if your legacy servers have gone. But are you sure that there are no mailboxes left homed on your old Exchange server. You can do a find in ADU+C for Exchange users with mailboxes and add the filter Exchange Home DB server with the name of the old server. Or you can check for legacy mailboxes under Exchange Management Console.

You may want to leave other references to the legacy Exchange server alone because you then have the option of building a legacy Exchange server back into the environment, say for example, if you needed to restore from an old backup.

Steve
0
 
rfrantaAuthor Commented:
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


0
 
pablomoscaCommented:
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.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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