Hi amjad.ra2, First you can check debuglog.log file and search for messages from OpswatImcColData It will give times (in ms) of was the time each policy takes to evaluate. Example 'OpswatImcColData' Result of Antivirus data to monitor(Successfully called: CheckRTPState : Time Taken:23.8515, Successfully called: GetDataFileTime : Time Taken:10.7346, Successfully called: GetDataFileVersion : Time Taken:10.5312, Call failed: GetDataFileSignatures : Error Desc : Not supported, Call failed: IsUpdateInProgress : Error Desc : Not supported, Successfully called: IsFullScanInProgress : Time Taken:263.504, ) Regarding the timming, you can not have a rule of thumb for that, because it is heavly influenced by resources consumption in the client machine and by the caching mechanisms of pulse secure. I'm doing tests for active patch policies, and depending of the end user computer and day, I've results as you, it fails by time out, other times, minutes to complete, other times just few seconds. Chers,
... View more