Jump to content

T3chGuy007

Members
  • Content Count

    29
  • Joined

  • Last visited

Profile Information

  • Location
    USA

Recent Profile Visitors

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

  1. 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.
  2. 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
  3. 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.
  4. 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
  5. 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
  6. I went ahead and installed the CU21 update and I have not encountered any issues.
  7. 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
  8. 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.
  9. 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.
  10. 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!
  11. 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 serv
  12. 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?
  13. 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!
  14. 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
  15. For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3. I was running SP2. Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option. I then opened ESMC and went to Help->About. The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169. I then went to Help->Upgrade Product and a new client task was created. After a few minutes, I was kicked out of ESMC and I could not log bac
×
×
  • Create New...