Problems after Update to DHS Compliant Version

[mbaerwolff]

Since the update of the Anti-Malware Engine, we have had massive problems with various programs. In some cases, .exe files that previously worked without any problems are moved to quarantine. However, this does not affect all clients. The exceptions that we define do not have the desired effect.
Do any of you have the same effects or possible recommended settings?

[G_W_Albrecht]

That is the right way to do that 😎

[the_rock]

I tested E88.60 myself in the lab and was fine, but again, thats only couple machines, so not anything close to number you have.

Andy

[J_B]

Has anyone noticed that the E88.32 client doesn't automatically run a scan after the client installs/upgrades?

We're moving 5000 E1 clients to the E2 client and Check Point have recommended that we upgrade to the E88.32 version and not the latest E88.60 version.

It's not a show stopper, but it just appears to the user that there's an issue after the upgrade as the yellow padlock flashes because a scan hasn't ran.  We've left devices for over 24 hours and the scan still hasn't kicked in, whereas on our E1 clients a scan always ran after client installation.

Within the Anti-Malware policy we have it set to 'Run initial scan after Anti-Malware blade installation'