This content has been marked as final. Show 5 replies
You could use the System Compliance Profile to do this. Create a rule which checks for a running McShield service and let this check run regularly as an SCP Scan task.
But is there anyone who can give an explanation for the fact that ePo is giving the wrong properties at first?
What do you mean about "shwoing the real state". As far as I can remember there is no "scanner service is running" property in the system properties in ePO 3.6.1.
When I look at the General setting of an Workstation (WS) is see the 'right settings'.
WS seems to be up to date. (See picture).
But the strange thing is, that when I take a look at the WS itself, it shows an disabled on-access scan and often a not up to date virusscanner.
Only when I choose 'Send Agent WakeUp Call' and check 'get full product properties' I get
the 'real settings'. Showing me a lower szDATversion and engine Version.
Isn't there a way to automate this? And why aren't the properties showing up correct?
You are running an unsupported version of Virusscan. Virusscan 7.1 reached end-of-life at december 2007 (http://www.mcafee.com/us/enterprise/support/customer_service/end_life.html). This means McAfee does not test this release with new DAT or engine versions or McAfee agents.
As this could lead to Virusses not being detected or such problems as you had described I would strongly recommend upgrading to at least Virusscan 8.0 or the newest version 8.5. This can be done in place and, if you have a valid support contract, free of charge.