When we had gpa 5.2.6 and cb v184.108.40.206xx only the defintion was broken. When cb went to 220.127.116.111 the real time scanning broke. With gpa 5.2.9-35 for us, it fixed the real time scan and the definition when using cb 18.104.22.1681. Seems every time cb makes a version , opswat needs to make changes that affects their clients like cisco anyconnect and palo alto
Our Organization has been encountering this well over 2 years...multiple cases opened. Every-time there is a new release of Carbon Black Defense addressing enhancements, bug fixes, etc - we can't adopt due to the Global Protect Agent failing to detect.
What is interesting is even if you go into GP- HIP Object Configuration for Anti Malware and disable\set to none on the Virus Definition Date, Product Version, and Last Scan time, users will still fail due to the 1970 date that many are plagued with.
We have test users with the same Model PC, Same Image, Same Versions, Same Portals and Gateways and they connect fine...others do not. The kicker is sometimes after broken users "reboot 3-4x" their signature changes from 1970 to present date. It extremely sporadic.
This has occurred on previous versions, however currently on GP 5.2.9 and on 5.2.10 with CB 22.214.171.1248 for Windows during our testing.
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!