Jump to content

OllyOrc

Members
  • Content Count

    13
  • Joined

  • Last visited

Everything posted by OllyOrc

  1. Kindly answered via email by ESET Technical Customer Care Engineer We have this documented as this is fairly commonly requested, this guide is available at https://support.eset.com/en/allow-external-remote-clients-to-check-into-a-central-eset-remote-administrator-server-6x although the guide refers to v6, it also applies for v7 Effectively, you will need to set the machines' Agents up with an externally resolvable address and have port 2222 available for the server, so that they get the correct address the moment that the Agent is installed. For machines currently with the Agent installed, applying the policy for the Agent address will have the same desired effect
  2. Many thanks for the continual support as currently have the new ESMC server communicating with multiple windows servers and Apple Macs on different LANs, along with a new Mirror Tool/Apache server. However, we have recently employed some new Mac users who will work from home, with occasional visits to the office, so my question is. Can the ESET Agent still communicate over the internet from their homes, back to our ESMC server to notify us of any threat alerts, if we open our Firewall to allow ESET traffic on the default port 2222 (or a different port if we change the ESMC server settings) and also create an external DNS to resolve to our internal ESMC server? Kind regards ESET Management Agent 7.1.840.0 Up-to-date version ESET Mac Endpoint Antivirus 6.8.400.0 Up-to-date version ESET Windows File Security 7.1.12006.0 Up-to-date version ESET Security Management Center (Server), Version 7.1 (7.1.503.0) ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0) Copyright (c) 1992-2019 ESET, spol. s r.o. All Rights Reserved. End-user license agreement CentOS (64-bit), Version 7.7.1908 License Management Installed Components: NAME VERSION Update module 1074.1 (20190925) Translation support module 1781 (20200108) SysInspector module 1274 (20180918) SSL module 1041B (20190913) Push Notification Service module 1057 (20200121) Configuration module 1822.1 (20191028) Database info: DB Name: era_db DB Version: MySQL 5.6.40 DB Size: 164MB DB Hostname: eset-manager.xxx.xxx.xxx DB User: era@localhost Warning: This program is protected by copyright and international treaties. Copying or distribution without express permission from ESET, spol. s r.o. by any means, in part or in full, is strictly prohibited and will result in prosecution to the full extent that these laws will allow internationally. ESET, the ESET logo, ESET Smart Security, LiveGrid, LiveGrid logo, SysInspector are either registered trademarks or trademarks of ESET, spol. s r.o. in the European Union and/or other countries. All other trademarks are the property of their respective owners. Protected by US Pat. 8,943,592.
  3. Thanks Michalj, it was your advice detailing placing the proxy settings into the Mac Agent installer, that fixed my issue as the Mac client is now reporting to the ESMC. I take your valid point that there is no need for the mirror tool when also using a proxy that will cache the updates anyway. However, I'm currently testing the mirror tool server works along with its Apache web server to deliver the updates to the clients. Now it is working fine I can point the majority of our servers towards the working Mirror tool, as they are on a separate network with no proxy. Many thanks
  4. Having recently migrated from ERA to ESMC everything is working fine and successfully updating our multiple windows servers. However, some new Apple Macs have been introduced to our domain and have had the the Mac ESET Endpoint Antivirus 6.8.400.0 successfully deployed to them and they used to show an up to date Last connected Time within ESMC. These Macs are on the staff LAN that has a staff proxy, along with a couple of windows servers. So I add the proxy details into the generated windows File security Installers to enable them to communicate with the ESMC that is on a different internal LAN. This worked fine for the couple of windows servers on the staff LAN but the Mac installer doesn't allow proxy details to be embedded within them. Therefore, I set the proxy details in the Policy that is assigned to the Macs but unfortunately they only show the Last Connected Time as the day they had their Mac ESET Endpoint Antivirus 6.8.400.0 deployed to them. It gets slightly more complicated as I also introduced a Mirror server and configured the Mac Policy and the Policy for the couple of windows servers on the staff LAN, to point at the mirror server to receive their updates, as I was under the false impression that all clients received their updates from the ESMC and not individually through the internet. Currently the couple of windows servers show up to Last Connected Time within ESMC, as they have the proxy settings necessary to see the ESMC on a separate LAN, plus their mirror proxy settings to allow them to successfully receive their updates from the mirror server which is great! However, the Macs also have their mirror proxy settings to allow them to successfully receive their updates from the mirror server which is working great but unfortunately they don't show an up to date Last Connected Time within the ESMC. Therefore my concern is that these Macs won't be able to alert any detected threats within the ESMC if they can not. Have I missed an important step in their configuration? Kind regards and won't be able to reply until Monday but appreciate any advice and hopefully I have explained this complex situation. ESET Security Management Center (Server), Version 7.1 (7.1.503.0) ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0) Copyright (c) 1992-2019 ESET, spol. s r.o. All Rights Reserved. End-user license agreement CentOS (64-bit), Version 7.7.1908 NAME VERSION Update module 1074.1 (20190925) Translation support module 1780 (20191217) SysInspector module 1274 (20180918) SSL module 1041B (20190913) Push Notification Service module 1055 (20191107) Configuration module 1822.1 (20191028) Database info: DB Name: era_db DB Version: MySQL 5.6.40 DB Size: 163MB DB Hostname: eset-manager.******* DB User: era@localhost
×
×
  • Create New...