Skip to main content
Solved

The VPN client agent was unable to set up monitoring of the VPN profile files

  • February 24, 2025
  • 3 replies
  • 92 views

BookMac
Forum|alt.badge.img+9

Hello everyone! Since 12/14/25 we have been receiving the message “The VPN client agent was unable to set up monitoring of the VPN profile files” every few seconds. It doesn't matter whether VPN is connected or not. It feels like the message only comes when you open the Finder and then you can't get rid of it. Reinstalling the same version fixes the problem. Since Friday we have activated version 5.1.7.80 for the zero touch deployment. So yesterday I activated version 5.1.6.103 again. When you connect to the VPN for the first time, the app is updated to 5.1.7.80. Today I have the first client installed with version 5.1.6.103. Since it was connected, it also automatically updated to 5.1.7.80. So it can't be my newly created 5.1.7.80 pkg. maybe it's because of macOS 15.3.1? Have you ever seen this?

 

 

Best answer by BookMac

I was also able to test the problem on Sonoma. Simply deleting the /opt/cisco/secureclient/vpn/profile folder and rebooting is enough. Then the error occurs. During the installation process, I removed the deletion of the folder before distributing the RAVPN_IPSEC.xml, and now the RAVPN_IPSEC.xml is distributed first, followed by the Cisco Secure Client.

3 replies

sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • February 24, 2025

@BookMac If you haven't already you should open a support case with Cisco as this appears to be an issue with the Cisco software rather than an issue deploying or configuring it via Jamf Pro.


AJPinto
Forum|alt.badge.img+26
  • Legendary Contributor
  • February 24, 2025

I second @sdagley, this is something you should raise a case with Cisco over. Even if it was a problem with the Configuration Profiles Jamf is deploying, Cisco would be the ones to tell you what is wrong and how to fix it.


BookMac
Forum|alt.badge.img+9
  • Author
  • Jamf Heroes
  • Answer
  • May 13, 2025

I was also able to test the problem on Sonoma. Simply deleting the /opt/cisco/secureclient/vpn/profile folder and rebooting is enough. Then the error occurs. During the installation process, I removed the deletion of the folder before distributing the RAVPN_IPSEC.xml, and now the RAVPN_IPSEC.xml is distributed first, followed by the Cisco Secure Client.