Trend 10.6 failing AV check after upgrading Pulse to 5.0R1
I have remote users running Trend 10.6 and are fine on Pulse 3.1. When they upgrade to 5.0R1 they cannot connected. The message they get says they don't have AV installed. If they downgrade to Pulse 3.1 they can get back in. I'm running 8.0R1 on a SA 6500. And my ESAP file is at 2.5.4.
I can't reproduce this in my lab or on our production box that users connect to. But the logs show where these people are failing. Any Ideas?
Re: Trend 10.6 failing AV check after upgrading Pulse to 5.0R1
There is a fix related to Trend in ESAP 2.6.0. Our experience with 2.5.4 was that it would not detect updated definitions - but the problem would only be exposed 5 days after the software was installed. 5 days is the period we consider definitions as up-to-date so it recognised the initial file date but not the updates. Updating to 2.6.0 fixed our issue.