Jump to content

MartinK

ESET Staff
  • Content Count

    1,762
  • Joined

  • Last visited

  • Days Won

    58

Kudos

  1. Upvote
    MartinK received kudos from MichalJ in Mixed environment: which is the best way to manage?   
    My recommendation is to check ports usage documentation: https://help.eset.com/esmc_install/71/en-US/ports_used.html
    Technically ESMC + Webconsole (tomcat) are listening on following ports:
    2222 (can be changed, for example to 443 to reduce possible firewall issues): this port is used by ESMC Agents to connect to ESMC. This one has to be open for client devices. It could possibly be limited to specific IP addresses if possible, but that could possibly block roaming devices 2223: port is used for (my recommendation is to not open this port from outside of server) for Webconsole-to-ESMC communication. If webconsole will be installed on the same machine (= default scenario), there is no need to expose this port for console to work correctly second use is for ESMC Agent installers in case of "Server assisted installation". I would strongly recommend to omit this functionality, it is deprecated in favor of all-in-one installers which are much more suitable for MSP scenario. 443: standard port for access to ESMC Webconsole via browser. Port has to be opened for ESMC users to access console. My recommendation is to enable access to this port only for known IP addresses if possible. There is also possibility to perform additional hardening of Apache Tomcat configuration to enable only most secure TLS ciphers, you just have to be sure your browser will support it. Also make sure that when installing ESMC, so called "Advanced security mode" is enabled in it's configuration. It will prevent connections of older ERA Agents but should work for ESMC 7.1 Agents installed even on oldest supported systems (Windows XP).
  2. Upvote
    MartinK gave kudos to Marcos in ESMC 7.1 sorting in GUI   
    For me sorting by status works. Make sure there is no number next to the arrow. As of ESMC 7.1, you can define primary, secondary and tertiary sorting which is indicated by numbers 1,2,3 respectively.

    In such case, click the column title until the number disappears and records are sorted by the Status column:

  3. Upvote
    MartinK gave kudos to Neal in ESMC Office 365 Settings not working for SMTP   
    Got mine working yesterday. Do you have Microsoft MFA enabled? If so, then you need to create an App Password for that user, and you use that App Password as your authentication password.
    Details below work for me.

  4. Upvote
    MartinK received kudos from MichalJ in Unable to upgrade ESET agent to Version   
    Actually you have to use different tasks to upgrade applications:
    Components upgrade task is required to upgrade ESMC Agents Software installation task is required for upgrade of other ESET applications
  5. Upvote
    MartinK received kudos from MichalJ in Not able to install ESET Security Management Center Server Installer   
    Please provide list of installer parameters you are using to deploy AGENT (only parameter names, no need for passwords or other sensitive details). From log it seems you are performing so called server-assisted installation, but probably with wrong hostname:port configuration, resulting in communication failure.
    Also once ESMC is installed, you might use also live installer created in console to deploy AGENT, it has no parameters so it would be much simpler.
  6. Upvote
    MartinK gave kudos to T3chGuy007 in ESMC Upgrade   
    For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3.  I was running SP2.  Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option.  I then opened ESMC and went to Help->About.  The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169.  I then went to Help->Upgrade Product and a new client task was created.  After a few minutes, I was kicked out of ESMC and I could not log back in.  A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in.  ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0.  The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier.
    https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
    https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15
  7. Upvote
    MartinK received kudos from MichalJ in Unknow status - new agent   
    Just for clarification for others in case they encounter this issue: unknown state indicates that for specific application version ESMC is not yet aware of it's state. This normally happens when new version of application is seen for the first time and it should be resolved automatically in no more than 1 hour.
  8. Upvote
    MartinK received kudos from FRiC in ESMC blocked by ESET Endpoint   
    I think this behavior has been already reported and probably fixed in the meantime. Maybe @Marcos will know more details of whether module responsible for scanning network has been updated in the meantime. It is also possible that update was canceled which might explain why only specific devices were affected.
  9. Upvote
    MartinK received kudos from JirkaL in Unknow status - new agent   
    Just for clarification for others in case they encounter this issue: unknown state indicates that for specific application version ESMC is not yet aware of it's state. This normally happens when new version of application is seen for the first time and it should be resolved automatically in no more than 1 hour.
  10. Upvote
    MartinK received kudos from MKach in "Product not Activated" even though Activate Product task succeeds   
    Just for verification: is your license intended to activate ESET Endpoint Security? Asking because this would probably happen if you try to activate it with license for different product, i.e. ESET Endpoint Antivirus or possible other.
  11. Upvote
    MartinK received kudos from Peter Randziak in Not able to install ESET Security Management Center Server Installer   
    When installing ESMC, following credentials are required:
    password for to-be-created ESMC user "Administrator" ( --server-root-password) credentials of DB administrator, i.e. DB user that has permissions to create database and create new user if required ( --db-admin-username , --db-admin-password ) DB user to be used by ESMC service to connect to database ( --db-user-username , --db-user-password ). This user can be the same as administrator, but I would not recommend that. In case provided user does not exists, it should be automatically created using DB administrator account -> created user will be granted permissions required for ESMC operations and it will be limited to ESMC database.
  12. Upvote
    MartinK received kudos from Peter Randziak in Future changes to ESET Security Management Center / ESET Remote Administrator   
    Unfortunately I am al so not sure how it was meant. We are officially declaring maximal number of managed clients to 10000 when using MySQL database, but it is not related to number of actually connecting clients, but rather limit is amount of data. ESMC installed over MySQL might have performance issues with processing larger amount of data and rendering larger datasets. As an result rendering of specific reports (threats for example) might be much slower, but in "clean" network even much larger environments can be managed with MySQL-based ESMC installation.
    Persistent connections as introduced in ESMC should actually significantly reduce load of ESMC server, especially in "dormant" state when no changes are made in management console. If properly configured on recommended HW, ESMC should handle hundreds of clients per second.
×
×
  • Create New...