Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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 ( 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!
  6. 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.
  7. 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 ste
  8. 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.
  9. 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
  10. 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
  11. I went ahead and installed the CU21 update and I have not encountered any issues.
  12. 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
  13. 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.
  14. 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.
  15. 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!
  • Create New...