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.