Re: GC *and* Universal Group Caching

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 08/21/04


Date: Sat, 21 Aug 2004 11:29:58 -0400

Great Post Dean. You da man!

:o)

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Dean Wells [MVP] wrote:
> JB Fields wrote:
> 
>>Thanks.  Appreciate the extra info.  So, I take it that if I
>>authenticate to a DC that is a GC and caching is turned on pointed at
>>another domain, the DC will get Universal group membership from it's
>>cache as its own behavior has been altered to do so.  It will not
>>look for a GC, unless a new person signs on who has not been
>>previously cached?
>>
>>>The preference would be if you have a GC at a site, don't use
>>>caching at the same site. No point unless you lose the GC but you do
>>>open yourself up for cache delays (i.e. adding a user to a group and
>>>it not being reflected in the cache for a while or alternatively
>>>removing someone and it not being reflected).
>>>
>>>The realistic use of caching is for the case where you can't have a
>>>GC onsite AND you are unable to disable the GC logon requirement
>>>(ignoregcfailures) because you use Universal groups for assigning
>>>perms and not just for DLs.
>>>
>>>   joe
>>>
>>>--
>>>Joe Richards Microsoft MVP Windows Server Directory Services
>>>www.joeware.net
>>>
>>>
>>>
>>>JB Fields wrote:
>>>
>>>>Any benefit in using both a GC and Universal Group Caching at a
>>>>remote site other than fault tollerance?  Which will the domain
>>>>controller use for finding uinversal group membership at user login
>>>>if both are available?
>>>>
>>>>J
> 
> 
> Correct, the caching is NOT a failover ... it's on or off.
> 
> In addition, Uni. Group caching is misrepresented by its name in that it
> also caches Global Groups which are already known to the site local DCs
> ... any Global Group membership changes, even those membership changes
> made locally at the caching site, will not take effect until the next
> _successful_ cache update.
> 
> The cache update process is per DC in the caching site (no bridgehead /
> a single DC in the site = no duplicate effort / 2 DCs = 2 independant
> cache update processes = 2 x bandwidth requirement) and defaults to an 8
> hour cycle but respects site-link time windows.  Finally, the update
> process is (by default) only capable of working with a maximum of 500
> actively cached users ... any users greater than the 500 max. (that are
> still actively having their cache updated) are simply not included in
> the update cycle.  No membership change for those users will become
> effective until their cache expires (by default 7 days) whereupon a GC
> is once again required for authentication or they fit within the 500
> user ceiling or the ceiling is increased to deal with them.
> 
> Dean
> 


Relevant Pages

  • Re[2]: [PHP] dynamic -> static
    ... As I wrote already this issue is mainly because of search engines ... incompatibility with dynamic content sites (to be more exact - with ... You can cache your code using PHP Accelerator or Turck ... MM> implementing a caching layer between your application and your database. ...
    (php.general)
  • Re: [PHP] Aggressive PHP Smart Caching
    ... i have begun to experiment w/ your caching tool. ... it is also important that the script calling ob_end_flushhave access to ... the header method in the first bit of code in the cache tool. ...
    (php.general)
  • Re: [PHP] dynamic -> static
    ... You can cache your code using PHP Accelerator or Turck ... implementing a caching layer between your application and your database. ... 404 causes it to error out regardless of the content of the response. ... with any caching system as above - finding and flushing stale data. ...
    (php.general)
  • Re: IIS 6.0 caching Image Files when we dont want it
    ... Well, your application does not sound like it is cache friendly, so maybe ... the decision to do static file caching works like this: ... IF Static File Caching is not disabled (W3SVC/DisableStaticFileCache is ... Disabling static file cache does indeed solve the problem but affects other ...
    (microsoft.public.inetserver.iis)
  • Re: GC *and* Universal Group Caching
    ... >> authenticate to a DC that is a GC and caching is turned on pointed at ... the DC will get Universal group membership from it's ... the caching is NOT a failover ... ... any Global Group membership changes, ...
    (microsoft.public.windows.server.active_directory)