Jump to content


  • Posts

  • Joined

  • Last visited

About HSeber

  • Rank

Profile Information

  • Location
  1. Did you carefully followed? -> https://support.eset.com/en/kb7088-install-eset-protect-web-console-using-jdk-windows Specially the last part ->"Migrate your existing ESMC / ESET PROTECT Web Console to use JDK" by adjusting Tomcat. I moved from Amazon Corretto v.8 to v.17 without issue by following the guide.
  2. Thank you Marco. As long Antivirus definitions for EP6 will be populated and can be downloaded by the mirror tool, i think we won't have an issue soon? However i'll contact my partner for clarification. Why XP systems running Agent 7.2 show up in ESET Protect console as outdated?
  3. We still manage Windows XP system running in an isolated enclave with ESET Endpoint Antivirus 6.5.2132.6 / Agent 8.0.1238.0 Recently on all clients there is a notification in the GUI about product out of date. I already went through the policies if there is a disable checkbox but i couldn't find something related. Our ESET Protect Server is latest v8.0.xx Any idea how to disable the notification?
  4. I have a request from our security team to disable TRACE and/or TRACK method on our running Apache HTTP Proxy ( by: To disable these methods, add the following lines for each virtual host in your configuration file : RewriteEngine on RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK) RewriteRule .* - [F] Alternatively, note that Apache versions 1.3.34, 2.0.55, and 2.2 support disabling the TRACE method natively via the 'TraceEnable' directive. As easy as it sounds the required module "mod_rewrite.so" is not included in the latest Apache HTTP Proxy package. Further I'm unsure if there will be any functional impact after this has been disabled? We use Apache HTTP Proxy ONLY as a repository for modules updates & ESET repository products (mirror tool) Please advise if it is safe to add the module and add the 3 line to the virtual host in our http.conf.
  5. I have the v.8 Agent running on Windows XP SP3 & Server 2008 32-bit without issue. Even when you have an XP SP3 client running with latest v.7 Agent - ESET Protect v.8 shows for the XP client "Outdated version" and offer the upgrade to v.8 Agent. Anyway - v.8 Agent runs fine on XP SP3 & Server 2008.
  6. Hm, do i need to following this KB which will use the "Software Install" task to download the *.lf file from a internal source to the client: [KB7656] Activate ESET business products using ESET PROTECT in offline environment or can i simply use the "Product Activation" task and select the new generated and imported offline license file?
  7. Thank you very much for answering all my questions. That will help me to do the right actions without any risk!
  8. Do i need to wait till the old offline license has expired? or can i already push a new generated offline lic to all these offline clients? Further could i also setup a dyn. group (not activated endpoint) with an automatic task who will push the new lic once a endpoint report back to our ESET server as "not activated"? We have this automatic process for the regular "online" license, will it work equal with the offline lic? Thanks
  9. Hi ESET team, i have just extended our license via EBA. The new license expire date has synced fine with our on-premise ESET Protect Server license. We also have one existing offline license (40 count) where we serve XP clients in a DMZ enclave environment. This license still shows the old expire date on our ESET Protect Server. My question is what i need to do to get the offline license extended in ESET Protect console and what to do to keep the offline clients activated?
  10. You can refer to KB6891 how to deploy ESET Management Agent v7 from ERA5 console. The guide works from Windows 7 or Server 2008 as it depends on Powershell v1 folder: https://support.eset.com/en/kb6891-deploy-eset-management-agent-using-eset-remote-administrator-5x I also had v5 Endpoints and 4.5 FileServer Products and i could manage them with ESMC7 after the Agent was deployed. We also having enclaved XP machines. For those i created from the ESMC an All-in-One installer, including latest Endpoint 6.5 & Agent v7. We do a manual install on each system on top of Endpoint v5. No need to uninstall v5 first. In the Online Help for ESMC 7.2 you find the information which products can be managed: https://help.eset.com/esmc_install/72/en-US/?supported_products_install.html
  11. I think i detected a serious bug in the All-in-one Installation wizard... Here is what i did a what happend: I've started to create an All-in-one package (Agent & Security Product) I removed the license (will be activated later by a automated task) For product i selected EEA 7.3.2039.0 Windows US language No Configuration policy selected. On next page the default ESMC certificate is selected with no passphrase. On the Advanced tab a Name was entered no description, no Tags selecgted, Parent group left to All. Unchecked "Enable ESET AV Remover" For Configuration type i selected - "Do not configure" and entered my ESMC server hostname + port number. No Http proxy is selected. Next, i've downloaded the package and installed this on Test-VM without any network adapter or connectivity! Once installed and rebooted i tried to uninstall the ESET Agent - but that failed because the password is incorrect? We have a Management Agent policy in place that set a password. Entering the password from the policy -> i was able to uninstall the Agent on the offline host From where and why accepted the Agent that password even when i select not policy during the installation wizard? Also my Test-VM was without any connectivty?
  12. Whenever i try to deactivate a activated product (remove license) the product remains activated and in the Object details under "Product & Licenses" the license is still shown. When triggering again the deactivation task on the same object (after 30 minutes) it says "License seat already removed" All Endpoint Objects show the same behavior, the license is not removed. Checking the Endpoint Client, all the License information is still there. Please help.
  13. I've copied & pasted the win32.zip via RDP into the server. Extracted on the server and... it works now. Previously i've always copied & pasted the exe + dll via RDP and received that library error. Strange, anyway...thanks for that quick help!
  14. I'm using the dll from the downloaded "win32.zip" file.
  15. I've installed/updated all VC packages. Same error. Attached the ProcMon capture log file. Logfile.rar
  • Create New...