hello list,

Windows Server 2003 -- (terminal services enabled)

Updated all servers to 0.93 Clamwin. Now scheduled scans fail to run. I deleted all settings ,and recreated the scheduled scans but still all fail to run at night. Is there anyway of troubleshooting this? Of course the system logs do not show a thing in regards to Clamwin "trying" to run.I even tried logging into the server console to create the scan jobs as admin,and still no work. Would I be better of creating scan jobs via the native Windows "scheduled taks" GUI? I'm thinking this is an terminal services /(installer) prob?
Any ideas?

Thanks,

Barry Cisna

Just adding this to the already item i posted. If I create a scheduled scan of Clamwin, if I am physically logged in( via remote desktop ),to the server,the scheduled scan will start and run, untill I log out of the server. At that point the started scan dies? I tried this on three servers Windows 2003 server with SP1.If I am NOT remote desktoped into the server as userxyz,who created the scheduled scan the scheduled scan never starts?
Hope this may help someone troubleshoot the situation. As I mentioned earlier I created a scheduled scan right at the server console as well ( not logged into the domain) as admin and no scheduled scans will start( unless I am logged intot he server console as admin). I am thinking I am going to have to setup scheduled scans via the native Windows scheduled jobs GUI.

Thanks,

Barry

clamwin has not been designed as a server scanner. Schedules are managed by clamtray.exe, a user needs to be logged on and clamtray.exe running for a scheduled scan to occur. You need to use windows task scheduler and clamscan.exe for that. There are quite a few posts on this subject in the forum