Hello!

We've taken over a customer who has ClamWin on their Windows Servers. When we updated the definition database, the application required a restart.

Planning the maintenance of this customer's infrastructure, it would make it easier for us to have an idea how often this will happen.

So I'm asking you, who've been working with ClamWin for a while, how often updates in your experience will require a restart of a Windows Server?

Your input is very much appreciated, thanks for taking time reading the post!

I don't recommend using ClamWin on any server because the Clam AV signatures/scan engine it uses has too many false positive detections and can kill the system. Look around these forums to see what happened last week. Use ClamWin only as a last resort/backup AV, and set it to report--not quarantine/remove. You need to use a real-time antivirus from a real organization--not one maintained by volunteers. Serve data is too important for ClamWin!

Regards,

Hm, interesting - thank you GuitarBob. There's an awful lot we like to do an need to do with this environment, but we don't want to exhaust the customer right away, so to speak. I value your input very much!