T3chGuy007

Out of curiosity, I verified that the only policies that were applied to the 'All' OU were my agent sync policy and my auto update policy, which disables automatic updates. I then rebooted the server and when I checked the 'All' OU after a reboot, the built-in auto update policy was once again enabled on the 'All' OU and set to first. So it appears that if you remove the built-in auto update policy and reboot the server, it gets added back. I'm hoping this can be corrected in the near future or provide a way to prevent this behavior.

I checked the policies assigned to the 'All' OU and the only two that are linked are a management agent one and the one that I created to disable auto updates. What happened is that I previously had the built-in auto update policy (which enables auto updates) removed from the 'All' OU, but after I upgraded Server Security on my ESET PROTECT server, that automatic update policy was linked again to my 'All' OU. It's like after a server reboot or a server upgrade it re-enables the automatic update policy.

Hello. I do not want my PCs to automatically update to the latest version of Endpoint Security when it's released, so I created a new policy to disable the auto-update feature per the article below. I assigned this policy to my 'All' OU and then I unassigned the built-in auto update policy from the same OU. However, I upgraded ESET Server Security on my ESET PROTECT server and I discovered the built-in auto update policy was reassigned to my 'All' OU again. How do I prevent that built-in policy from reapplying to all of my devices after an upgrade? I want to handle software updates manually and not have it managed by ESET PROTECT. I cannot delete the built-in policy, but it seems unassigning only works until the server is rebooted or upgraded. https://support.eset.com/en/kb8147-opt-out-from-auto-updates-in-eset-protect-and-eset-protect-cloud

I received the same message as @TheSkymanDC and when I reboot the PCs in question; they show updated to the latest version as soon as it reports back to the server.

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!

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.

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?

Ok, I'll wait to deploy the agent upgrade until tomorrow. Thanks for the help!

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?

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.

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!

Ok, thanks for clarifying!

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.

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?

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!

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.

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.

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.

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.

Hello. This morning, I logged into ESET PROTECT and several of our PCs have the warning ""Secure Browser is non-functional". I checked and we don't even have Secure Browser active, and to be honest, I didn't even know it was an option. We are running ESET PROTECT (Server), Version 8.0 (8.0.1258.0) and ESET PROTECT (Web Console), Version 8.0 (8.0.191.0) with ESET Management Agent 8.0.1238.0 and ESET Endpoint Security 8.0.2028.0. Any ideas on why we are seeing this now and how to turn off these warnings? Thanks!

Ok, I guess I misunderstood the article because I thought by reinstalling ESMC Web Console it would eliminate the SSL connection error, but that doesn't seem to be the case. As it's been said, the portal will still show that it's not secure unless I use a 3rd party authority.

Ok, just to clarify, the KB article states that the solution for the insecure message is to reinstall ESMC Web Console. I was under the impression that if I did this and opted to have the installer generate a certificate automatically (which I did), it would fix the issue. You're telling me that the article is wrong and additional steps are needed? See highlights below. Reinstall the ESMC Web Console using the All-in-one installer You can reinstall the ESMC Web Console using the All-in-one installer to automatically generate the secure connection (https) certificate. Follow the steps below: Make sure Apache Tomcat is not used by any other application than ESMC Web Console. Uninstall Apache Tomcat. This step unistalls also the ESMC Web Console. Download the ESMC All-in-one-installer - use the same version as your ESMC Server: - version 7.0 32-bit - version 7.0 64-bit - version 7.1 Run the ESMC All-in-one-installer. Select Install → Accept the EULA → select the component to install: ESET Security Management Center Webconsole. The secure connection certificate will be automatically generated during the installation.

Ok, thanks for the clarification. I went ahead and uninstalled Tomcat, like the KB said to do, and I then installed ESET Security Management Center Webconsole. I did not check the option for "Add Custom HTTPS certificate" because the instructions said that the secure connection certificate will be automatically generated during the installation. Once the install was finished, I launched the ESMC portal again, but it still shows as insecure. Did I skip a step? I believe I followed the instructions so I'm not sure why it is still showing insecure. Thanks for the any help.

Hello. It looks like our ESMC installation was setup without using SSL so whenever I go to our ESMC portal, I get a warning that the connection is not secure. I found this KB article that states to download and reinstall ESMC Web Console using the All-in-one installer in order to generate the secure cert. It says to download the version of the All-in-one installer that matches your ESMC Server version. I am running v7.2.1278.0 of ESMC Server and v7.2.230.0 of the Web Console. When I go to the download page, I only see v7.2.11.1 of the All-in-one installer. Is this the version that I need or is there an updated All-in-one installer somewhere?

In case anyone was wondering, I upgraded SQL Server 2017 Express to SQL Server 2019 Express, and I have experienced no issues. After the upgrade, I had to download and install CU6 for 2019 since the upgrade only installed the RTM version (15.0.2000.5). https://support.microsoft.com/en-us/help/4518398/sql-server-2019-build-versions https://support.microsoft.com/en-us/help/4563110/cumulative-update-6-for-sql-server-2019