NetSHield...

[WillShakespeare]

Will my problems ever end???
Now, I have placed the most recent update file, and the update.ini in a folder on the ePO server. I have created tasks to update on my clients and servers. Servers use netshield, clients virusscan. When the task runs for the clients, they are updated as required, no problems... but when I run the same task on the servers, they don't update.
When I try to force update through NetShield console, I get an error reading destination folder, which is exactly the same as for the clients...
If I run the .exe update on the server, even remotely using the file on the ePO server, it runs fine, and updates, but the task doesn't work...
Any ideas?

Will

 

[ChrisHirst]

Hi Will

I found the answer to this problem is to set the task manager service logon on each NT or Win2k client machine to a domain account with at least Domain Admin permissions. With Win9x the updates run no matter what because no account checking takes place. My method is to have a user account set up purely for Anti Virus logon ( call it AVService say) and give it elevated priviledges. The only time this will cause a problem is on an undocked laptop as the service cannot find the account SID.

Chris.

 

[WillShakespeare]

Hi Chris,

Thanks for all the info you have given me... I found out the problem I was having... the ePO NetShield 4.5 tasks do not use the update.ini file. They use the delta.ini file and the dat*.zip file. I managed to work this out when I finally figured out where the log files were.
Anyway, the delta.ini file, and the dat*.zip file only updates the DAT file, not the ENG. This is annoying as the process seems to work, and running the sdat*.exe file works on each server, so why can't NAI produce an sdat .ini file to update both engine and dat file???? This is crazy! I figure I might try renaming the update.ini file to delta.ini, and seeing if the sdat*.exe file gets used by the NetShield update process.
So anyway, my point is I have managed to get Netshield on my servers (via the ePO server console) to automatically update their respective DAT files, but not the engine... without any scripts. (Though I am likely to use your nai.bat ftp script for the time being until I can automate this all through ePO as I should be able to!)

Once again thanks, and if you can offer assistance in using ePO as my Virus Solution, and not simply part of the managing process, I'd like to hear more... Isn't that what ePO is supposed to be designed for?

 

[ChrisHirst]

Hi Will

Same here on ePO we have only just upgraded to AVD from TVD when the licence renewal came up and as yet have not got to grips with ePO, so I am still using my tried and trusted method. But as I start to use ePO some info will be posted up.

Chris

 

[WillShakespeare]

Yes... I will post what I can too. In the mean time, I just created an ftp script based on yours that is more appropriate to our infrastructure, and it works fine, thanks!
But we are still having a few teething problems, as you may see on my other post...

Will