Jump to content

j-gray

Members
  • Content Count

    265
  • Joined

  • Last visited

  • Days Won

    3

j-gray last won the day on April 12 2018

j-gray had the most liked content!

Profile Information

  • Location
    USA

Recent Profile Visitors

1,555 profile views
  1. j-gray

    Issues with OS X client after upgrade

    @Matus Are you saying the splash-screen issue is known? I have a case open (#216348) and support has advised that this is not a known issue.
  2. It appears that sub-groups are not respecting the parent group filter. I have parent group filter by OS, therefore, sub-groups do not specify OS in the expression. While it appears correctly in the console (e.g. only Macs are in the Mac group), because OS is not specified in any sub-group, sub-groups are applied to all clients.
  3. @Marcos Groups are displayed on the left with client info in the main pane:
  4. I have two separate dynamic groups to contain different operating systems; one for Windows and one for OS X based on the following two templates, respectively: OS edition . OS type = (equal) Microsoft Windows OS edition . OS type = (equal) Mac OS When I look in the console, as expected I see only Windows workstations/servers in the Windows group and only OS X devices in the Mac container. Yet, when I look at computer details of any client, it shows it being a member of both dynamic groups. Any idea what is causing this?
  5. j-gray

    Question - ESET Remote Administrator 6

    As a database is required, it installs SQL Express (free/no license required) by default. You can install the full version of SQL, but will require a license: https://help.eset.com/era_install/65/en-US/sql_server_windows.html?sql_server_windows.html MySQL is an option, too: https://help.eset.com/era_install/65/en-US/sql_server_windows.html?mysql_windows.html
  6. j-gray

    Issues with OS X client after upgrade

    I've created a case for the kernel extension error (#216378). Unfortunately, I was informed this is a known issue with no ETA for fix. We'll be halting our upgrade rollout for now.
  7. j-gray

    Issues with OS X client after upgrade

    I've created a case for the splash-screen issue. I'll create another one for the Protection Status/kernel extension issue, shortly.
  8. j-gray

    Issues with OS X client after upgrade

    @MichalJ Thanks for the reply. Behavior is counter-intuitive; the client shows red exclamation indicating a security risk, but console shows green check indicating good status. I would not want to see a green/good status if security risks are present and unresloved. The splash-screen appears at every reboot. Regarding Protection Status, tray icon and gui status looks like this: Protection Status policy looks like this: Issue reproduces intermittently. Client was working properly and I just rebooted to verify splash-screen is still appearing on reboot. Client came up with the error. Reboots in the past have resolved the error, but it recurs randomly on subsequent reboots.
  9. j-gray

    Issues with OS X client after upgrade

    Also finding that systems are showing a green check in the status column, despite having active threats: Properties of the client reflect the unresolved threats:
  10. j-gray

    Issues with OS X client after upgrade

    Anyone else seeing these issues on OS X? I imagine the splash-screen issue is a bug?
  11. We've upgraded our server to latest version, as well as some OS X clients (agent and av). I'm encountering the following issues: Splash-screen is displayed at startup. Policy is set (and locked) to not to display splash-screen at startup. Client 'Protection Status' shows an error and red flag with 'Web and Email' component on the client GUI. Policy is set for Protection Status to only show if Restart is required. Client GUI should not be showing other Protection Statuses. Web and Email error is appearing in client GUI somewhat consistently after reboots: "Kernel extension required for Firewall was not loaded because of an error. Try to restart macOS or reinstall the product." Though we have these components disabled by policy, something apparently is not loading correctly at start up.
  12. What you have posted reflects the defaults, and this is how the clients are configured, both Win7 and Win10.
  13. After upgrading to v7, I'm finding random systems with the following warning: "This feature is not monitored by Windows Security Center". Product = Operating System, Subproduct = Firewall We have the same policy applied to all Windows workstations, yet some have this warning while others do not. We do have the Windows firewall enabled on all systems. This error appears on some Windows 10, some Windows 7 and various versions of antivirus and agent. I'm unable to determine why the warning appears on some but not others, given same settings and policies. I can disable reporting of this, but would rather understand why it's being inconsistent.
  14. Thanks for the reply. That's confusing; the error specifies Firewall, but it's actually specific to Web and Email components. Also appears to only trigger for v7 clients and not earlier version, despite the same policy on both versions. Regardless, we have Web and Email components disabled, as well as Firewall and Content Filtering. Seems we should not get errors/warning for something we've intentionally disabled. It would be another story if it was enabled but not functioning properly...
  15. We successfully upgraded our server to v7 and we've upgraded some OS X and Windows agents to the latest versions, so far without issue. However, after upgrading Windows antivirus to the latest version, they are all showing an alert in the console: "Protocol filtering is disabled". The alert shows the subproduct as 'Firewall'. However, the Firewall is completely disabled via policy. Further, this alert does not show on Windows clients with earlier version of antivirus (e.g. 6.x). The client shows no errors in the GUI. Where in the policies can I fix this?
×