EPM Policy Best Practices – Refresh AD Computer Groups Cache

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Endpoint Privilege Manager (EPM) Articles
2 min read
L0 Member
No ratings
Problem: When working on EPM policies you may have a need to modify your targets such as adding additional computers to your policies for example.  Best practice is to target your AD Computer Security Groups in your policies when possible.  However, when computers are added in AD, it could take up to 24 hours for the modified EPM policies to recognize those newly added computers.

Solution:  Introduced in EPM v23.6, you will be able to refresh the AD computer groups cache immediately without having to wait the 24 hour period.  This will allow you to update and deploy your policies much more quickly and ensure any newly added computers are included.

Steps

In the following example, we have an EPM policy with a Target to an AD security group called “DemoSecGroup”.
ka3Vy000003dbWxIAI__eid=ka3Vy000003dbWx&feoid=00N2J000009R3kv&refid=0EMHt000005P0sd.png
We have just added a few computers to the “DemoSecGroup” security group and would like to refresh the AD computers group cache proactively.  From a computer that has version 23.6 of the EPM agent or higher, navigate to the below path and run the command “vf_agent.exe -RefreshCache AD”.  The refresh process could take a few minutes to complete.  Another option to trigger this command is by using the “Request Settings” item in the pop-up menu from the EPM tray icon.
ka3Vy000003dbWxIAI__eid=ka3Vy000003dbWx&feoid=00N2J000009R3kv&refid=0EMHt000005P0se.png
Rate this article:
  • 2096 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎12-16-2024 10:48 AM
Updated by: