We're in a co-existence situation. We've successfully installed two Hub servers in our environment. The two RGC's were created successfully and we can route mail between our production Ex2003 environment and our pre-production Ex2007 environment. The problem is that we do not want just one Hub and one Ex2003 bridgehead server set to send/receive mail. That would lead to single points of failure. I am trying to use the Set-RoutingGroupConnector to add addittional Source and Target Transport Servers as so: Set-RoutingGroupconnector -identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\From 2007 to 2003" -sourcetransportservers HUB1,HUB2 -targettransportservers EX2003-BH1,EX2003-BH2 HUB1 and 2 are replaced with the NetBIOS names of my Hub servers. EX2003-BH1 and BH2 are replaced by the NetBIOS names of our Ex2003 bridgehead servers. I've tried quotes around all servers names (e.g. "HUB1","HUB2") and FQDN's of all servers names, but it doesn't work. I have used this cmdlet to change the name of the connectors without any issue. It's been quite a few hours since I made the change, and we've checked to verify replication health in our environment. Here is a copy of the error message I am getting: Set-RoutingGroupConnector : Active Directory operation failed on mydc.mydomain.com. This error is not retriable. Additional information: The name reference is invalid.This may be caused by replication latency between Active Directory domain controllers.Active directory response: 000020B5: AtrErr: DSID-03152392, #1: 0: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att315c30e2 (msExchTargetBridgeheadServersDN)At line:1 char:26+ set-routinggroupconnector <<<< -domaincontroller mydc.mydomain.com -identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\From 2007 to 2003" -sourcetransportservers HUB1,HUB2 -targettransportservers EX2003-BH1,EX2003-BH2 I've got no clue what this means... anyone?

Hi, Please refer to following KB: You cannot add a server that is running Exchange 2000 Server or Exchange Server 2003 to a Hub Transport server role when you set up Exchange Server 2007 http://support.microsoft.com/?id=934258 Mike

I appreciate the response, but that's not what i'm trying to do. I'm trying to modify the current RGC, not create a new one. I've seen posts on the 'net where people have been successful doing this. I'm trying to use Set-RoutingGroupConnector, not New-RoutingGroupConnector. Also, check out this article talking about Set-RoutingGroupConnector: http://technet.microsoft.com/en-us/library/aa998581(EXCHG.80).aspx The example even shows adding a Ex2003BH server to the connector.

Addingto this in hopes of someone being able to help. I've done this: $rgc = Get-RoutingGroupConnector - Identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\From 2007 to 2003" $rgc.SourceTransportServers Which returns a lot of information about HUB1. So I'm certainly retrieving information. And then I run this: $rgc.SourceTransportServers += "HUB2" ...which should append the second HT server to the SourceTransportServers output.Instead, I get an error: Exception setting "SourceTransportServers": "Cannot convert value "System.Object[]" to type "Microsoft.Exchange.Data.MultiValuedProperty`1[Microsoft.Exchange.Data.Directory.ADObjectId]". Error: "Failed to convertHUB2 from System.String to Microsoft.Exchange.Data.Directory.ADObjectId.""At line:1 char:6+ $rgc.s <<<< ourcetransportservers += "HUB2" So in this case all I tried to do was add a new HT server as a source transport server. No Exchange 2003 servers were involved here - period. I still can't make this happen. Any other info I can give that'd help?

I called MS support yesterday. Turns out there is a known issue here. I'm waiting for the tech to get back to me with more info. At that point I'll post the findings.

Any luck? I'm experiencing the same issue.

Sort of. It is indeed a bug. MS has confirmed this and marked my case as a non-dec, i.e. no charge for it. The problem is that your Exchange 2003 has written some things to the AD schema that don't jive. The MS tech could not get a hold of the tech who wrote the article, but here is where the "problem" is with your environment: Open ADSIEDIT and navigate down as follows: Configuration - Services - Microsoft Exchange - Org name - Administrative Groups - Your Admin Group - Servers - First server in the list - Protocols - SMTP - CN= X, where X probably is equal to 1. Now navigated to SMTP under your second server in the list. Likely it does not say CN=1, rather it says CN=2. That's the problem. The Exchange 2007 RGC's only will accept 2003 bridgeheads where that schema setting is CN=1. I don't know if this is a cluster issue (we're running a 2003 cluster) or not. MS has instructed me to delete the RGCs created when Exchange 2007 was installed. Create a new RGC from the 2003 tools, make it bidirectional, and add your bridgeheads and hub servers as needed. The important thing is to delete the existing connector first or 2003 won't let you create a bidirectional connector. I have *not* done this as of yet. Were debating if it is worth the risk.