dhoffman_98 is spot on, however the reason option B also works is because of replication, a call is made to AD on a deny to verify Group membership (in case changes have been made) it will work at this point because AD is fully replicated and able to confirm membership. To answer your question there is no other way to get this process over with out using option A or B. What you could do is force a replication, but to do this after each group membership update will be frustrating, rather just wait out the 15 minutes or reboot.
Main Topics
Browse All Topics





by: dhoffman_98Posted on 2007-08-07 at 19:33:49ID: 19651009
I'm not sure that B is really going to make a difference unless you have some GPO that is making changes... but in general making a change to group membership means that the user's Kerberos token will change. This token contains the user's security information, including group membership information. The security token is called each time you attempt to access a privileged resource and if the token has the appropriate information your access will be granted or denied.
The trick is this... the Kerberos token is generated at login time... thus the need for a user to log out and log in again.