This is something which concerns me a bit, as I did not know about this until I just decided to log onto the UTM and look at Endpoint Protection. I got no message at all from the client I was on that this happened.
The item in red specifically.
Endpoint Protection in the UTM had an alert next to my computer name, it actually showed online finally, (haha) but with this alert, so I pulled the log on my client computer and low and behold I am seeing this now.
My Dashboard also showed two items blocked, but I was not ever told on the client like I was on version 10.0, nor does the client (or log) show anything.
I never had this error before, nor has it ever shown up prior to this release of the Endpoint client.
Also as a note, not sure where the log date/time is getting its information from, but that log was not pulled today at 2:51 PM, it was at 8:51 AM (central time) on Nov 8th. :)
Code:
****************** Sophos Anti-Virus Log - 11/8/2012 2:51:04 PM **************
20121106 230618 Using detection data version 4.83G (detection engine 3.37.2). This version can detect 4204139 items.
20121106 230618 User (NT AUTHORITY\LOCAL SERVICE) has started on-access scanning for this machine.
20121106 230620 Web Protection is no longer functional. The filtering driver has been bypassed or unloaded.
20121107 001153 User (NT AUTHORITY\SYSTEM) has stopped on-access scanning for this machine.
20121107 001154 Using detection data version 4.83G (detection engine 3.37.2). This version can detect 4204147 items.Endpoint Protection in the UTM had an alert next to my computer name, it actually showed online finally, (haha) but with this alert, so I pulled the log on my client computer and low and behold I am seeing this now.
My Dashboard also showed two items blocked, but I was not ever told on the client like I was on version 10.0, nor does the client (or log) show anything.
I never had this error before, nor has it ever shown up prior to this release of the Endpoint client.
Also as a note, not sure where the log date/time is getting its information from, but that log was not pulled today at 2:51 PM, it was at 8:51 AM (central time) on Nov 8th. :)