Jump to content


  • Content Count

  • Joined

Everything posted by katycomputersystems

  1. Our MacOS clients running ESET Endpoint Security 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 within the computer description page, this is inconsistent and makes no sense, it was a bad idea and should be fixed.
  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, currently if you want to grow quickly, you will need to make a deal with one of the big RMM players to sell your products at a 90% discount. If you get a few more RMM features, I am convinced more MSPs and IT departments will agree with my world view embracing a simpler, more efficient set of tools to serve their clients.
  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 manual intervention, I would appreciate eset Remote Administrator's assistance in helping us identify the issue. I suspect the issue is logged somewhere - that is after all how you are determining that the system is not up to date. 2. If Security column only refers to a ESET product, what is the point of this setting? 3. You are breaking my heart, I still love ESET Remote Administrator, but would be much happier if I had the ability to easily set commonly used tasks. Currently, it is a multi-step process. 4. Hmm - our numbering may be out of sync, that will be great if you facilitate favorite tasks, the other request is just bonus 5. Yes, I would like some file, any text file really that can be edited & merged back in. Merging may be problematic, so export in text/XML format then import back into new policy would be fine. BTW there is a bad flaw in the policy management system. If you edit an Endpoint policy and make the mistake of changing it to Remote Agent policy, you loose all your Endpoint policy settings. I cursed your developers over this issue. Won't make that mistake again :-( 6. I only use ScreenConnect. Thank you for your help.
  16. Marcos: Thanks. It's a mix of W7 & W10 causing the update issue. The notification is valuable, we want it to continue, but need a bit more information to help us resolve the alert. I changed the non-ESET application setting - looking forward to getting this information, it affects less than 10% of our clients, but the information will be helpful. I changed this setting & waited until the workstation checking in a couple of times, I still don't see the Security Product listed on this page: Is it on another page, the client's configuration is showing the new setting: Client has McAfee:
  17. A few items for consideration: 1. When ERA says "Operating system is not up to date", provide more information. We have several workstations that say OS not up to date, we update, restart, update, restart, still "OS not up to date" 2. The computer list shows ESET products in the "Security Product" column, it would be nice if it showed other third party products when no ESET product is on the machine. 3. I would like to customize the action menus. For example "Send Wake-up Call" & "Connect" are useless to us since 95% of our workstations are off-site. 3a. It would be terrific if the action menus included a Favorite Tasks option that would function like "Last Used tasks" but allow us to define a few (10) of our favorite tasks. 4. Ability to export policy to XML file, then import that XML file. ERA is an amazingly powerful tool, frequently, I know there has to be a setting in there somewhere, but I cannot find it or perhaps, I want to add 20 items, it would be a heck of lot easier if I could export to XML, view/edit XML, then merge it back in. 5. Any integration you could provide with ScreenConnect would be nice. For example I'd like to have the "Connect" action menu remote me into the client's workstation using ScreenConnect.
  • Create New...