queueable.random.delay.interval

This configuration parameter specifies a maximum delay, in minutes, before adclient starts its background tasks, including:

  • Cache population and refresh

  • Group membership refresh

  • Zone data (SAM) cache reload

  • Computer object updates in AD, including DC information, uptime, and Group Policy (GP) status

On each machine, the scheduler for these background tasks calculates a random number of minutes between 1 and the maximum interval set in this parameter. If you change the interval setting, the period of time is recalculated. The default setting is 0 for no delay.

Exceptions

Login, authentication, and on-demand lookups are not affected by this parameter.

Effects of Using This Parameter

  • Prevents simultaneous access to Active Directory's DCs by large numbers of machines which might be restarted at the same time, such as during a maintenance window. Background traffic is distributed evenly over a greater period of time.

  • If the delay interval is set to a value greater than 0, the propagation of zone and role changes is delayed for some time (up to a maximum of the parameter value) after a restart.

  • The offset is recalculated every time a background task is triggered, so the exact time delay is unpredictable.

  • This parameter works in sum with the cache TTL setting in adclient.refresh.interval.dz. The greatest possible age of data that could result is the maximum delay interval plus the cache TTL. For example, if adclient.refresh.interval.dz is 30 minutes and queueable.random.delay.interval is 60 minutes, propagation of data could take up to 90 minutes.