Endpoint Privilege Manager (EPM) Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
We will be updating this article based on the questions we receive about the security bulletin. Please click the Follow button to receive change notifications. Is it necessary to uninstall the agent in order to install the updated version? No, the agent can be upgraded per the instructions in the following doc: Windows Agents MacOS Agents Linux Agents I'm receiving an "invalid key" or "incorrect configuration file" when attempting to install the new version When prompted for the installation key, make sure to use the one that was generated when downloading the installer package from the EPM console. When asked to select the configuration file, select the .config file that is included in the installation package. For more information, please refer to documentation   I am using EPM server (Self-Hosted), can I upgrade to the latest EPM agents' version? All Windows and macOS versions are supported on the legacy EPM Self-Hosted server. Note: as of December 31, 2023, CyberArk will not support EPM Self-Hosted, See End-of-Life Policy for more information   Which Control panel functions are impacted? The elevation by EPM Agent of "Add/remove applications" or "Settings/Apps/Installed apps" are impacted.
View full article
Question In an EPM elevate if necessary policy, what is the expected policy action of child processes if "include child processes" is enabled? Answer If an elevate if necessary policy has a definition which uses child processes... if the initial process launch of the parent app launches with the "allow" policy action, its children will also use that "elevate" policy action. In the vf_agent_srv.trace logs the parent process launch will show this: Action=1 (NORMAL_RUN) inheritable In the vf_agent_srv.trace logs  the child process launches will show this: Action=1 (NORMAL_RUN) inherited from parent   If an elevate if necessary policy has a definition which uses child processes... if the initial process launch of the parent app launches with the "elevate" policy action, its children will also use that "elevate" policy action. In the vf_agent_srv.trace logs the parent process launch will show this: Action=4 (ELEVATE_ON_DEMAND) inheritable In the vf_agent_srv.trace logs  the child process launches will show this: Action=4 (ELEVATE_ON_DEMAND) inherited from parent  
View full article
Question 1.Why do we only see services.msc events and not configmgrsec events? 2.Does the inbox show only the parent event when “Run as Admin” is triggered? 3.Does the customer need to manually add events based on “Service Name” in User Policies?   Answer 1.Elevate on Demand policies send inbox events only when elevation occurs. Example: services.msc was run as admin → Event logged. Child process configmgrsec.msc was run normally → No event logged. 2.Yes. If you trigger Run as Admin, the parent process event is logged. If you run the application normally, no event is logged. 3.Yes. To track specific service-related events, customers must manually add those based on the Service Name in their User Policies. Example : Please find the screenshot : service_name.png User Policies-->Service Access --> Add Service --> MSSQLSERVER    
View full article
Deploying and configuring the macOS EPM Agent. Steps This video provides a comprehensive walkthrough for installing the signed EPM package, configuring and activating the agent, and preparing files for managed deployment through the macOS MDM platform.    
View full article
Question What is the purpose of "Protect against ransomware" policy and how does it functions? There are well known applications that are showing in the events management, which is definitely not a ransomware. Answer Protect against ransomware policy detects and/or restrict unauthorized access to sensitive/protected files by unhandled applications. It does not flag anything, and the policy sends events of the unhandled applications to the events management. Before activating the Protect against ransomware policy, please ensure that the relevant applications are included in these groups: 1. Microsoft Windows Programs (Default Policies) - A group of applications that is automatically included and managed by the Protect against Ransomware policy. 2. Authorized Applications (Ransomware protection) - A group of applications that is automatically excluded from the Protect against Ransomware policy. There is also an extension option in the policy that prevents users and applications from changing values for these registry keys.
View full article
Question Are there any Limitations when using any of EPM's RestAPI features? Answer 1. Time Out when logging in Logging in process may fail due to momentarily high-server load. Should this be the case, the status code received will be 408.  What can be done?  Perform login once more. Load will eventually pass and the login process will succeed, should all proper parameters are correct. 2. Token and Parallel requests The same Token cannot be used for more then 1 parallel request. e.g: 2 Runners, 2 Shells should not use the same token to execute requests. This is relevant even in a situation in which a login is performed once, but the Token is then used in more then 1 request in parallel - this is deemed to fail - which will result in abnormal behaviors, such as: Internal Server errors (status code 500), wrong data will be received in the response, etc. What can be done?  Use different tokens to execute multiple requests. 3. Timeout of different type of requests Should a timeout be reached when one attempts to retrieve inbox events for example (Aggregated, Raw), the server will return status code 500. The cause will be an extremely large number of  unhandled events in both Privilege Management Inbox and in Application Control Inbox.  What can be done?  Use Filters to narrow down the amount of events to be retrieved from the DB in the response, to a point in which the Timeout won't be reached. 4. Login amount in SAAS vs. OnPrem/AD. In SAAS environment, user can perform login once per minute (60 seconds). In On-Premise deployments, this is not the case. 5. Maximum API Calls per API call time period The maximum allowed number of API calls per defined time period = 3 calls The period of time to limit the API calls to the maximum number allowed = 5 minutes (Note - these 2 parameters are configurable for on-premise customers under Set > Server Configuration > API limitations)  
View full article
Question Can Integrated Windows Authentication (IWA) be used with Endpoint Privilege Management (EPM) Windows sign-in? Answer No. IWA and EPM Endpoint Sign-In (ESI) are not compatible. IWA relies on an existing Active Directory (AD) user session to perform web-based authentication. EPM ESI initiates web login before the user session is available. Because of this difference in authentication flow, the two methods are not designed to work together and cannot coexist. Related Documentation: Configure Integrated Windows Authentication (IWA) Configure Endpoint Sign-In Policy User Experience: Endpoint Sign-In
View full article
Many customer support cases for EPM that involve Azure AD are not related to EPM.  For example, some customers use Azure AD or groups in advanced policy targeting, but the end-user is not logged in with an Azure AD user.  The purpose of the article is to provide a few commands to use as troubleshooting steps to gather information and possibly show if issues are outside of EPM or not. Steps Advanced Policy Targeting Check userdomain variable Run this from cmd echo %userdomain% expected outcome: Should see AzureAD If you see something else, the user may be logged in with a regular active directory user Check whoami output Run this from cmd  whoami /all Expect to see azuread\username Expect to see "NT AUTHORITY\Cloud Account Authentication" If you don't see the above, it might be an indication that the user may be logged in with a regular active directory user Note: May not see the actual Azure AD groups listed Testing if the computer/user can talk to AzureAD Run the powershell commands $path = "C:\myfolder" $permission = "AzureAD\[email protected]","FullControl","Allow" (Get-Acl $path).SetAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule $permission)) | Set-Acl $path Expected outcome: It should set the security permission on the folder AzureAD authentication Test if the computer can authenticate to AzureAD (outside of EPM) On the endpoint, run "C:\Program Files\CyberArk\Endpoint Privilege Manager\agent\vf_agent.exe" -SuspendPolicies Enter credentials of someone who can suspend policies Open file explorer and browse to c:\windows\system32 shift+right click notepad.exe > open as different user Enter user in form of azuread\[email protected] Enter credentials and see if notepad opens.  If not, the endpoint may have a problem reading the AzureAD directory, and the issue is not related to EPM. On the endpoint, run "C:\Program Files\CyberArk\Endpoint Privilege Manager\agent\vf_agent.exe" -ResumePolicies If the customer can't authenticated to AzureAD using the above step, it is not expected that they should be able to suspend policies using an Azure AD user
View full article
Recommended best practices in response to commonly asked questions for agent deployment in Windows, Mac, and Linux platforms.   Steps Frequently Asked Questions: How often should I upgrade agents? It is recommended that agents be upgraded to the latest version to benefit from new features and security fixes. Per CyberArk’s End-of-Life Policy, agents are supported for up to one year from the date of release. At a minimum agents should be upgraded once or twice a year to ensure a supported version of the agent is utilized. It is recommended to review the EPM release notes to determine if your version of the agent needs to be upgraded based on your environment. More information about our End-of-Life policy can be found here. Take a look at our nugget video on upgrading agents at scale. How do I deploy EPM agents with minimal end-user impact? Check out our Getting Started with EPM guide for recommendations to ensure a smooth implementation.  It contains a checklist and training resources to avoid any delays in getting EPM rolled out effectively. The EPM agent can be deployed through a variety of different methods (manually via the installation wizard which can be downloaded from the EPM console, CLI with a configuration file, and deployment at scale using a third-party software distribution tool such as Microsoft Intune, Microsoft System Center Configuration Manager, JAMF, Altiris, etc.) Take a look at our nugget videos on deploying QuickStart policies (Phase 1 + Phase 2) Win Agent Installation: The best method to deploy at scale is via CLI using the MsiExec.exe command which can also be configured to install the agent silently.  Once the MsiExec script is written, it can be deployed using your preferred third-party software distribution tool.  See our online documentation for information about the MsiExec command and syntax. Mac OS Agent Installation: The best method to deploy at scale is via an MDM tool such as JAMF Pro, or Microsoft Intune.  With each of these tools, you’ll need to configure a Configuration Profile that allows for EPM’s system extensions to be installed automatically without user intervention.  After the configuration profile is configured and in-place, then package up your EPM agent with the installation binary, configuration profile, sign (if necessary), then deploy via your MDM. What tools are available for troubleshooting policies? Leveraging the EPM File Tab is an effective way to proactively troubleshoot your EPM policies.  After building your policy, you can confirm if your application is being handled by the policy you just created.  For more information about enabling and using the EPM File Tab click here. Another important tool to have in your arsenal is the ShowProcInfo command which shows all the running processes on the OS.  This command shows more details about the process (process ID, session ID, etc.), file info (owner, publisher, checksum, etc.), token (user, integrity level of token, etc.), and the applied EPM policy if there is a match.  This information is valuable if your policies are not being handled as expected or more insight is needed about the application such as any child process dependencies.  Click here to learn how to enable this tool. Take a look at our nugget videos on building good definitions for Windows and MacOS.  
View full article
Please see the attached guide to successfully integrate EPM and Intune for windows.
View full article
Question What are the Required UAC Settings for EPM "Trust" policies to function properly? Answer The below UAC values, are the UAC settings required for EPM to collect events and to allow for Trusted Sources based off Digital signatures to work.   You may configure these same settings using the Local Group Policy Editor -> Security Settings -> Local Policies -> Security Options For additional information on these UAC settings please visit: Microsoft UAC Group Policy Settings and Registry Key Settings   Minimum UAC configuration for Intune Q: What are the Suggested UAC Settings for "Trust" Policies functionality? A: These are the UAC settings required for EPM to collect events and to allow for Trusted Sources based off Digital signatures to work. You may configure these settings using the Local Group Policy Editor -> Security Settings -> Local Policies -> Security Options , Or by GPO.   For additional information on these UAC settings please visit the following Microsoft KB: http://technet.microsoft.com/en-us/library/dd835564%28v=ws.10%29.aspx   Q: What are the Suggested UAC Settings? A: These are the UAC settings required for EPM to collect events and to allow for Trusted Sources based off Digital signatures to work.     You may configure these same settings using the Local Group Policy Editor -> Security Settings -> Local Policies -> Security Options For additional information on these UAC settings please visit the following Microsoft KB: http://technet.microsoft.com/en-us/library/dd835564%28v=ws.10%29.aspx
View full article
Problem: Seeing a warning in the EPM SAML configuration page indicating that the “EPM Server Certificate has expired and must be replaced”.    Solution: Seeing this warning message can be alarming but it is important to note that this warning message only applies to IdP servers that are configured to validate signed SAML assertions. If your IdP is unsigned for SAML assertion then this warning can simply be ignored. In most cases, the EPM server certificate is not used since most IdP servers do not require it.   Steps In the EPM Management console, select SAML Integration to display the SAML 2.0 Integration page. The warning described in this article appears as below.      Note that if you are using a signed certificate to validate SAML assertions then you will need to ensure your certificate is valid and installed correctly.  
View full article
Steps Refer to the doc attached to this article. It has step by step instructions on how to setup the self-signed certificate for use with the OPAG tool. There are also some general troubleshooting steps and known issues. Please be aware that this is not the only method for creating self-signed certificates, and the certificate used with OPAG does not have to be self-signed and can be obtained by other means. It just has to meet the specifications outlined in the online documentation at: https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/EPM/Server%20User%20Guide/One-time%20Run%20Authorization%20Tool.htm
View full article
Question Can domain accounts use the "Admin sign-in" feature if they are part of the local Administrators group? Answer The "Admin sign-in" feature currently supports Windows login only for local administrator accounts. This means that even if a domain account is added to the local Administrators group, it will not be able to use this feature. This is expected behavior. The feature is designed to allow local administrators to sign in directly to the device using their username and password. It does not extend this capability to domain accounts, regardless of their group membership. For domain administrator accounts, or any domain-based user, the supported method of access is through the secure sign-in flow. To enable this: The domain account must be invited to Identity, and The user must authenticate via Identity OIDC, following the same secure sign-in process used by standard users. This ensures that domain accounts are properly managed and authenticated through the Identity platform, maintaining consistency and security across all user types.
View full article
Question Why are Mac EPM agents and Windows EPM agents still sending policy audit events to the EPM Console even though policy audit has been disabled in those policies? Answer Here are two possible reasons: A) The endpoint has not received the change to the policy yet B) The agent has policy audit events queued up to upload to EPM SaaS but is limited to 200 per hour       more details: A) The endpoint has not received the change to the policy yet To confirm if the endpoint has received your change (to disable policy audit on a policy), get SupportInfo logs.  Then open the policy xml.  On a Windows endpoint it's in the trace subfolder and is named vf_policies.xml.  On a Mac it's named Policy.xml.  Search for the policy name.   In the following example ... <Policy id="36991" order="420" action="1" name="Test allow" reportUsage="2" internalType="3"> <Targets> <ApplicationGroup id="{ecc0705c-9d62-4add-93dd-dc405c4e362c}"/> <ApplicationGroup id="{8887b6d7-82a4-419d-b9cc-3ca2241c49ab}" name=""/> </Targets> </Policy>   ...reportUsage="2" means that policy audit means policy audit is disabled for this policy.  If you don't see reportUsage="2" at all, it means policy audit is enabled         B) The agent has policy audit events queued up to upload to EPM SaaS, but is limited to 200 per hour The EPM Agent has a setting which is not configurable by the customer which determines how many events can be uploaded by the agent per hour.  If you get support info logs and then look in the policy xml, you will see a section that looks like this: <MaxHourlyEvents> <PrivLack>250</PrivLack> <File>100</File> <PolicyUsage>200</PolicyUsage> <Restrict>100</Restrict> <NetAccess>500</NetAccess> </MaxHourlyEvents>   PolicyUsage setting of 200 means the endpoint can only upload 200 policy audit events per hour.  After one hour, it can upload more.  If you disable policy audit on a particular policy, this does not remove policy audit events associated with that policy from the endpoints queue of policy events it needs to upload.  They will continue to upload, 200 events at a time, until the queue is cleared.  
View full article
Functionally, this is how Policy Targeting works in general (Not just for Remove Local Admin Users feature): (Computers in this set) AND (AD/Entra ID computers and groups) AND (Users and groups) In the formula above, we see that each is AND’ed together. Now, within each of the targeting options above, they functionally OR the specific objects within them respectively and we get: (Computer1 OR Computer2 Or …) AND (Acme\comp1 OR Acme\comp2 OR …) AND (Acme\user1 OR Acme\user2 OR …) The key thing to understand is that you OR the objects within the specific target option and then those target options are AND together after. Similarly, in the 'Exclude from policy' section, each is OR’ed together.   Now, to get even deeper into how this all works from a design and workflow perspective: Computers in this set is functionally processed first and dictates which endpoints (based on agentID(s) behind the scenes) the policy is delivered to from the SaaS. This means that, if you are not included within the Computers in this set targeting, then you as the endpoint/agent don’t have knowledge of or a copy of that policy. After the endpoint receives the policies, they will assess whether they are specified in or are members of a computer group specified in the AD/Entra ID computers and groups targeting. If the endpoint/agent successfully identifies that it’s a target of the the AD/Entra ID computers and groups targeting, whether by direct membership or is part of a group defined in that targeting, then the policy is applicable for use on the endpoint. After all that is handled, when a user runs a process and the agent assesses policies to figure out which matches to handle that process, the agent will evaluate the user against the Users andgroups targeting, specified in the policies. This whole workflow and logical process is what inevitably sums to the functional AND of the policy targeting options and the functional OR of the objects within each, respectively.   To Summarize; The “Computers in this set” is working at service level, for include and exclude. It will be checked first, will send only to the relevant endpoints. The “AD/Entra ID computers and groups” and “Users and groups” are checked in the agents after the policy is received.
View full article
EPM agent logs are encrypted by default in EPM sets created after the release of EPM v23.9 (September 23). The default decryption password can be obtained as follows: In the Configuration page, make sure that Agent configuration is selected from the drop-down list. Click the More actions (...) button next to the Create custom configuration button. Select Show default support info file password. The password is displayed.   To decrypt the log, use the following command: vf_agent.exe -dsi <crptPath> <password> For example: vf_agent.exe -dsi “c:\temp\supportInfo.zip.crpt” "12345" In Mac: $ CyberArkEPM -dsi crptFilePath Password   Online help doc link here How can I change the default password? The default password can be changed as follows: In the EPM console->Advanced->Agent Configuration->Support info file password. What to do in case I forgot the decryption password? In such a case, please change the decryption password in the console, and collect the agent log again (it’s recommended to make sure that the agent received the new password by right-clicking the tray icon and select ‘Request settings’)
View full article
Question EPM Agent shows disconnected or is not visible in the Endpoints (Beta) pane. What could be causing this issue? Answer The EPM Console currently provides two interfaces for managing endpoints: My Computers (Legacy) and Endpoints (Beta). When implementing outbound firewall rules, it is essential to update your allow list to include the new EPM URLs. This ensures full functionality of the enhanced endpoint management capabilities and supports agent upgrades.   🔐An example of new required URLs for the USA Region To enable proper connectivity for EPM Agents version 24.12 and above with Endpoints Beta, the following URLs must be allowed: - https://files-na.epm.cyberark.com (new) - agents-na.epm.cyberark.com (new)   📌 Minimum Agent Version Requirement Endpoints Beta requires a minimum supported agent version. Please refer to the official documentation for details via the link below. Minimum required agent version for certain actions     🌐 Outbound Traffic Rules Ensure your network configuration aligns with CyberArk’s guidelines for outbound traffic. NOTE: If your organization uses SSL inspection, you must configure it to exclude the EPM service URLs listed in the following table. This ensures communication between EPM agents and the SaaS service. Complete documentation is available via the link below. Network Setup  
View full article
Question How do I make a custom EPM role that only allows the EPM admin the ability to run endpoint reports, but nothing else? Answer Instructions for endpoints reports only: NOTE: These instructions are just for a role that can ONLY run endpoint reports. If you need other kinds of reports, you might need to add more view-only permissions. For example, if the user needs to run policies reports, you should give the role read only access to policies. Click the drop down next to "Policies" and set to "None" If you click the plus sign next to "Reports" to expand the section, it likely does not need to be altered Click the drop down next to "Events" and set to "None" Click the drop down next to "Scan Computers" and set to "None" Click the drop down next to "Policy Coverage" and set to "None" Click the drop down next to "Computers" and set to "View Only" Click the drop down next to "Threat Intelligence New UI" and set to "None" Click the drop down next to "Policy Audit" and set to "None" Click the drop down next to "End-User UI" and set to "None" Click the drop down next to "Advanced" and set to "None" Click green "save" button in upper right to save changes Account management Right click any set where the user needs this custom role and choose "Changing bindings for set <setname>" Click the drop down next the user then choose the custom role you created Click OK
View full article
Question Why doesn’t a user immediately gain full administrative privileges after being added to the local Administrators group in Windows? Answer This behavior is expected and aligns with how Windows enforces group membership and privilege elevation. When a user is added to the local Administrators group, they do not immediately gain full administrative privileges. This is because Windows does not update the user's access token mid-session. The access token, which defines the user’s security context, is created at logon and remains fixed for the duration of the session. As a result, the user is not treated as a full administrator until they log off and log back on, at which point a new token is issued that reflects the updated group membership. Until that happens, the user is in a transitional state: they are technically a member of the Administrators group, but their current session does not carry the full administrative privileges associated with that group. This is why they are sometimes referred to as having “limited” or “deferred” admin rights during that session. You’ll also see this noted in the Computer Management console under: Local Users and Groups → Groups → [Group Name] “Changes to a user's group membership are not effective until the next time the user logs on.” This is a deliberate part of Windows security architecture. Group membership changes are only applied at the start of a new session to ensure consistency and security.
View full article
In order to use an AD account as the reconcile account for a Unix account, we need to create a second "Dummy" account to reconcile the Unix account. (NOTE: The dummy account is just an instance of the AD domain account but in the UPN format.) We will then add both this dummy account and the primary AD account to an "Account Group" (see Footnote 1 below).  We will do this so that when the primary AD account changes its own password, it will change the password for the entire group which includes the dummy account you created.  This dummy account will have the correct username for the Unix target as it will be in the UPN format ([email protected]).  Since the primary AD account remains unchanged, it will still work as intended. NOTE: It is assumed that the AD domain account can login to the Linux target and has the permissions to reset the target Linux account password.   Steps Create a platform for the dummy account: Import and duplicate the OOTB Dummy plugin here: https://community.cyberark.com/marketplace/s/#a352J000000pl70QAA-a392J000001h4SEQAY  Use this article to set extra platform parameters under “Additional Policy Settings”: https://community.cyberark.com/s/article/CPM-Dummy-Plugin-Configuration   Create the dummy account: Add a new account on the new duplicated dummy platform Username will be the UPN format ([email protected]) of the primary AD account Address can be the domain.com For the dummy account's password, retrieve the password from the primary AD account Save the dummy account    Create a password account group platform: https://docs.cyberark.com/pam-self-hosted/Latest/en/Content/PASIMP/Account-Groups.htm#Createagroupplatform   Create an account group and add the primary AD account and dummy account to it: https://docs.cyberark.com/pam-self-hosted/Latest/en/Content/PASIMP/Account-Groups.htm#Createanaccountgroup The account group now contains the primary AD account and the dummy account in the UPN format.   Associate the dummy account as the reconcile account for the target Unix account. The primary AD account will still be managed as before including password changes on the AD. These changes will now update the password object for the dummy account to keep the passwords in sync. Please note however that a reconcile on the primary AD account will now behave differently since it is in an account group.  See here: https://community.cyberark.com/s/article/00004972 *Footnote 1 - Documentation on Managing/Creating Account Groups. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Account-Groups.htm
View full article
How do I gather Support Info logs via EPM console? Other than gathering Support Info logs from the endpoint directly, you can actually generate from the EPM console. The condition is that the endpoint MUST be online. Pre-Requisite:  EPM Agents must be on 25.4 or newer in order to utilize this feature! Please note: The naming of the zip folder from this version of Support Info logs will be different from the version directly from the endpoint.  For example - If you need to do deeper investigation due to performance, using Process Monitor to record would be valuable, therefore collecting directly from the endpoint in question would be preferable. supportInfo_YYYY-MM-DDTHH_MM_SS_XXXX.zip (From EPM console) VS. VfSupInfo YYYY.MM.DD HH:MM.zip (Directly from Windows endpoint) epm-supportinfo-YYYY-MM-DD-HHMMSS-XXXXXXXXXXX.zip - (Directly from Linux endpoint) CyberArkEPMFeedback_AgentVersion_YYYY-MM-DD_HH_MM_SS.zip (Directly from macOS endpoint) The EPM console's version will not contain: System Windows Event Log (Windows) Application Windows Event Log (Windows) Process Monitoring recording session. (Windows)   Steps 1. In the EPM Console, proceed to Endpoints 2. Select a relevant endpoint then under the Agent Details tab, click "Generate support info file".  It will start the upload to EPM Console process.  This can take a few minutes to complete. 4. Once the download is ready, click Download file. Q: How do I remotely gather support data from an agent? A: There is a hidden option to allow you to remotely gather support data and do some other actions for our client agent. To access this option do the following: 1. Open you console and select “Computers” and select the “My Computers” tab. 2. Select the blank area of the tool bar. 3. Now hit “Ctrl” + “Shift” + “F12”. This will create a new tool bar called “Support”. 4. Select the machine you wish to take action on. Then select the “Support” tool bar and select what you would like to do. 5. In this example I have selected “Get Full Trace”. Doing so will open a new window and you will see a loading screen. 6. Once the trace has completed you will be prompted with a download link.
View full article
Question When a PowerShell script is executed by either Execute Script Policy or Deploy Script Policy, the script will not be executed successfully if the script includes a section where it accesses Microsoft Excel. If the script is run manually via PowerShell application in the endpoint, the script will be executed with no errors. Answer Please note that this is a bug of the Windows OS. This bug occurs specifically when running an automated PowerShell script that is accessing Microsoft Excel. Please refer to this blog for more information: Automating Excel 2007 on Windows Server 2008 64-bit The solution for this Windows bug can be changed in other OS versions, but it works and have been tested on Windows 10. The solution goes as follows: 1. In the endpoint, create the following directories: C:\Windows\SysWOW64\config\systemprofile\Desktop C:\Windows\System32\config\systemprofile\Desktop  2. For the created Desktop directories, add Full control permissions for the relevant user. 3. Configure a new Execute Script policy and check if it works by request settings at the affected endpoint. For Deploy Script policy, execute the script from the Control Panel.
View full article
Question What is the proper way to copy a LCD Secret Key from one LCD policy to another? Answer Go to the existing Credentials Rotation Policy and go to the "Password Vault" section. Click "Show" first.  This is sometimes required to have the key copy properly. Click "Copy"   Then in the destination Credentials Rotation Policy click Paste    
View full article
Question Where Does EPM Get Serial Number Data From? Answer Some endpoints monitored by EPM Agents may display serial numbers with multiple or unexpected values. For example, a device might report a serial number like /35LYX14/VNWFV003AF0618/ in EPM, while a direct WMI query on the device returns 35LYX14 .   Root Cause: EPM collects serial number data from Windows Management Instrumentation (WMI). Specifically, it may pull from either: BIOS information ( Win32_BIOS ) Motherboard information ( Win32_BaseBoard ) In cases where the serial number appears longer or includes slashes, it is typically sourced from the motherboard’s WMI data, which may include additional identifiers or formatting. This discrepancy can affect client health reporting and asset tracking systems that rely on consistent serial number values.   Recommendation: If consistent serial number formatting is required, consider standardizing on a specific WMI class (e.g., BIOS) for reporting, or implement post-processing logic to normalize the values.
View full article
This article is to help when a Linux agent install fails with the following error:   Error in PREIN scriptlet in rpm package cyberark-epm Failed: cyberark-epm-25.3.0-3407.x86_64 Error: Transaction failed 2025-06-02 08:14:51 Error: EPM 25.3.0.3407 RPM install failed. Steps 1) If possible, try to check if the issue could be preventing all installs, not just EPM agent installs. If so, issue is likely not with the EPM agent installer but rather something that needs to be worked on by the customer's endpoint team.   2) How to collect further logs (RHEL 8 instructions): run install... dnf install -y --rpmverbosity=debug epm-rhel8.x86_64.rpm 2>&1 | tee send_to_rd.output capture any terminal output during the failure ask customer to upload send_to_rd.output to case upload /var/log/dnf.log upload /var/log/dnf.rpm.log upload /var/log/messages
View full article
Question What is the potential impact of the  vf_policies.xml  file size on network performance? Answer The size of the  vf_policies.xml  policy file can significantly influence network load, especially in environments with a large number of connected agents. The potential network impact can be estimated using the following formula: Estimated Network Load = Policy File Size × Number of Connected Agents Example Calculation: If the policy file is 1 MB in size (which is larger than average but not the largest observed), and there are 10,000 connected agents, the total data transferred would be approximately: 1 MB × 10,000 agents = ~10 GB On a gigabit LAN, this volume of data could theoretically be transmitted in about 8 seconds, assuming ideal conditions and no other competing traffic. Mitigation Mechanisms: To prevent network congestion and ensure smoother performance, both the server and agent components include built-in mechanisms that stagger agent requests over a longer time window. This spreading technique helps distribute the load more evenly and avoids sudden spikes in bandwidth consumption. Best Practices: Monitor policy file size growth over time. Regularly audit and optimize policy content to avoid unnecessary bloat. Ensure network infrastructure is scaled appropriately for the number of agents and expected policy distribution frequency.
View full article
Question The Memory Restriction setting, located under Policy > Options > Application Access Control > Memory of other processes > Restrict, is designed to control how applications interact with the memory space of other processes. Answer This setting is intended to block write operations to the memory of other processes. Read operations are not restricted by this policy. This distinction ensures that diagnostic or monitoring tools that require memory reads can function as expected, while preventing potentially malicious or unauthorized memory modifications. Implementation Notes: The restriction applies at the driver level and is enforced by the Endpoint Privilege Management (EPM) Agent. Applications attempting to write to the memory of another process will be blocked when this policy is enabled. Applications performing memory reads will not be blocked under this setting. Best Practices: Use this setting to enhance security by preventing memory tampering between processes. Combine with other Application Access Control policies for comprehensive protection. Regularly review policy effectiveness and update configurations as needed.
View full article
How to Remove EPM Agent Proxy Settings? Steps Method 1: Reinstall the Agent Without Proxy Arguments Reinstall the EPM Agent without including any proxy-related arguments in the installation command. This will reset the agent’s configuration, including proxy settings, to default. Note: This method will preserve the agent ID if installed over the existing installation. However, if you uninstall and then reinstall, a new agent ID will be generated, which may impact policy associations    Method 2: Manually Remove Proxy Settings from the Windows Registry You can manually remove the proxy configuration by editing the Windows Registry. This method is useful when reinstallation is not feasible. Registry Keys to Check and Remove: HKEY_LOCAL_MACHINE\SOFTWARE\Viewfinity\Agent\Proxy* Important: Editing the registry requires administrative privileges. You may also need elevation rights depending on your organization's policy for  regedit . Caution: Always back up the registry before making changes. Incorrect modifications can affect system stability.
View full article
Question Why is Windows Enterprise multi-session detected as a Server OS? Answer In the EPM console, Windows Enterprise multi-session may appear as a Server operating system. This is expected behavior based on how the OS identifies itself at the system level.   Windows Enterprise multi-session is a virtualized edition of Windows Enterprise, designed specifically for use in Azure Virtual Desktop environments. One of the key technical distinctions is that it reports its  ProductType  as  3 —the same value used by Windows Server editions. This classification is intentional and serves several purposes: Compatibility with RDSH tooling: It ensures the OS works seamlessly with Remote Desktop Session Host (RDSH) management tools. Support for multi-session-aware applications: Applications designed for multi-user environments can function correctly. System-level optimizations: The OS benefits from performance tuning typically reserved for server-class systems. Because EPM relies on system-level identifiers to classify operating systems, it reflects this  ProductType  value in the console. As a result, Windows Enterprise multi-session is displayed as a Server OS.   This behavior does not indicate a misconfiguration or issue with EPM. It is a direct consequence of how the OS is designed to report itself for compatibility and performance reasons.   For more details, see the official Microsoft documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-multisession-faq
View full article
  • 234 Posts
  • 19 Subscriptions
Top Liked Posts in LIVEcommunity Article
Top Liked Authors