Jump to content

ronmanp

Members
  • Posts

    64
  • Joined

Posts posted by ronmanp

  1. We use SCCM. So it installs using MSIEXEC running as SYSTEM. We have roughly 700 applications in SCCM and can confirm that ESET is the one giving us the most trouble. Unfortunately that's not just how Windows Installer is supposed to work. 

    We did work with ESET premium support but with little success hence our decision to change product. 

  2. This command works if you don't attempt to upgrade first. Once we attempt to upgrade and it fails the only option we have is to use the Uninstaller Tool. Sounds like we'll have to script the removal, restart and then installation of the latest build just to upgrade. 

    That's not just an isolated case, we can repro on a newly imaged machine upgrading from ESET Endpoint Antivirus 8.0 to 8.1. 

  3. Hi, 

    I just upgraded to V7 from ERA 6.5 using the Component Upgrade task. I used the V7 AIO installer to upgrade Apache HTTP Proxy as well. 

    I get these errors all the time in "C:\Program Files\Apache HTTP Proxy\logs\error.log"

    Quote

    [Mon Feb 04 16:58:45.932716 2019] [ssl:warn] [pid 7308:tid 452] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]

    Shouldn't there be httpd-ssl.conf in "C:\Program Files\Apache HTTP Proxy\conf" ?? It's not present for us at least.

    I had issues with client activation and decided to disable proxy in the client to use your public servers. It appears to have fixed the issue so the proxy config has some issues for sure.

  4. Yes we are ok here, just wanted to share this in case someone had the same problem as we had to spend some time on this problem. 

    On the same note, even just by accessing https://edfpcs.trafficmanager.net in Chrome will prompt a security warning which is sub-optimal to say the least. 

    I known it's not meant to be accessed directly but it could probably be improved.

    You can consider this as resolved for us. 

    Thanks for looking into it,

  5. Hi Peter, 

    We had issues activating ESET Endpoint Antivirus and after monitoring ESET and our web proxy logs we found out https://edfpcs.trafficmanager.net/ was getting blocked due to certificate mismatch. 

    So our web proxy blocks it before the balancer can do its job. 

    Not a big deal because we manually whitelisted it but I feel like we'd have a lot more issues than just ESET activation servers if our web proxy didn't support DNS balancers.

  6. Hi, 

    I'm experiencing issue activating a client that connects through the ESET Apache HTTP Proxy. Definition updates download just fine once the product is activated but for some reason the only way I can activate is if I disable the proxy in the ESET Endpoint Antivirus client. 

    • ESET Endpoint Antivirus 6.6.2072.2
    • Policy set to use proxy and fallback to direct connection when proxy not available
    • Managed by ERA 6.5
    • Default httpd.conf (unchanged from the ERA 6.5 installer)
    • Pointed my browser to the Apache HTTP Proxy and went to https://edf.eset.com/edf successfully
    • Confirmed on our corporate web proxy that no web traffic is being blocked 

    Worth noting that this started with version of ESET Endpoint Antivirus 6.6 as I didn't experience this issue with 6.5 and older.

    Thanks, 

  7. Same here. 

    I've been told by ESET support that ERA 7 is coming out and it should support all the 6.6 configurations out of the box.

    Also been suggested to locally configure a client, click on request configuration from ERA and then create a new policy with the imported configuration. I didn't try that as I'll just be sticking to 6.5 until there's a proper solution.

  8. Using Endpoint Antivirus 6.6.2046.0 with ERA 6.5.522.0.

    We disable Protocol Filtering by policy so we also disable the application statuses that relate to it. Just after upgrading to 6.6.2046.0 from 6.5 I started having warnings about it again.

    After checking I see that Endpoint Antivirus 6.6.2046.0 added two new application protocol filtering statuses that can't be changed by policy yet. Please see screenshot comparing the options I have from the server vs what I have locally. I assume we'll need to wait for ERA 6.6 to fully support Endpoint Antivirus 6.6.2046.0?

    As a side note, I suggest that when you disable a functionality by policy the client should automatically stop sending alerts about it.

    ESET Endpoint Antivirus.png

×
×
  • Create New...