Campbell IT

Absolutely! Most IT Admins know their environment well enough to know which machines are not up to date. I want my ESET product to tell me when there is a problem with ESET.

Terrific. Honestly, the constant upgrades are getting tiresome. It's almost a full time job to keep up with ESET upgrades.

We have about 20 Windows 2012 R2 servers that are running version 7.0 that need to be upgraded to 7.3 before the upcoming EOL date. Scheduling downtime for these servers is a challenge. If we push the upgrades to these servers without rebooting, what are the consequences of delaying the reboot? Will they be totally unprotected until the reboot? Any other issues we should be concerned about? Thanks.

I don't seem to be able to stack dynamic groups. Can you elaborate, or post a link to a KB explaining this?

I'm trying to get a dynamic group configured that includes all desktops in a certain subnet, but excludes a handful of logged in users, namely members of our IT team. What I am trying to accomplish is to get these desktops into a group so that we can apply a weekly reboot task to them as our users never want to reboot, preventing us from pushing updates. So far, I can get all of the desktops in the subnet included in the group, but I cannot seem to exclude myself (or other IT team members). Any help is appreciated.

Yes, I understand. That's why I am trying to upgrade to at least 7.3, but I have not been successful. Is there any solution?

We have a few legacy servers that can't be migrated to a newer OS and cannot be decommissioned yet. One such server is Microsoft Windows Server 2008 Standard Service Pack 2 64 bit with all Windows updates which is currently running 7.2.12004.2. I cannot install 7.3.12002.0 on it. The installer gives me a message about an incompatible OS. Any ideas how I can protect this server? Thank you.

That would explain why I see changes this morning in the console. I had about 25 machines left to upgrade to get rid of this message and this morning, on most of them, the alert is gone.

It's out now. I was in the process of updating all of our workstations to 7.3.2044 and now all of a sudden this morning, 7.3 has been replaced by 8.0. I sure wish ESET would let us choose which version we want to install when we click the "Update ESET Products" button. At least leave the latest version and one version prior to that. I think we're all smart enough to know the difference and can make that decision for ourselves. I had to create an installation task to finish my rollout instead of being able to click the update button.

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.

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?

Thanks. It was set properly, but not forced.

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.

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.

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.