Jump to content

T3chGuy007

Members
  • Content Count

    24
  • Joined

  • Last visited

Everything posted by T3chGuy007

  1. I went ahead and installed the CU21 update and I have not encountered any issues.
  2. Hello. I have ESMC v7.2.1266.0 running with Microsoft SQL Server 2017 (RT Express Edition (64-bit) v14.0.2027.2. I'm doing some maintenance in our environment and I see that SQL Server 2017 CU21 was released on 7/1/2020. The version I'm running (v14.0.2027.2) was released 7/9/2019. My question is am I able to upgrade our SQL to CU21 without causing any major issues with ESET? I believe it should be okay, but I wanted to see if anyone else has upgraded their DB or if the version of ESMC has be using SQL v14.0.2027.2. Thanks! https://support.microsoft.com/en-us/help/4047329 https://support.microsoft.com/en-us/help/4557397/cumulative-update-21-for-sql-server-2017
  3. I was finally able to reboot the server with this upgrade problem, but that didn't fix the issue. I tried to uninstall the agent, but it failed with the same "unable to stop service" error. HIPS is disabled on this server, so I created a new policy with HIPS enabled (so I wouldn't affect other servers) and applied it to the server with the error. Once HIPS was enabled, I rebooted and then tried running the agent_x64.msi file again. This time, the upgrade succeeded with no errors. I'm not sure why HIPS had to be enabled, but it seems to have fixed my issue.
  4. HIPS is permanently disabled and always has been disabled on the server. Unfortunately, I have to wait until after hours to reboot it. I was hoping there was a way to do the upgrade without rebooting. I haven't had to reboot other devices when upgrading the agent.
  5. Hello. I just wanted to confirm that it was our recently installed WatchGuard that was preventing our clients from doing module updates. I believe it was related to the WatchGuard proxy. Thanks for the help!
  6. Hello. I have a server that is running ESET File Security 7.1.2010.0 and ESET Management Agent 7.1.717.0. I've upgrade ESMC to 7.2.1266.0 so I'm trying to upgrade the agent on the server to 7.2.1266.0. However, when I run a Security Management Center Components Upgrade task, it never finishes. Other systems finish within a few minutes. If I download agent_x64.msi from ESET's website and try to do the install, it fails too. See attached log. I believe it has something to do with trying to stop/upgrade the management service. The log file also lists that it's unable to stop the HIPS service, but HIPS is disabled on this server. Any suggestions? Thanks! output.log
  7. Ok, I tried a few of those hostnames and I can ping each of them. Wouldn't that mean I should be able to download module updates? I ran a tracert to us-update.eset.com and I made it out of environment so could it still be our WatchGuard?
  8. Ahh, I'm glad you said that because my co-worker just implemented a new WatchGuard appliance. Are there URLs that need to be whitelisted? Right now, I can ping update.eset.com, but the updates still fail. Thanks!
  9. Hello. I noticed several of my clients, which are running Endpoint Security 7.3.2032.0, are providing an error when updating modules. My first thought was to upgrade the clients to 7.3.2036.0, but this did not fix the issue. I then found a forum post that states changing the regular automatic update schedule to 10 mins from 60 mins as well as changing the skipped task option to "As soon as possible" fixed the issue, but it did not work for me. In my case, I can see the clients automatically checking for updates, but each time it comes back with an error of "Module update failed. Download interrupted". I've restarted the PCs, tried kicking off a module update task in ESMC, as well as updating manually on each client, but I get the same error each time. I read that you have to uninstall/reinstall the product, but this seems excessive. I have opened a case with support, but I thought I would try here as well. Anyone else with this problem?
×
×
  • Create New...