I get bugged constantly by this message in the alerts, perhaps because I’m scanning too frequently, or because I don’t understand the alert process, or because I’m just easily irritated.
Trend Micro OfficeScan Client was not up-to-date on {machine name}
For instance, today I first updated everyone’s Officescan (good practice in case Mr. Murphy shows up during the upgrade). Then I went through a version upgrade of the Antivirus server. During this upgrade and subsequent rollout of 10.5 to the workstations, Spiceworks ran the usual scan. What did I get… a barrage of alerts.
In an ideal world, I’d go running to find a grace period in the alert settings (much like the concept of setting the alert to 10% of drive space remaining, instead of the default of 20% (or perhaps I have that backwards?)). I’d hope to be able to have it let the computers slide for 2 or 3 days before labeling them as delinquents.
Any suggestions?
1 Spice up
I believe SW gets the up-to-date/not-up-to-date info through WMI from the A/V application. SW gets that information better from Trend Micro Officescan with 5.0 than it did in 4.7.
Perhaps you could check with a WMI query to see if a client is reporting back that the A/V is up-to-date or not.
I’ve found that this topic is an on-going issue for ages.
http://community.spiceworks.com/topic/761 documents the fact that I’m not alone. By the time that I check the Trend Micro screens a few hours later, it’s all cleared up (presumably in the meantime). Yeah, I can go and check my Trend Micro screens, but it would be nice to have it working properly, instead of highlighting when it’s behind by a pattern file for 20 minutes.
