Jump to content

GDI

Members
  • Posts

    38
  • Joined

  • Last visited

About GDI

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

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

  1. Thanks for the info! Looks like it was probably my fault. I was testing some deployments and it looks like there was a previous GPO to disabled some of the features. I'm assuming it was a left over due to a conflict with our previous AV. All is good now!
  2. We are noticing that Windows built in "App & Browser Control" seems to be turned off by upon a fresh Windows install. We've debated enabling it via GPO. But, my question is, do they (or should they) be enabled if ESET is installed? Or does ESET basically do the same that smartscreen for app & files and Edge would do? Is there any potential for conflicts if "App & Browser Control" is enable along with having ESET installed?
  3. @Peter Randziak Is there any update for this? We are using Protect Cloud and this has been going on for at least 5 days. Should we be logging support tickets for this? I'm also seeing no indication of this issue at https://status.eset.com/.
  4. @Marcos Disregard. I just noticed the post that @Peter Randziak acknowledges that this is a known issue.
  5. @Marcos Is this a known service issue? We've been having the same issue the past several days.
  6. Have I posted in the wrong forum for this question?
  7. We are adding some iOS devices to our Protect Cloud instance. From what I understand, there isn't an ESET "App" for iOS and adding it into ESET gives very basic MDM functionality, like locking, factory reset, and some policies. What is interesting, under Dashboard > Antivirus Detections > Last Scan, it shows the iOS devices as "Never Scanned". Is this right? I thought iOS devices don't have scanning functionality or have I missed something? If they don't have scanning functionality, is there a way to exclude them from the "Never Scanned" stats?
  8. I'm seeing a few systems where rebooting makes the error go away. I'm assuming once it is fully resolved, a reboot won't be necessary and it'll clear itself out on the next check-in with the ESET servers. Correct?
  9. Thank you for the info! Regarding the info I quoted above, I'm still a bit confused. I copied our current ESET installation to a test server and ran the all-in-one installer. Once the installer opened, it had an option to install ESET Bridge, so I went ahead and tried it out and it did in fact uninstall the Apache HTTP Proxy. I confirmed this because before I started the installer, we had a "ApachHttpProxy" service. After the all-in-one installer ran and I restarted the server, the "ApachHttpProxy" service was no longer there and the "ESET Bridge" service was installed.
  10. Maybe I'm being dense, but I'm not quite understanding the migration instructions from Apache HTTP Proxy to ESET Bridge. We are using Protect On-Prem on Windows Server 2019. I've read the instructions at https://help.eset.com/ebe/1/en-US/migrate_from_http_proxy.html and have the following questions: 1. First, the warning says "Do not install ESET Bridge on the computer running Apache HTTP Proxy" then it says that if I run the all-in-one installer, it'll uninstall Apache HTTP proxy and install ESET Bridge. Seems like those instructions are contradictory. Should I run the all-in-one installer on the ESET protect server to replace Apache HTTP Proxy with ESET bridge? 2. Step 2 says to configure the ESET Bridge Policy, but the "Install ESET Bridge" instructions says it creates the default HTTP Proxy Usage policies. So, which one is it? Do I create new policies or does the ESET Bridge installation create the policies? Thanks!
  11. We are still having this issue when there is an internet outage. We had one last night and several of our servers gave the error but could not be restarted since it was during business hours. I was able to get the logs of one server while the error was showing, then restarted it and the notification went away.
  12. Ok, so at this point it sounds like we can release 9.1.2051.0 as the issue has been resolved in the module (obviously as long as all systems have picked up the 2011.5 configuration module)
  13. For those of us who deploy via ESET Protect, and those of us who are little less experienced with ESET, does that mean we should expect a newer version (higher than 9.1.2051.0) to be available for deployment from ESET Protect at some point next week? We'd prefer to stay on 9.0.2046.0 and wait for a full release rather than install a pre-release.
×
×
  • Create New...