Jump to content

T3chGuy007

Members
  • Posts

    74
  • Joined

  • Last visited

  • Days Won

    1

T3chGuy007 last won the day on January 26 2022

T3chGuy007 had the most liked content!

About T3chGuy007

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Redeploying a new agent without having to uninstall the old agent fixed the issue. All of my clients are reporting again. Thanks for the quick help!
  2. Do you mean logging into ESET PROTECT and then going to Installers and creating a new agent only installer? Should I have to uninstall the old agent from the clients first?
  3. Hello. I upgraded to ESET PROTECT 10.1 this morning, and all went well. When I logged back into ESET PROTECT, I had a notice that Apache Tomcat was outdated, so I upgraded it to 9.0.76. I then started to upgrade all of my clients to the latest ESET Management Agent (10.1.1288.0) and the majority of my clients upgraded without any issue. However, I have around 20 clients that have lost connection to the server and have not reported in over an hour. I checked the status.html on one of the PCs and I've attached the error in this post. All of my clients were reporting prior to the upgrade, so I'm not sure why some clients are reporting just fine after the upgrade and others are not. I've rebooted a few of the clients that aren't reporting, but this doesn't help. Any suggestions? Thanks!
  4. All clients were back to normal this morning, but as of 11:31 EST, about half of my PCs are back to the "The ESET Push Notification Service servers cannot be reached" warning. Hopefully, this is just temporary.
  5. Unchecking the "Show" box that @Marcos highlighted, does remove the warning from client PCs, but I discovered that I had a separate policy for servers, which I also had to uncheck the "Show" box for. The warning still shows in ESET PROTECT though, but that is fine as long as the end users don't see it.
  6. Same issue with around 90% of my clients in ESET PROTECT showing the "The ESET Push Notification Service servers cannot be reached" warning. Just started receiving this warning over the last few days.
  7. I had this same issue. When trying to upgrade ESET PROTECT Server to v10.0.1128.0 from within the ESET PROTECT console, I waited over an hour and the console would not come up. I eventually restarted the server and when it came back up, I got the 404 error. I then tried to use the AIO, but it got stuck at upgrading SQL even though I was running the latest version of SQL Server Express 2019 (CU18). I ended up rolling back all changes on the server and then trying to use the AIO installer instead of through the console. Once again, the installer got stuck on upgrading SQL. This time, I killed a TiWorker.exe process that was causing 100% CPU usage and the AIO installer immediately changed to successful on SQL and the rest of the upgrade completed without any issues. I've always done the ESET PROTECT upgrades through the console, so I'm not sure why this upgrade caused so many issues.
  8. I'm running ESET PROTECT (Server), Version 9.1 (9.1.1295.0) and ESET PROTECT (Web Console), Version 9.1 (9.1.292.0) with JDK 18.0.2, but I think you need to at least install JDK 17 because ESET PROTECT will report anything lower than JDK 17 as outdated. https://help.eset.com/protect_admin/91/en-US/update_third_party_components.html https://www.oracle.com/java/technologies/downloads/#jdk18-windows
  9. Are we not able to use the ESET PROTECT Components Upgrade task to upgrade the agent on our clients to 9.1.0.1298? I would normally create a new task to do this for our PCs that aren't domain joined, but since the version of ESET PROTECT is 9.1.1295.0, it only shows 9.1.1295.0 for the reference ESET PROTECT server when creating the task. Doesn't the server version need to be the same as the agent version? It appears that the server will stay on 9.1.0.1295 and the agents will be on 9.1.0.1298. Is this correct?
  10. I still don't have this option to upgrade ESET PROTECT. Is there a reason why it hasn't shown up yet? Why isn't there a way to force an update check?
  11. I just saw @Marcospost about the 9.1.18.1 hotfix, but I still don't have this option to update on my ESET PROTECT. Is there a way to manually check for updates? It seems like there's no way to do this and you have to wait until the upgrade option is available.
  12. Hello. When I logged into ESET PROTECT this morning and checked my Dashboard, I noticed that a new version of ESET Management Agent is available. I'm running 9.1.1295.0 and 9.1.1298.0 is out, but I don't see an update for ESET PROTECT (Server) yet. I'm running 9.1 (9.1.1295.0) and it was my understanding that you wait for the server to get upgraded before you upgrade the agent. I checked https://help.eset.com/latestVersions/?lang=en and the latest version of ESET PROTECT is 9.1.18.1 (July 27, 2022). Will the upgrade to ESET PROTECT be released soon?
  13. I think you need to install the latest Cumulative Update for SQL Server 2019. The latest is CU16. The version of SQL Server 2019 that you have is 15.0.2000.5, which according to ESET's article on outdated components, is outdated. It will warn you that it's outdated if it's lower than 15.0.4223.0. https://support.microsoft.com/en-us/topic/kb4518398-sql-server-2019-build-versions-782ed548-1cd8-b5c3-a566-8b4f9e20293a https://help.eset.com/protect_admin/91/en-US/update_third_party_components.html
  14. It looks like ESET will report that your version of SQL is outdated unless it's running SQL Server 2019. https://help.eset.com/protect_admin/91/en-US/update_third_party_components.html
  15. I had this same message too, but I had outdated Tomcat and Java. I have since upgraded Tomcat to 9.0.64 through the all-in-one installer and am going to install JDK 17 or 18. If I had to guess, that alert will stay there until all third-party components are upgraded. I have a similar complaint about the licensing warning. I have 100 licenses and it starts throwing a warning when I hit 90. Super annoying! UPDATE: I just installed JDK 18, even though they only show JDK 17 is supported and that warning message went away when I logged into ESET PROTECT again. In fact, I don't even see an option to check to see if I have any outdated third-party components.
×
×
  • Create New...