Jump to content

T3chGuy007

Members
  • Posts

    45
  • Joined

  • Last visited

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. Hello. I see that ESET Endpoint Security v8.1.2037.2 was released. Are there plans to release v8.2 of Endpoint Security soon? I just don't want to start upgrading my clients to v8.1.2037.2 only to have v8.2 come out a week later as what happened in the post below when v8.0.2039 came out and a week later v8.1.2031 was released. I know v8.0.2039 was a hotfix and v8.1.2031 was a feature update, so I wanted to make sure there wasn't a feature update planned to be released soon. Thanks!
  2. Thanks for the clarification, but it would have been nice if the hot fix and feature update were released on the same day. This way, those users who like to keep their devices up-to-date would have had the option to install v8.0.2039.0 or v8.1.2031.0. I would have never updated our PCs to 8.0.2039.0 if I had known 8.1.2031.0 was going to come out a week later.
  3. My thoughts exactly. I spent a couple of days upgrading all of our clients to 8.0.2039 only to come in today and find 8.1.2031 has been released. Unless it is an absolute emergency release, having a new release a week apart is very frustrating. Is ESET becoming Microsoft and releasing a cumulative update once a month?
  4. Ok, I'll wait to deploy the agent upgrade until tomorrow. Thanks for the help!
  5. Ok, with the module update, is this that will download automatically to client PCs and we'll just have to wait for that to complete before processing with more agent upgrades? Or is that something we'll need to push out from ESET PROTECT?
  6. In my case, if the user is logged into Windows, the firewall message pops up. If the user isn't logged into Windows, the message pops up the next time they login.
  7. Hello. I'm in the process of upgrading my clients from ESET Management Agent 8.0.1238.0 to 8.1.1223.0 and when I run an ESET PROTECT Components Upgrade on a PC, I receive the warning below during the installation process. I also receive this message when I try to deploy agent_x64.msi using my deployment software. Is there a way to disable this from coming up? If I click "Keep rules", I have to enter admin credentials, which most users do not have on their PCs. Thanks!
  8. Ok, thanks for clarifying!
  9. Hello. Can you tell me if Apache Tomcat 10.0.7 is supported with ESET PROTECT (Web Console), Version 8.1 (8.1.221.0)? I downloaded the latest ESET PROTECT All-in-one Installer (8.1.13.0), but it came with apache-tomcat-9.0.46-windows-x64, so I tried downloading apache-tomcat-10.0.7-windows-x64 and putting the .zip file into the x64\installers directory, but when I tried to do the upgrade to ESET PROTECT Web Console , it kept erroring out. So I downloaded and tried apache-tomcat-9.0.48-windows-x64 and it worked fine.
  10. Hello. This morning when I logged into ESET PROTECT, I saw a message that a new version of ESET PROTECT was available. So I backed up my certificates and DB and started the upgrade from within the console. After 30 mins, I still could not login to the console and the error below kept coming up. All of the ESET services and Apache Tomcat 9.0 were running. I checked C:\Program Files\Apache Software Foundation\apache-tomcat-9.0.35\webapps\ and I had three folders. They were era.bak, era.new, and ROOT. I renamed era.new to era and restarted the Tomcat service and I was able to login. I checked the task for the upgrade and it looks like there was an error when renaming era.new to era. Do we know the cause of this other than access is denied?
  11. Hello. We currently have a 100-user license and have 87 of those licenses active. If I activate another three devices, I will get a warning in ESET PROTECT that our available license count is getting low. Is there a way to disable this message or change the trigger so it shows a warning when only 5 licenses are left? Thanks!
  12. Hello. After changing the Secure Browser policy to disabled and preventing changes to the policy, I rebooted all of our PCs on Monday. Yesterday, no PCs were showing this warning in ESET PROTECT, but today, about half of my PCs are showing this warning again. I submitted a case with ESET to see how we can fix this issue/bug.
  13. Ok, I changed my policy so that Secure Browser is disabled. I don't think our users would have turned it on since the PCs that have this warning, the users do not have admin rights. Thanks for the help.
  14. Hello. It looks like Secure Browser is already disabled and all of our clients have been running ESET Endpoint Security 8.0.2028.0 about a week after it was released. It's possible the PC was updated with updates like Chrome, Firefox, etc, but nothing Windows Update related since those are all controlled. I can look into creating a new ticket to see if they need logs to investigate. Thanks.
  15. It looks like rebooting the PC clears the warning, but it would be nice to know why it's just now coming up and if there was a way to fix this without having to reboot the PC.
×
×
  • Create New...