Jump to content

Campbell IT

Members
  • Content Count

    64
  • Joined

Everything posted by Campbell IT

  1. Well, you have a bug then, because we have had several machines that I did not upgrade manually, but they upgraded on their own. I discovered this because I noticed there was an alert on a machine. The alert was that the machine needed to reboot to complete an upgrade. I had not upgraded the machine manually and I am the only one who administers the ESET server. I asked the user to reboot and after they did, the version was upgraded to 7.2.2055. This was while we were on ESMC 7.1.
  2. Well, I have 3 machines that until late last week, were on 7.2.2055 that are now on 7.3.2032. One of these machines is my workstation. All 3 of them had ZERO shutdowns after our weekly scan until yesterday when I was sitting in front my computer and watched it with my own two eyes as a prompt came up telling me it was going to shut down after the scan. I was able to cancel it, but the other two machines shut down as I was testing to see what would happen and I did not intervene. I get that there is a bug in 7.3.2032. So tell me how upgrading to 7.3.2032 did not cause the issue?
  3. I just experienced this on my machine. Fortunately, I was in the office today, so I was able to stop it from rebooting. My big concern is that we have had a few computers automatically upgrade themselves without any intervention on our part. Is there a way I can prevent any other machines from automatically upgrading? I currently have 3 machines on 7.3 and would like to keep it that way until this issue is fixed. I have a lot of people working remotely and not much manpower available to turn machines back on.
  4. I got a message that I could not send a PM to you. It doesn't matter, though. I was successful with my upgrade after I stopped the EraServerSvc service. Now I get to re-learn how to deploy the Agent.
  5. How do I send the log to you? It has hostname and IP address info in it, which I do not want to make public.
  6. The clients are checking in every 5 minutes. AD synchronization only occurs once a day.
  7. I reviewed the logs myself and found these entries: Error 1921. Service 'ESET Security Management Center Server' (EraServerSvc) could not be stopped. Verify that you have sufficient privileges to stop system services. Info 1920. Service 'ESET Security Management Center Server' (EraServerSvc) failed to start. Verify that you have sufficient privileges to start system services. I do have sufficient privileges. Should I manually stop the service before I attempt the upgrade?
  8. It failed a the ESMC upgrade. I tried to send you a PM with the logs attached, but it said you can't receive messages. How do I securely upload logs to you?
  9. I attempted to upgrade our ESMC 7.1 server to 7.2 by downloading the installer, running it on the server and choosing "Upgrade All Components". It upgraded SQL Express OK, then it took quite a while on the next step and then failed with a 1603 and 1708 error. Prior tests of this process on a snaphshot copy of our server worked flawlessly. Any help is appreciated.
  10. Please have an option to block automatic upgrades as you have described above. While it sounds good in principle, unless reboots are forced, you could end up with computers that have pending reboots for weeks. We struggle with getting our users to log off, let alone reboot. Plus, if there is an issue with an upgrade in our environment, we would need to be able to prevent the upgrade from happening on more computers. Thanks.
  11. I had several machines detect HTML/ScrInject.B and for weeks, the detections would show up as unresolved. I finally got some time where the user would let me work on the system for a couple of hours and the only way I could find to actually get the detections to resolve was to run an in-depth scan with cleaning. It baffles me because these detections were reported after a smart scan. If there is some other easy (albeit, not intuitive) way do resolve detections, I would love to hear it. Thanks.
  12. I have found after working with ESMC 7.x for some time that the only way to permanently resolve detections is to run an In-depth scan with cleaning after a detection has occurred. Is there a way to configure ESMC so that when a desktop reports s detection, an in-depth scan with cleaning is scheduled automatically?
  13. "Last successful update" would work fine. In the meantime, I will adjust the settings you outlined above. Again, thanks for listening to my feedback.
  14. Thank you for looking into the suggestion. We only have a few computers that would have multiple users logged in at one time. In 5.x, the logged in user shows up as "Multiple users". It doesn't happen often, so it wouldn't be a problem for us. To clarify - I'm asking to have the option to display this info in the computer table. Either have it off by default, but allow admins to enable it or vice-versa. Regarding the Detection engine, what I am looking for (and what we used the VSDB info for) is to be able to see at a quick glance, which machines are not updated. I suppose that ESMC will flag machines in red if they have an issue, but then we have to drill down to find out what is going on. Sometimes it's as simple as the machine being turned off, which we don't need to investigate.
  15. Description: Add fields to Computers list Detail: In ESET ERA 5.x you could customize the fields in the list of computers. It made it very easy to see what user is logged into a particular machine because you could add a custom field with the username. In ESMC, you have to click on the machine, then click Show Details and then scroll down to Users to see who is logged in. The same goes for the Virus DB version (now called Detection Engine in ESMC). Please give administrators the option to make the console less click intensive. We need to be able to find info quickly without having to click and scroll so much. Thanks for listening.
×
×
  • Create New...