Re: Delay for nexted security group membership?
- From: shasta <shawn.monighan@xxxxxxxxxxxxx>
- Date: Wed, 12 Dec 2007 06:20:00 -0800
Here is some more information and hopefully I can do a better job explaining
my question.
We have 5 sites. Our corporate office is condsidered our main site; the
domain controllers where we make AD changes. The replication interval is set
for 15 minutes between each of our 5 sites.
I have security group A and put the Domain Users group in to security group
A. How long does it take AD to recognize this nested group membership?
"Richard Mueller [MVP]" wrote:
.
"Richard Mueller [MVP]" <rlmueller-nospam@xxxxxxxxxxxxxxxxxxxx> wrote in
message news:eEFzPoDPIHA.5264@xxxxxxxxxxxxxxxxxxxxxxx
"shasta" <shawn.monighan@xxxxxxxxxxxxx> wrote in message
news:F1094D34-EF3B-41C5-819F-BF2D458959B9@xxxxxxxxxxxxxxxx
I am trying to find out the amount of time it takes for nested group
membership to take effect. Meaning if I put a security group within
another
group how long does it take AD to regconize this change. Kinda like if
I
put a user in a security group the user has to logout and then login to
push
the reconigition of this membership.
When a user authenticates the DC gives them a token with the objectSid of
all groups the user belongs to, including the "primary" group of the user
and all groups the user is a member of due to group nesting (in the
domain). If the user is added to a group while they are logged on, their
token is not modified. They must logoff and logon again so the new token
reflects the new membership. Whenever the user attempts to access a
resource, the token can be checked to see if it includes a trustee that
has permission for the resource.
If the permissions of a group are modified, that should be reflected
immediately. If changing membership requires changes in the token, the
user must logoff and logon.
--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--
And as Jorge points out, when the user logs out and logs back in, the DC
that authenticates the user must know about any changes in group membership.
There can be a delay until the changes replicate. This depends on network
topology, but should not be more than about 15 minutes, unless there are
slow links.
--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--
- Follow-Ups:
- Re: Delay for nexted security group membership?
- From: Jorge Silva
- Re: Delay for nexted security group membership?
- References:
- Re: Delay for nexted security group membership?
- From: Richard Mueller [MVP]
- Re: Delay for nexted security group membership?
- From: Richard Mueller [MVP]
- Re: Delay for nexted security group membership?
- Prev by Date: Re: Windows cannot connect to the domain & Event ID 3210 5722 - Lots of Details!
- Next by Date: Re: Delay for nexted security group membership?
- Previous by thread: Re: Delay for nexted security group membership?
- Next by thread: Re: Delay for nexted security group membership?
- Index(es):
Relevant Pages
|