Jump to content

robscott27

Members
  • Posts

    4
  • Joined

  • Last visited

About robscott27

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. Unfortunately, this may be exactly what you end up doing. It's what I've had to do (see my above posts). Still doing actually. ESET Tech Support told me to uninstall the current version on the client machine and install the latest downloadable package, which was 6.1.222. I've also found that a reinstall of the ESET remote agent was also needed. I've got about 60-70 clients myself - only a third of yours - but it's rather time consuming. I mean, it fixes the problem and they're activated again, but still. I still don't have a clear explanation of WHY they suddenly deactivated. Only that they did and now need to be entirely re-installed.
  2. In my case, all my clients are Endpoint Antivirus clients and the license is for Endpoint Antivirus. In fact, until about a week ago, they were all just fine (in terms of licenses and activations) and had been fine since about mid-January of 2015.
  3. I have/had this same sort of issue with version 6 as well. Only my ERA server is on a Windows 2008 machine. All the clients that the remote agent is going to are WIndows 7 based machines. Two things I've noticed - whether they help or not, that'll be up to you: 1. The Windows firewall, if on, will block the install. Turning it off will *sometimes* allow it to install, but will still fail due to #2 below 2. We have a Barracuda Web Filter 610 installed which blocks web access if the user has not authenticated against Active Directory. If the client machine (and possibly the ERA server, I'm still testing this one out) does not have web access, the remote agent won't install. The error generated on the backend ends up being: Failed to synchronize package repository. More often than not, the firewall is the cause - at least in my experiences with my machines. Not sure if that helps at all, but figured I'd contribute as I've experienced this sort of thing as well.
  4. I've got the same thing happening with my clients. The only problem is, pushing another product activation to them doesn't resolve the problem. I've got a 75 seat license and thus far am only using 50 of them. Oddly though, in the "Used Licenses" area of the client details screen via the ERA, the expiration date is what it should be and not the 12/31/69 date some folks seem to have. Any ideas as to a fix? These clients won't update until they've gotten their activation back. Thanks!
×
×
  • Create New...