Managed by Tab
- From: "nospam@xxxxxxxxxxxxx" <nospam@xxxxxxxxxxxxx>
- Date: Wed, 08 Feb 2006 16:27:17 -0800
Sorry for the delayed response.
As for the user, both the user and group are located on the same
domain. Also in the domain that they belong there are 2 GC's. So I am
not sure if the GC is the issue. Do you have any other suggestions?
Thanks
On Wed, 1 Feb 2006 12:16:09 -0800, "John Fullbright"
<fullbrij@xxxxxxxxxxx wrote:
What you are referring to is the process DSProxy uses to determine a
server to give as a referral.
I think first, you'd have to determine the GC the specific outlook
client is using:
http://support.microsoft.com/kb/317209/
Apply the fix and check again.
If all else fails, you can just set it on the client
http://support.microsoft.com/kb/319206/en-us
"Nuevo" <imaneophyte@xxxxxxxxx wrote in message
news:edQCNh2JGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
John
I read that KB article and I see that you are right in one regard.
I'll attempt to sway you to see that I'm also right. So perhaps the
two parts are a whole answer to the original question:-)
My (longer and probably quite a lot more boring) explanation.
Pre SP2
The global catalog server will be from one of two locations:
. The GC is located within the same AD site as the Exchange server
(normal behavior).
. The GC is located within an AD site that is directly connected to
the Exchange server's AD site (when all in-site GCs are unavailable).
In addition to site membership there is a preference for global
catalog servers that are members of the same domain as the Exchange
server. If none are available, then DSProxy will utilize the other
global catalog servers in the AD site.
In a multi-domain environment this can lead to problems. For
example, if Outlook is referred to a GC server that does not reside in
the same domain as the user object certain object updates, e.g.
delegate access or distribution group membership, will fail.
Post SP 2
In Exchange 2003 SP2, the referral process will now attempt to
provide the Outlook client with a GC that belongs to the same domain
as the mailbox-enabled user using a new algorithm.
Five constraints for determining which GC to refer client (Notice
the weighting given to GCs in a user's domain):
.Constraint 1 A GC that is available (RPC ping) - 16 points
.Constraint 2 A GC that supports the client's protocol - 8 points
.Constraint 3 A GC that belongs to the user's domain - 4 points
.Constraint 4 A GC that is in the same Active Directory site as
the Exchange server - 2 points
.Constraint 5 A GC that is one of the GCs that the Exchange is
currently using - 1 point
Implications
These changes may cause an impact on existing environments. GC
referrals may change with an impact on client performance. Consider
adding GC servers to domains that contain mailboxes.
References
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TechRef/b7f8fbf4-732c-4a87-a9d5-3c4c375e5948.mspx
http://blogs.technet.com/exchange/search.aspx?q=dsproxy&p=1
http://support.microsoft.com/?id=256976
http://support.microsoft.com/default.aspx?scid=kb;en-us;250570
http://support.microsoft.com/?kbid=872897
"John Fullbright" <fullbrij@xxxxxxxxxxx wrote in message
news:%23q%23aIO2JGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
I always though it had to do with group placement, and whether or
not the GC
partition is writable.
I used to wake up in the middle of the night with a phone call,
only to be
dispatched to a hotsite issue where the customer would vent because
I was
the face of Microsoft on site, and then I'd have to figure out want
went
wrong and why. I lasted three years, and went on site about 150
times. I
think it was ROSS #4 where I learned the idiosyncrasies and
intracacies of
the relationship between Exchange, Outlook, and Active Directory
the hard
way.
Here's a link:
http://support.microsoft.com/kb/318074/en-us
enjoy
"Nuevo" <imaneophyte@xxxxxxxxx wrote in message
news:Oc6CcA2JGHA.984@xxxxxxxxxxxxxxxxxxxxxxx
The problem is caused by Exchange selecting a GC that is not in the
user
domain. SP2 introduces a new algorithm for DSAccess to
preferentially
select a GC in the user domain.
Nue
<nospam@xxxxxxxxxxxxx wrote in message
news:eov1u195p8dlenq9uj59teecqddvlvuk0e@xxxxxxxxxx
Yes I am trying to do this within Outlook. Is there any information
on
where to place our GC? We have a GC in every domain.
Thanks
On Wed, 1 Feb 2006 12:36:23 -0500, "Nuevo" <imaneophyte@xxxxxxxxx
wrote:
Are you trying to use Outlook to manage this? This may be to do with
your
GC
placement.
Nue
<nospam@xxxxxxxxxxxxx wrote in message
news:72q1u1lcjvfaoi6gtkanjmkfrnkj26jm9c@xxxxxxxxxx
Currently we have exchange 2003 in the root domain. Most of our
users
are located in the child domain. We I try and use and designate a
user to manage that group and select "Manager can update membership
list" it doesn't work. User still gets access denied. Is there
something else I am missing? If so what would it be?
Thank You
>
.
- Follow-Ups:
- Re: Managed by Tab
- From: John Fullbright
- Re: Managed by Tab
- Prev by Date: Re: Unblocked emails are still blocked
- Next by Date: Re: Message Forwarding Question
- Previous by thread: Re: Managed By Tab
- Next by thread: Re: Managed by Tab
- Index(es):
Relevant Pages
|
