• Content count

  • Joined

  • Last visited

  1. Up until no only safe mode repair to the previous good version has been completely successful for us. What a time waster.
  2. Restarts do not fix this in spite of meeting the said criteria.
  3. 6.6.2072 is a no-go for our still affected machines. Does ESET have any plans to issue an update that can actually fix the issue, or are the rest of us SOL and left with safe mode uninstalls with the uninstall tool as our only hope here?
  4. Rebooting my machine got the system tray icon back and no module errors, We have the client password protected so users cannot modify anything, normally when uninstalling, we enter this password and uninstall works. Sadly on my system it fails, so i may need to try the Safe Mode uninstaller as the client will not open or populate the system tray. Rebooting the other system and trying another push, and even an uninstall thru ERA still fails on each attempt.
  5. I deactivated one of the affected machines in ELA, rebooted the machine and tried to push the new client via ERA, it fails. I downloaded the updated client to my machine, which is one of the borked 6.6.2068 machines and ran it as admin, it gets most of the way through and throws the error "Service "ESET Service" (ekrn) could not be deleted. Verify that you have sufficient privileges to remove system services."
  6. Moving existing server to the cloud

    Thats what started the confusion, lol! Thanks Marcos can you please clarify regarding my concerns above?
  7. Moving existing server to the cloud

    So internally now we are IP, after the move we will be, when I look at the Policies on ERA I have the ESET Remote Administrator Agent>Our Company Default Agent Policy, and I also have one in ESET Endpoint for Windows.Antivirus policy. In the first, I can edit a server list that is currently empty. Do I add the new IP here, and should I also add the current IP as well? (not sure why its blank). In the second, not sure where if at all I should be looking to edit to add the new IP. Or am I looking in the wrong place? Also, I see a My Profile listed in the settings but nowhere can I find where to audit this profile.
  8. Moving existing server to the cloud

    Thanks rekun, looking into this. We have the new IP I think I can add to the Agent Server list in the main Agent Policy, yes? Apologies I dont spend alot of time in there.
  9. We are going to use Veeam to "vmotion" our ERA server that is currently a virtual machine to a cloud provider off premises. I've only see KB articles discussing migrating with multiple servers and updating certs across them. I think the only real change will be to just the IP address for the server in the new location. Will the Endpoint Antivirus clients on premises see the server after the IP change? If not what is the solution without having to add more ERA servers?
  10. Can a license.lf file be copied to a machine that is missing it?
  11. My deactivated system showed up immediately in ERA, ran the activation job and activation failed on the client. If I manually run updates on the client it sits there checking and doesn't finish. The only working option was a system rollback. However that across all our affected systems means alot of downtime for productive users and a couple weeks IT busy work, we simply dont have that option at this time.
  12. Thanks Marcos, we tried deactivation based on the notes here but still have the issue. As others have pointed out some of these systems show good on the console while they are not. We anxiously await a fix!
  13. On a side note, before getting this info here, an uninstall failed from Control Panel on a 7 machine and a system restore got the machine back to pre update state.
  14. We have this issue also with about 40 systems, sometimes I can manually apply the license and sometimes it reverts to the Livegrid and activation errors and has the no license listed. If I manually activate its ok somewhat but still get the module error, and then it reverts again. ESET needs to step up and get this sorted ASAP, manual Safe Mode uninstall is not something we have the resources for even on 40 machines.