- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
05-26-2026 07:33 AM
Hello Team,
I have reviewed multiple documents and articles regarding agent corruption issues, but I have not found a clear explanation of why the agents are becoming corrupted. We use JAMF (MDM) to deploy agents to end-user machines and have created a smart group to identify devices missing server connections. I consistently see around 300 machines in that group.
All of these machines have the required EPM prerequisite profiles. We also created an Extension Attribute (EA) in JAMF to validate the network setup connection based on the CyberArk documentation (https://docs.cyberark.com/epm/latest/en/content/installation/network-setup.htm). Everything appears to be configured correctly.
However, it is not ideal to reinstall EPM repeatedly. Do you have any suggestions for resolving this more effectively? Are there any automation strategies you follow, or has anyone else experienced similar issues?
06-04-2026 06:37 AM
This is a fairly common pattern with EPM + JAMF deployments on macOS, and what you’re describing usually isn’t “random corruption”—it’s typically one (or a combination) of the following:
Agent/service drift rather than actual corruption
What often looks like corruption is actually:
Result: device shows as “missing server connection” even though installation is intact.
Network / connectivity edge cases
Even if your EA checks pass, intermittent issues can still break agent state:
Important nuance:
EPM agents are very sensitive to transient network failures during registration/heartbeat, not just permanent misconfiguration.
macOS background process termination
macOS can:
If the EPM agent:
→ it can appear “corrupted” but is actually stalled
Upgrade / policy drift via JAMF
Common hidden issue:
JAMF doesn’t always ensure:
“clean, atomic application state”
Implement a “lightweight agent reset” (NOT full reinstall)
Create a JAMF policy that:
#!/bin/bash
# Restart EPM services
launchctl kickstart -k system/com.cyberark.epm
# OR fallback
pkill -f epm
sleep 5
# Restart service (adjust path if needed)
launchctl load /Library/LaunchDaemons/com.cyberark.epm.plist
# Force reconnect if supported
/Library/Application\ Support/CyberArk/EPM/epmcli reconnect
Much faster than reinstall
Fixes ~70–80% of “corruption” cases in practice
06-04-2026 08:14 AM
Thank you for the guidance @Robert Stothard . Please let me know if I am misunderstanding or missing anything.
We tested the suggested reset commands, but the sample service and plist names do not exist on our macOS EPM agent.
The following commands failed:
launchctl kickstart -k system/com.cyberark.epm
launchctl load /Library/LaunchDaemons/com.cyberark.epm.plist
On our test Mac, EPM is installed with the bundle ID: `com.cyberark.CyberArkEPM`.
The CyberArk LaunchDaemons present are:
- `/Library/LaunchDaemons/com.cyberark.CyberArkEPMNetworkSession.plist`
- `/Library/LaunchDaemons/com.cyberark.CyberArkEPMScriptSandbox.plist`
The output of `launchctl print system` shows:
- `com.cyberark.CyberArkEPMNetworkSession`
- `com.cyberark.CyberArkEPMScriptSandbox`
- `NetworkExtension.com.cyberark.CyberArkEPMNetworkExtension.26.5.0.106`
- `DF8U2CCCD8.com.cyberark.CyberArkEPMEndpointSecurityExtension`
Could you please confirm the supported lightweight reset commands for the macOS agent version 26.5.0.106?
Specifically, should we restart using the following command?
sudo launchctl kickstart -k system/com.cyberark.CyberArkEPMNetworkSession
If a reload is necessary, should we use:
sudo launchctl bootstrap system /Library/LaunchDaemons/com.cyberark.CyberArkEPMNetworkSession.plist
Instead of the older `launchctl load` command?
Additionally, should we make any changes to the `CyberArkEPMScriptSandbox` or the System/Network Extensions, or should we leave them untouched?
Lastly, is there an official reconnect command for this version? The suggested `epmcli reconnect` command returned a permission denied error.
We are trying to build a JAMF self-healing policy for devices with a “missing server connection” issue, and we want to ensure we use only CyberArk-supported commands.
06-29-2026 07:48 AM
Hello @Robert Stothard ,
Can I please get an update on this? I opened a support case and received the following response:
"EPM does not offer or support any such mechanism or script as you are describing (JAMF or otherwise)."
Could you please help me understand if there is any other recommended approach to handle this scenario? We are trying to identify and remediate broken EPM agents without having to uninstall and reinstall them every time. Any guidance or best practices would be greatly appreciated.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

