Remote chest

[cfikes_buna]

I don't guess anyone has heard anything new with this issue yet have they? I was hoping to replace sophos with avast for my school, but if this problem cannot be resolved, I don't believe this will work.

avast, please give us a work around.

[Avosec-UK]

I don't guess anyone has heard anything new with this issue yet have they? I was hoping to replace sophos with avast for my school, but if this problem cannot be resolved, I don't believe this will work.

avast, please give us a work around.

You can use the aswChest application in C:\Program Files\AVAST Software\Enterprise Administration.

Just type the name/IP address of the managed machine and the avast! client password and you should be able to change the contents of the virus chest remotely.

[cfikes_buna]

THANK YOU SO MUCH ! ! ! ! !
That worked.

[siny]

I don't guess anyone has heard anything new with this issue yet have they? I was hoping to replace sophos with avast for my school, but if this problem cannot be resolved, I don't believe this will work.

avast, please give us a work around.

You can use the aswChest application in C:\Program Files\AVAST Software\Enterprise Administration.

Just type the name/IP address of the managed machine and the avast! client password and you should be able to change the contents of the virus chest remotely.

So what is the difference between right click -> Connect to Virus Chest and this? I see that the same program is being invoked, only with "wrong" arguments. And it does not remember previously typed addresses, so I have to type them all over again, which totally defeats the purpose of central management! Is this so hard to fix in Enterprise Console?

Anyway, thanks for a half fix, but I would really like to see this (better) integrated ...

Best regards,
Siniša Bandin