merickson

Is there any follow-up from this topic? I just had this problem start randomly on half of my clients. I've added an activation task that seemed to fix it until a reboot of the client. This is what the clients show from the remote admin console: Public License ID : ######### Product Name : ESET Endpoint Antivirus for Windows Expiration Date : 1969 Dec 31 17:59:59 Activated by ERA : Yes Managed by ERA : Yes

I had this same problem until I created another policy just for the agent to check in every 60 minutes. I think it downloads the policy at this 60 minute interval, then applies it, then checks back. The whole process seemed to take hours for my clients as well. So far I have 2 policies per workstation, one for the antivirus and one for the agent. All good so far. Good luck, -Mark

I can confirm that rcraig's suggestion worked great! Thank you very much! Steps taken: mysql -u root -p grant SUPER on *.* to 'era'@'localhost' identified by 'PASSWORD'; (I only have one thing using this database, so I used *.* instead of era_db. Substitute the password of course.) ./Server-Linux-x86_64.sh runs with no errors now. -Mark

Hello all, Any idea how to upgrade the OVA to the latest version? I saw a post about this new OVA version being released. I already have this deployed and everything running great... however I really need to upgrade because of this new fix: (Improved: You can disable Windows Security Center monitoring of Antivirus and Firewall, and System Updates settings). It's driving me nuts right now. I attempted to upgrade my install by downloading the latest Linux installer for 6.1.28.0, Server-Linux-x86_64.sh. Upon executing it, it fails with a 1910: Error occured while preparing the database upgrade. It also breaks the server. When I look at /var/log/eset/RemoteAdministrator/EraServerInstaller.log, it does have an indication of the problem: "Access denied; you need (at least one of) the SUPER privilege(s) for this operation" That's the extent of my technically abilities for now, and I think I'll just wait until someone helps out here. If anyone else has attempted this, I have figured out that by running /root/eset_installers/Server-Linux-x86_64-6.1.336.0.sh again will fix everything the way it was before. Thanks for any info! -Mark