Jump to content

drewd

Members
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by drewd

  1. It appears that IIS is using a port that the ERA Dashboard is configured to use. You can try changing the port that the ERA Dashboard uses, by performing the following steps: Open the ESET Remote Administrator Console (ERAC) by clicking Start > All Programs > ESET > ESET Remote Administrator Console > ESET Remote Administrator Console. Click Tools > Server Options. Click the Advanced tab > Edit Advanced Settings. Expand ESET Remote Administrator > ERA Server > Settings > Dashboards. Click HTTP Server Port, and HTTPS Server Port, (one at a time), and enter values
  2. The following ESET KB article explains how to remotely install ESET NOD32 Antivirus Business Edition for Mac OS X: How do I remotely install ESET NOD32 Antivirus Business Edition for Mac OS X? hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2524
  3. Although there is not a Virtual Desktop Infrastructure specific version of the ESET antivirus client, our current Endpoint products are certified as VMWare Ready and Citrix Ready. For additional information regarding how to deploy our products in a VDI environment, please read the ESET Virtual Environment Optimization Guide.
  4. Please verify with us that you have performed the following steps: User credentials are not syncing in the Active Directory of the ESET Remote Administrator Server hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2757
  5. Please use the ESET KB article SOLN2716, that ChadH suggested to verify that the ESET antivirus client is configured properly to connect to the ERA Server, and that port 2222 is open on both the server as well as the workstation: hxxp://kb.eset.com/esetkb/SOLN2716:
  6. Have you tried updating openssl? What is the output of the following command from a terminal? openssl version If you are running a 64-bit OS, you may need to install the 32-bit version of openssl. Also what is the output of the following? uname -a && cat /etc/*release
  7. I see that you would like to automatically initiate deployment of the ESET antivirus client, to machines where it is not yet installed. You can accomplish this via a Windows Login Script. A Windows logon script will allow you to assign tasks that will be performed when a user logs on to a particular computer. Since a login script is essentially a text file, you can just use a simple text editor to insert a line into the script that will call the file einstaller.exe from a predefined network share. This will initiate the remote push installation of the ESET antivirus client,
  8. I see that you are asking about using text strings to identify non legitimate email as SPAM. EMSX allows you to setup User-defined rules from within the EMSX GUI, that can filter SPAM and malware based on many different variables: You can specify conditions, such as text strings, that when detected will result in certain actions being performed, such as the email being placed into the system quarantine, or certain types of attachments being deleted. Here is some additional information regarding creating, and using User-defined rules to filter SPAM and malware, from the documentatio
  9. It is difficult to say what exactly happened, based on the information provided, but you can do the following in the future: Ensure that you are using ESET RA version 5.0.511.0 or higher, and EMSX version 4.5.10011.0 or higher. It is always a good idea to have backups of all of your current configurations. If you want to create a XML file that can be imported directly into the EMSX client then be sure to use the "Export Marked to" option from ESET Configuration Editor, which should only export the options that you specifically edited. If you want to deliver the configuration settin
  10. The ApprovedSenders file is now managed from within the EMSX GUI Antispam engine parameters setup, as the Allowed Senders/Domains whitelist. You can access this functionality via the EMSX GUI to enter the email addresses and domains that you want to whitelist, one-by-one, or you can also use the ESET Configuration Editor to add a comma-delimited list: You also have the option of entering the email addresses, and domains that you would like to add to the EMSX Allowed Senders, as a comma-delimited list, from within the ESET Configuration Editor: Windows Server v4.5 > Mail Secur
×
×
  • Create New...