Hi all,

I have just installed ClamWin & Clam Sentinel in a university but seem to be encountering the same issue on all hosts.

When I install both bits of software, I configure them so that they do not require any interaction from users. However, each time a new user logs in to a machine, Clam Sentinel resets to default which makes it ask the user which disks to scan.

Is there anyway I can make the settings stay the same for every user that logs into a system?

Each installation of ClamWin and Clam Sentinel is for an individual computer. Clam Sentinel does support the scanning of networked drives, but there is no central ability for network management on either program.

Clam Sentinel tends to be a bit aggressive on heuristic detection and tends to have some false positives on dll files and other files (including setup/install files) that are "sloppy" and that do not use professional programming and system registration practices. I suggest that you set up a central download folder (if possible), and verify all downloads that are detected with Virus Total before they are installed. I know this isn't a good practice, but to minimize false positives in Clam Sentinel, I have personally whitelisted all dll files in my two Win 8 programs folders from Sentinel scans--if it can detect/quarantine the primary malicious executable that calls a dll file, everything will be okay. There is also not much malware in the program folders (maybe except for a true file infecting virus, but you don't see many of them any more).

If possible, for the best protection you should also use an on-access, real-time AV along with ClamWin/Clam Sentinel. MS Windows Defender is available for use on small networks with 10 or less stations and works well with ClamWin/Clam Sentinel if you whitelist the clamtmp temporary scan files and every exe file in the ClamWin/Clam Sentinel program folders.

Thank you for using ClamWin and Clam Sentinel.

Regards,

It seems to be the installation itself. When Clam Sentinel installs it creates a folder in Appdata to store the configuration file, when a new user logs in, it creates a new configuration file in that users app data directory, which means Sentinel will go back to default settings.

If I was able to get Sentinel to install its configuration file somewhere outside of the users directory, that would work.

Any advice on this?

Thanks!

So the problem is really the Clam Sentinel installation? It looks like the only way to do that is to change the Sentinel installation code on a network. Could you do something there with a redirection script?

Regards,