Jump to content

Jboring

Members
  • Posts

    9
  • Joined

  • Last visited

About Jboring

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've modified my template to match the one in the KB, hopefully that fixes the issue.
  2. Here's how the template is set up:
  3. Description: Static group cloning Detail: Allow for a static group to be cloned, to duplicate the contained static/dynamic group structure but not duplicating the agents assigned to the original group. This would make setup for an MSP much easier. Setting up a static group for each of our clients, then dynamic groups in each to separate workstations/servers was a huge pain in the butt. Description: Dynamic template operations for public IP Detail: Unless I'm completely missing it, I don't think there's a way to make a dynamic group filtering for a specific external IP as you could with ESET 5's console. This is also useful for MSP setup when sorting out workstation machines that don't have a unique workgroup name.
  4. I am experiencing some weirdness with dynamic groups. My first issue is that I have a dynamic group set up for machines missing Endpoint Antivirus, with a client task set to deploy EAV when a machine joins the group. Despite only ever seeing machines missing EAV listed in this group, a couple hundred endpoints with existing EAV installs have upgraded themselves through this client task somehow. With a couple of clients having very low bandwidth, I want to control when updates are rolled out. Could my group template be improved somehow maybe? (using Computer.Managed products mask currently). The second issue is that for some of my dynamic groups, they do not include agents that have been offline for longer than a couple of weeks.
  5. The majority of these appear to be in sort of a half-installed state, so I can't open up the GUI. Today I found that I could remove the ekrn service registry key, reboot, then use the stand-alone installer to get 6.6.2072 working, at least on the machines I've tried it on.
  6. The new patch has thankfully fixed the majority of our broken endpoints. Unfortunately, I've got a decent chunk of 6.2068 installs I can't get rid of on remote machines (would take weeks to do each machine individually with the safe-mode uninstaller). The problem is a registry key that refuses to be removed. HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ekrn.exe Anyone have a way around this?
  7. Some info on a current broken machine : web seat ID: 2174d941-554e-4aa0-a6f3-a325b74f4f09 public lic: 3AB-9X7-57A upgraded from older 6.6 to 6.6.2068 on Dec 21st registry keys for username/password don't exist at all , license file does exist in the programdata folder 'your license file does not contain a username/password' error on the machine, 'ESET livegrid is not accessable' error in ERA web console.
  8. I haven't used any offline license files yet. The affected machines are on a license with public ID of 3AB-6JS-RPN. With the upgrade to ESET 6, our licensing apparently needed to be modified in some fashion, so as of today I've been moving everything to the new licenses. Maybe something is up with the old license?. The majority of the 6.6.2068 machines are stuck on the old license (3AB-6JS-RPN) , however the few unaffected 6.2068 machines took the new license and are working without any issues.
  9. Same issue here for the majority of machines I've upgraded to 6.6.2068. So far I haven't found a way to roll these machines back to the previous version without doing the removal tool in safe mode (uninstallation fails normally), which doesn't help with a couple hundred machines. Activation tasks fail on all affected machines. I can remove a license from these machines from the web console, however they still display as currently having an active license in the web console.
×
×
  • Create New...