Now I notice I have an error every time I go into the ESM and want to look
at my hub transport receive connector properties:
-----------------
get-receiveconnector
Failed
Error:
The Exchange group with GUID "3f965b9c-f167-4b4a-936c-b8efb19c4784" was not
found. This group was automatically created during Exchange Setup, but has
been subsequently removed.
-----------------
Anyone else run into this? I saw some posts out there saying to rerun setup
/prepareAD, but I'm wondering what that effect that has on an existing 2007
environment which is otherwise running fine (just can't modify my settings
for the receive connectors on my hub transport....
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com
I ended up fixing the issue by using softerras LDAP administrator and
restoring the exchangelegacyinterop group from the tombstoned - deleted
objects folder. The second that came back, I was able to see my two receive
connectors. Doesn't seem like the "exchange domain servers" had anything
to do with fixing the issue..in case anyone runs into this again
Still not sure why I would need to have something that was created for
2003<->2007 interdependance... the only thing I left around was the original
2003 administrative group that had the 2003 exchange servers since all the
articles I read made a big panic about not deleting that since it was the
original administive group...
"Jamestechman" <jamest...@gmail.com> wrote in message
news:6e48fdc4-0d22-4975...@x35g2000hsb.googlegroups.com...
>Nope..nothing returns when I do that..
>
>I ended up fixing the issue by using softerras LDAP administrator and
>restoring the exchangelegacyinterop group from the tombstoned - deleted
>objects folder. The second that came back, I was able to see my two receive
>connectors. Doesn't seem like the "exchange domain servers" had anything
>to do with fixing the issue..in case anyone runs into this again
I wonder if it would have worked if you had removed the
ExchangeLegacyInterop group from the Exchange objects permissions in
AD via adisedit. It could be that it barfed simply because it could
not resolve that guid.