Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


MarathonIT last won the day on October 7 2016

MarathonIT had the most liked content!

About MarathonIT

  • Rank

Profile Information

  • Location
  1. After removing some adware (and maybe something worse), I rebooted and ran the Windows All-in-One Repair from tweaking dot com. For those who aren't familiar with it, it restores many different Windows components to their "out of the box" state, the idea being that they return these areas to the condition they were in when installed. It refreshes such things as registry key permissions, file/folder default permissions, repairs winsock, windows update, and a bunch of other stuff. The idea is that you don't know what little things are changed when you get infected with something, and removing malware doesn't necessarily return the Windows configuration to its normal state. Anyway, after running this and rebooting, the system is now working properly again, without periodic crashing of SysInspector.
  2. Just had a thought - how is Sysinspector triggered? It appears to be crashing every 15 minutes or so, but I can't find anything in the Windows task scheduler. While I figure out what a real solution to this issue is, can I disable it to avoid all the annoying errors the user is having to endure?
  3. ESET Endpoint AV ver 5.0.2265.0 Windows 7 Pro, SP1 Every 15 minutes or so: "System Analyzer Tool has stopped working" Tried uninstalling and reinstalling. Scanned with a number of malware removal tools. Removed some stuff, rebooted, but issue persists. Tempted to wave my hands in the air and whine about what a lousy product this is, etc. etc., but it's the first time I've had any real problems with ESET, and can't find the same issue out there experienced by someone else. After reinstalling EEAV and removing malware, what else can a guy do? Not eager to schedule a half a day to completely rebuild the computer, just to get the AV product working. Any other suggestions? Thx
  4. Thanks Michal for locating the installation files for me. Been doing them automatically for so long, I completely forgot about all that. Turns out that, even though it had long been uninstalled, the ESET installation script detected Norton Internet Security on the computer. All I had to do was delete the empty registry key: HKLM\Software\Norton After that, the installation was successful. Amazing how much time I spent going through multiple documents step by step, trying to find out what was wrong. Question: if ESET can point out what's wrong when I install the .msi locally on the computer, why can't it report that back through a push installation, instead of the generic 1603 error code, which just means, "It failed"? tmuster2k - looks like the "ignoreconflicts" switch could be dangerous, but it is good to know that such a thing exists. If you're sure there isn't a competitive product installed, that switch would sure save time. Thanks all...
  5. In ERA5, under Actions, Manage Packages. Choose Language, then Product, then it says a username and password are required to download. The only reason I am downloading to create a package is that one computer refuses to accept a remote install, and sometimes installing locally tells me the reason. I wish the installer would product more useful errors than just "1603" - I've been through the KB docs and can't figure out what's wrong. I know it's not the ESET product, but something dumb in the target computer, but I think ESET could be more specific in its objection to installing on it. Anyway, if I do need a password to install this .msi file, I need to know where to find it. Thanks
  6. Using ERA5 with MSP licensing. I put a license key into the ESET MSP Utility and it picks up my license username (that thing starting with EAV) from the ESET servers and my licenses are available for my use. Problem is, I need that EAV name and a password to download installers from ESET - I have no idea what the password is. Seems silly that I should need it and not have it, but where is it? I looked through all the license management pages, through the MSU and the ERA. Can't find it. Am I chasing my tail? Can someone please point me in the right direction? Thanks.
  7. After re-reading the article on the ERA proxy, I not only see that it's optional, but also that it's a good idea to use it in certain situations. So, I withdraw that part of my question above.
  8. Where to start? Been using ERA5 and EAV5 for a while, using MSP licensing obtained through my former RMM provider (Labtech). I'm changing RMM and opened an ESET MSP account. All good so far - everyone I've encountered so far has been great. I figure I should be changing to ERA6, as ERA5 is likely going to be dropped and I'll be in trouble. I like ERA5, but life goes on... Been having trouble understanding the upgrade/migration process, the limitations of the policy migrations and the ERA Proxy piece. I have about 100 endpoints out there all "reporting" to my ERA5 server. I have a port forwarded on the router the server is behind and that's all I needed to do. Since I have no faith in my ability to migrate my ERA5 server (mainly because I don't understand the explanation of the policy migration limitations), I wondered about merely building an ERA6 server and using the ERA5 server to push out a policy change to have my endpoints report to the new server. Can that work? I can rebuild the policies - they weren't put together very well anyway. Another question: I understand that each V5 endpoint will need the agent installed to report to the new server. I believe my RMM software will help me with that - or maybe I could use it to just push out V6 clients to upgrade my V5's? And finally: what's up with this ERA proxy piece? One document says I "may" use it, I think I read somewhere else that it needs to be installed on a server in the client environment... Sounds kind of tedious: I have one client with 25 endpoints, but they are spread out over 10 locations. I'm going to have to put a server in each small office, just to run an ERA proxy? ERA6 frankly looks a bit scary to me - I'm seeing a bunch of pieces that need to be deployed and configured. Looks really finicky. I only have about 100 endpoints currently, but they are spread out all over the place. If I have to install or configure all these little bits on each client individually, I might be better off finding a product that isn't so hard to deploy. On the other hand, since I like the ESET product so much, maybe I just need some advice on how to proceed. Appreciate any input. I am reading, and finding lots of docs, but they aren't always that clear. Maybe hearing from someone who's been through all this will help me get it all straight in my mind. Thx
  9. I think I have a good grasp on how to do things with the Policy Manager. However, I am wondering how everyone uses it: do you create an entire set of policies and manually populate them, depending on the needs of the endpoints? Seems to me that the biggest reason this would be useful would be for exclusions lists, depending on which systems have which software. However, I believe I have read somewhere that Exclusions Lists can't be merged. Seems like a pretty obvious feature not to be included. What other tips can anyone provide for effective use of policies? While I am generally pretty happy with the ERA console and its documentation, I wish there was a bit more written in a "Best Practices" or "Effective Use of..." type of article. Any hints anyone can provide would be appreciated. Thanks. (Currently using ERA 5.0.x)
  10. I tried this from a different angle. Obviously I misunderstood something along the way. I like the ESET management products, but am not what I'd call an expert yet. Earlier, I created a new Configuration Task, changing only the setting that told the clients to report to my ERAS. I saved the .xml and sent out the task, receiving only the message: "No task for this client". I am wondering if I had somehow misconfigured the configuration file and effectively pushed out no changes. Just now, I requested the configuration information from one of the client machines, and Saved and Opened it with configuration editor. Changed the settings for Remote Admin and saved, then pushed THAT one out. It was successful for all 5 client machines, and I am now able to delete them and not have them come back to my client list after 10 minutes. Anyway, not sure what I did wrong, but it's all better!
  11. Since I no longer have a relationship with the client, I no longer have the ability to login/configure their systems. A push uninstall yields this: "Could not set up IPC connection to target computer (SC error code 6, GLE error code 53)" Anyway, I am not so much interested in uninstalling the ESET as I am removing them as systems reporting to MY ERAS. Seems to me that, in a situation like this, where a client no longer pays for their licensing, an MSP should at least be able to cut off their administration access. This would set the ESET to want them that their licensing has expired, making them more likely to contact ESET and buy licensing, rather than shop for another product. Why should I pay for them to continuously use my licensing, when they no longer pay me for it? The ERAS should allow me to block systems from reporting to my server, thereby cutting off management and licensing...
  12. I don't know that they installed a different brand of AV, just that they no longer deal with my company. As a result, I would like their systems removed from my ERA, so I can use the licenses for paying clients. I will have to research how to create an "Uninstall" task - not seeing that in the ERA under "New Task".
  13. I am having a problem "getting rid of" a few client systems belonging to a former client. They installed new AV software on most of their computers, but I still have 5 of them (all Windows 7) who are showing in the ERA (Version 5x). I tried to push out a task, changing their configuration to "Unmanaged" but the Task always ends in error, saying: "No task for this client". I have tried merely deleting these clients manually, but they always reappear after a short while. I no long have a relationship with this company and am no longer charging them for these licenses. How can I free these MSP licenses up for use elsewhere? Thanks.
  14. Funny, the ESET specialist at LabTech told me that system variables (e.g. %windir%) are NOT supported. Should try to get a test virus and try it myself I guess. Another thing I wondered about was whether or not wildcards could be used throughout the path. For example, C:\users\*\AppData\Local\Packages\*.* In any event, it would be nice to see something on this topic in the documentation - that way the software engineers could list what they accept or not for the reference of us all (or at least those of us who check the documentation occasionally)...
  • Create New...