ok I guess no one pays attention to the eset group anymore so I will throw this out to everyone...

Ok I am sure that some of you have dealt with the eset 4812 update issue.

My question is simple. How do I clear the cache on my client computers from the remote admin counsel? I really don’t want to have to go to every machine to do this and if I have to I am going to be rather upset. I am also going to assume that by clearing the cache on every machine, removing the 4812 from the server and rebooting it will fix this issue.

If you dealt with this issue how did you correct it? All of my clients are stuck at 4812 or 4813?

The one problem with Eset I have found is the upgrade version process. You have to uninstall the old one before installing an upgraded version. Fortunately the Remote Admin console makes it fairly easy to do. Update your install packages first, then use the Remote Install module to uninstall, reboot, then reinstall, reboot. . Takes time but the results are usually worth it.

Scott how did you avoid that virus defenition? If you auto update your virus definitions then you should have gotten the 4812 defention? Unless your update schedule just skipped over it. ESET was pretty quick about getting an update out once they realized the 4812 update was pooched.

Basically messed things up so that it wouldnt update your virus def beyond the 4812. I have my server set to check for new virus defs every 4hours. And it seems I grabbed that def and passed it to my clients. So all of My clients are stuck at either 4812 or 4813 at the moment. Even an uninstall and re-install didnt fix the issue.

Now I can understand things like this happening. ESET did get a handle on it very quickly, within 4 hours or so. What I am a bit miffed about is that I cant find anything on the ESET site on how to fix this issue. I am sure the support ticket will tell me to uninstall and re-install. That is one of their favorit fixes it seems.

The one problem with Eset I have found is the upgrade version process. You have to uninstall the old one before installing an upgraded version. Fortunately the Remote Admin console makes it fairly easy to do. Update your install packages first, then use the Remote Install module to uninstall, reboot, then reinstall, reboot. . Takes time but the results are usually worth it.