Jump to content

katycomputersystems

Members
  • Content Count

    64
  • Joined

  • Last visited

Profile Information

  • Location
    USA

Recent Profile Visitors

1,086 profile views
  1. Our MacOS clients running ESET Endpoint Security 6.9.200.0 are getting a Legacy System Extension popup. When should we expect an update to clear this issue?
  2. Thanks Michal, I deactivated pc47006, waited until it showed up as a problem in ESMC, then activated it in ESMC, same issue: At this point, I'll ignore the issue and see what if any impact it has on our clients.
  3. Perfect - using this report I was able to deactivate the seat after determining its origin.
  4. PS: He's in my database, however a few searches yielded no useful (based on my current knowledge) information:
  5. In msp.eset.com I see an unrecognized device: So, I go to ESMC & search for this computer: I am rewarded with "No results found": How do I track down this device?
  6. More weirdness 46740 is a multiple, then it isn't:
  7. Nearly all "Multiple Devices" represent the same machine with different versions of Endpoint Security. A few are clearly different machines, each with a different computer name, installed at different times etc. Very confusing....
  8. I migrated to msp.eset.com when I go to the activated_units page, I find many of my endpoints seem to be using two licenses for the same product, it looks like this: Can someone explain what this means? Should I go through and deactivate the duplicates? Is there some automated way to clean this mess?
  9. I am trying to build a "ESMC Agent Upgrade for MacOS" Client Task. When I select the item I want to install there is no MacOS client - am I doing something wrong, or is there no way to upgrade the ESMC MacOS client?
  10. I didn't see the move to group option, it's somewhat better than the drag computer into group approach. Not having move to group in details is a workflow issue. Ordinarily, when adding a computer to ESMC, we run the installer, the computer shows up in a default group with only its name in the description field. We open details, edit the name and (until now) change its group to an appropriate group, click OK and we are done. The new way of doing things adds a step, every step creates the opportunity for an error to occur. Besides, there is no reason for us to edit the static group's name
  11. Description: Change parent group within computer details Detail: In ERA you could change the parent group when viewing details. Now, if you select parent group, you are prompted to rename the parent group, this is something that is rarely done. In ESMC, you change parent group by dragging the computer into a new static group, I am not a fan of that approach.
  12. In our environment, it is rare that an endpoint is renamed, however I wouldn't want that to initiate a name change in ESMC.
  13. "Send Wake Up Call" works well on local network, not so well in the field. It would be great if could use the command line to prompt ERA Agent to phone home. We'd put the command in our ScreenConnect toolbox & issue command as appropriate. Currently, we have ESET phoning home every minute, I would like to drop that to every hour, but can't afford to do so while getting things setup.
  14. BTW, it might help to understand how I envision use of ERA, I manage a small MSP, we have a few hundred endpoints, many will stipulate that we should have an official RMM & PSA tool, I disagree. I find that between ERA & ScreenConnect we can efficiently serve our clients. So, many of my comments reflect that desire to have ERA include features that are typically found in a RMM tool, this may be unfair to your developers, but if we can have a few more features, I am convinced your sales & marketers will be delighted. Furthermore it will give ESET more control over your destiny,
  15. @MichalJ Thanks for your comments, yes we are a MSP, though our world view is similar to an IT department of a large organization. For example, a hospital would organize their departments in a manner similar to how we view independent customers. 1. We are using eset, WuInstall and abc-update to keep Windows up to date, of course W10 attempts to keep itself updated on its own. Our preference is to update as soon as Microsoft releases updates. The problem I have is that I cannot seem to clear the "Update Needed" flag in eset, I assume that means that there is a missing update that requires
×
×
  • Create New...