Question
A collection of frequently asked questions regarding how the EPM Agent interacts with Active Directory (AD) and Domain Controllers (DCs), including cache refresh intervals, authentication methods, logging, and retry behaviors.
Answer
1. What is the default and configurable interval for the agent’s AD/DC cache refresh and any retry/rescan behavior?
The EPM Agent maintains two distinct AD caches:
AD Users/User Groups Cache: Built upon agent startup and refreshed with every policy update.
AD Computer Groups Cache: Built upon agent startup and refreshed approximately every 24 hours.
Both caches can be force-refreshed via the agent command-line interface (CLI). Do note that "Request Settings" option from EPM tray icon does not refresh the AD Computer Groups Cache.
2. How does the agent authenticate to domain controllers (LDAP simple bind, Kerberos, LDAPS)?
Only the AD computer groups cache mechanism authenticates directly to the DC. It initially attempts LDAPS authentication. If LDAPS fails, it will fall back to standard LDAP authentication.
3. Apart from the AD group membership of the computer account and user (during runtime), does the agent retrieve any other details from the DC?
No additional details are retrieved.
For computer accounts, the agent retrieves only group membership information.
For users and user groups, it retrieves the mapping between the account name and the account Security Identifier (SID).
4. If the agent runs as Local System, does it authenticate to AD using the domain computer account, or does it require separate credentials for LDAP/AD queries?
The agent authenticates using the native domain computer account. No separate LDAP credentials are required to be configured.
5. Where are the local agent logs stored, and do they show cache refresh activity, target DC, query type, timing, retries, and failures?
Yes, cache refresh activity, retries, and failures are all logged.
The logs are stored locally on the endpoint at the following path: C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent\Trace
To search specifically for AD computer group-related issues in these logs, filter your search using the prefix: AdCompGrpThread
6. Is user group membership collected at runtime for policy/app decisions? If yes, is it cached, and does each app launch trigger a fresh DC query?
Yes, the agent maintains a cache for policy and application decisions.
If an entry is not present in the cache, a DC query is executed during the initial application launch. That result is then stored in the cache until the next policy update, at which point the cache is completely rebuilt. Until that subsequent policy update occurs, user group membership remains safely cached, and no additional DC queries are generated by subsequent application launches.
7. How does the agent choose a DC, and is the process site-aware?
The process is not site-aware. The EPM Agent leverages standard Windows APIs to naturally discover and select Active Directory Domain Controllers.
8. Does the agent perform AD/DC lookups immediately at startup, user logon, network reconnect, or when the agent service restarts? Could these events cause many endpoints to query DCs at the same time?
Machine group membership information is queried from AD under the following conditions, utilizing randomization to prevent DC overload:
Routine Refresh: The cache is refreshed approximately every 24 hours following an agent restart. The actual refresh interval varies randomly between 23 and 25 hours.
Load Distribution: Because the cache refresh interval is triggered relative to the individual agent's restart time (and incorporates the 23-25 hour randomization) rather than an absolute clock time, it effectively prevents simultaneous queries and distributes the query load across the deployment.
9. What is the fallback/retry behavior if a DC is unavailable or slow?
If the DC is unavailable, the agent retains the last successful query result in its cache. Retries are scheduled based on the cache type:
Users/Policies Cache: Retries upon the next policy update.
Computer Groups Cache: Retries after its standard cycle (approximately 24 hours).
If an administrator needs to expedite the retry process, both caches can be manually force-refreshed via the agent CLI.
10. Does Idira provide expected LDAP/DC request rates per endpoint or sizing guidance for large deployments?
No, there is currently no specific sizing guidance or expected request rate metrics provided for LDAP/DC queries.
11. How long does the EPM Agent typically take to synchronize OU membership after being moved to another Set?
The operation to move an agent to a new Set completes almost immediately (within seconds to minutes, as it is a live server-pushed command).
However, moving a Set does not force a refresh of the AD Computer Groups Cache (which backs OU/AD-group-based targeting). That cache continues to run on its independent 23–25 hour cycle.
If a newly referenced AD group has never been cached, it is checked almost immediately.
If the group was already cached and the endpoint's actual membership changed, the stale cache can persist for up to 23–25 hours until the next scheduled rescan.
12. Does the EPM Agent re-evaluate the local AD computer cache when policies are created or updated in the EPM Console?
Yes, the agent refreshes the cache when a policy changes, specifically when new targets are added.
However, it is important to emphasize that for AD computer groups, the agent does not automatically refresh the cache when a group is modified directly in Active Directory. The agent has no indication if or when a group changes within AD. For those AD modifications, the agent will only recognize the new group membership during its next scheduled cache refresh cycle (or if a refresh is manually forced).
View full article