Prev: PFDAVADMIN not working on EX2007 after Rollup 5
Next: The Exchange server address list service failed to respond...
From: TallPaul on 9 Dec 2008 07:50
I'm having trouble modifying RGCs using the set-RoutingGroupConnector cmdlet.

When I type "set-RoutingGroupConnector -Identity RGC1 -Cost 50" I get an
error saying "The operation could not be performed because 'RGC1' matches
multiple entries."

I imagine this is because RGC1 is a bidirectional routing group connector.
When I type "get-RoutingGroupConnector" RGC1 is shown twice, from E2K7-E2K
and vice versa.

Does anyone know how I can specify which of these entries to modify?
From: Oliver Moazzezi [MVP] on 9 Dec 2008 08:06
Hi there,

You can either rename the 2003 to 2007 one in ESM (right click rename, it
allows this). Or you can rename in EMS

Set-RoutingGroupConnector -identity 'name' -name 'newname'

You might have an issue with the above command, perform
Get-RoutingGroupConnector and then follow up with |fl to check that the
bi-directional ones have a different -identity to their actual -names. I
don't have a bi-directional one in the lab.

Oliver


From: TallPaul on 9 Dec 2008 08:39
Thanks Oliver, changing the name in ESM has done the trick.

"Oliver Moazzezi [MVP]" wrote:

> Hi there,
>
> You can either rename the 2003 to 2007 one in ESM (right click rename, it
> allows this). Or you can rename in EMS
>
> Set-RoutingGroupConnector -identity 'name' -name 'newname'
>
> You might have an issue with the above command, perform
> Get-RoutingGroupConnector and then follow up with |fl to check that the
> bi-directional ones have a different -identity to their actual -names. I
> don't have a bi-directional one in the lab.
>
> Oliver
>
>
>
From: Andy David {MVP} on 9 Dec 2008 09:05
On Tue, 9 Dec 2008 05:39:16 -0800, TallPaul
<tallpaul(a)discussions.microsoft.com> wrote:

>Thanks Oliver, changing the name in ESM has done the trick.

Yea, I never create bi-directional for that reason. Easier for me to
just issue 2 PS commands to create 2 separate ones. :)


>
>"Oliver Moazzezi [MVP]" wrote:
>
>> Hi there,
>>
>> You can either rename the 2003 to 2007 one in ESM (right click rename, it
>> allows this). Or you can rename in EMS
>>
>> Set-RoutingGroupConnector -identity 'name' -name 'newname'
>>
>> You might have an issue with the above command, perform
>> Get-RoutingGroupConnector and then follow up with |fl to check that the
>> bi-directional ones have a different -identity to their actual -names. I
>> don't have a bi-directional one in the lab.
>>
>> Oliver
>>
>>
>>
 | 
Pages: 1
Prev: PFDAVADMIN not working on EX2007 after Rollup 5
Next: The Exchange server address list service failed to respond...