Group Refresh updates are falling behind Rule

Run As Profiles

Name
Default

Alert Details

Message Priority Severity
Group Refresh updates are falling behind Medium Warning

Rule Knowledgebase

Summary

The No GC Logon task was unable to update all of the cached entries during its last attempt.

Sample Event:

The group membership cache refresh task is behind schedule.

Causes
This rule does not contain any causes.
Resolutions

Consider forcing a group membership cache update.

If the number of entries is greater than 500, you should have also received a companion alert “Group Cache Refresh has reached the user limit for this domain controller.” In this case, follow the instructions for that alert.

Otherwise, the replication window is too short for the number of objects in the cache, and the only option is to extend the window.

External References

For more information, see:

See Also for Active Directory (AD) Monitoring Management Pack


Downloads for Active Directory (AD) Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED