cancel
Showing results for 
Search instead for 
Did you mean: 

Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

Highlighted
Frequent Contributor

Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

We have a couple of Windows 7 users that are running Trend Micro Titanium Maximum Security 6.0.2012. Host Checker is reporting that the virus definitions are out-of-date despite the fact the the definitions are current. We are running ESAP 2.5.1 on an SA-6500 with firmware 7.4r8. Our Host Checker policy is set to require virus definitions no older than 5 days from any supported AV product.

 

Has anyone else experienced this? If so, is there a workaround or fix other than creating a separate rule just for this product?

 

I don't find anything release in release notes for ESAP 2.5.2.

 

Thanks.

4 REPLIES 4
Highlighted
Super Contributor

Re: Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

They can try turning off UAC settings on the machine.

Regards,

Jay

Highlighted
Frequent Contributor

Re: Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

Thanks.

Unfortunately, for the two open cases I had, both users found their own solution before I could try disabling UAC. One upgraded to Trend 7 which seems to work properly. The other moved to a different AV product.

If I get any more complaints for Trend 6, I will try turning off UAC and let you know.

Highlighted
Frequent Contributor

Re: Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

The user that upgraded to Trend 7 reported that all was well for one week but now the problem has returned - definitions reporting as out-of-date. I had him try disabling UAC but that didn't resolve the problem.

I have confirmed ESAP 2.5.2 and ESAP 2.5.3 did not resolve the problem for Trend 6.

Any other ideas?

Anyone else experiencing this problem?

Highlighted
Frequent Contributor

Re: Trend Micro Titanium Maximum Security 6 and ESAP 2.5.1

I downloaded the trial version of Trend 7. Interestingly, it work for the first 5 days then Pulse began to report that the definitions were out-of-date. Not coincidentally, our HC policy requires definitions to be no older than 5 days.

The application shows that the smart scan pattern file is being updated and, in fact, is a bit newer than the version listed in the latest epupdate file.

Any thoughts?