Endpoint Protection Suite Adding ???? Scans

Avast Business Avast Endpoint Protection
1

I’m seeing nearly 30 ? ? ? ? scans showing up on all our managed clients.

https://dl.dropboxusercontent.com/u/8315780/avast1.JPG

We are running client version 8.0.1609 and eac version 8.0.405

We had a Daily Quick Scan and a Weekly Full Scan setup. I’ve deleted both and recreated the Daily Quick Scan but the ??? scans still exist.

https://dl.dropboxusercontent.com/u/8315780/avast2.JPG

Anyone else seeing this issue?

2

What does it say under details ?

3

A basic, all harddisks scan.

https://dl.dropboxusercontent.com/u/8315780/avast4.JPG

https://dl.dropboxusercontent.com/u/8315780/avast3.JPG

4

Looks to me there was a hiccup somewhere damaging the database with the scans.
I don’t know how to correct it other than removing all scans manually.

Could be there is another way though.

5

Hello,

we have same problem like you. Now I have on my client about 300 “???” scans.
1 year ago I tried made ticket on support, but without success. I think that they don’t try to help. Support is horrible.
“???” scans appear on clients in our network casually. I can’t find context about some action and appearing new “???” test.
I have suspicion that the problem is in communication clients and management server. We have more than 1000 clients. AEA server have problem. The console is mostly freezes and not possible to login. When I want to go into I must restart service “avast! Enterprise Administration Server”, but this service can’t kill task “entServer.exe”. I must kill the task manualy and then I can start the service. After this procedure usually sql take 25% CPU for tens minutes and console is so slow.
I tried installed new AEA server with clean DB and reinstalled clients to new AEA server. But when on AEA 500+ clients started same problems (freezes AEA console, “???” scan on clients).

How many clients do you have?

MZ

6

Thanks guys. I appreciate your input.

MZ - We have about 800 clients. We had noticed the AEA console freezing up at times. Occasionally it wouldn’t even let us log into it however, a reboot of the server would fix that. My next thought was to build out a new server with a clean db to see if that helped but from your experience that didn’t help.