We have weekly task created thru EPO 5.1.1 (build 357) which starts FULL SCAN.
Client's McAfee Agent version: 184.108.40.2066
Client's McAfee VirusScan version: 8.8.0 (220.127.116.115); patch 6
The thing is the we are experiencing problem on one of the laptops.
The full scan is scheduled at 3.00 AM, and this laptop is durring that time outside company LAN, and when he turn ON his laptop in the morning this full Access starts automatically which is not a desired behavour.
The full scan task doesn't have "run missed task enabled" so we don't understand why the task runs.
Solved! Go to Solution.
HI I've been away or I would have answered you earlier.
I was advised the issue is with the 5.0.1 and 5.0.2 agents and that I could go back to using the 4.8 agent which doesnt have this issue.
This of course is no use for windows 10 that needs the 5.0.2 agent.
The data points for investigating this behavior are not straight to just share over the forums.
I suggest contacting Support in order to look into this particular client's configuration, looking at what is configured locally as well what it is receiving from ePO.
Some things come to mind as plausible scenarios to explore -
- a second task exists which is running
- the task has an older configuration and has not received the new task configuration
- a bug with the Agent, running a task when missed even if not configured to do so
My overnight scans for a site with MA 5.0.2, VSE p5 and ePO 5.3 don't start as scheduled they start when you boot the PC, for all 350 users.
I've had a case logged for a week that someone is ignoring.
welcome to the club
Very odd different MA ePO and VSE patch, exact same issue.
I've got 5.1.1 (357) and 5.3.0 (400) servers with MA 4.8 and 5.0.1 and no issue but I kept them at VSE p4.
Im still chasing a reply with any information from an engineer . Hopefully my SAM can shake loose a reply.
If I get more info I will; post back as it may relate.
Got an answer..............
MA v5.x agents don't like the hibernation you get with win8 etc and kick in the task as if it was a missed task.
Its raised with Engineering.. .
Now I know what to look for I can find some 8.1 machines with hibernation on my epo5.1.1 with 5.0.1 aswell.
This week I got that same behaviour cause the agent Support recommendation was update to the 5.0.2 or go back to 4.8 in order to see if the same issue is still happening