Jump to content

MartinK

ESET Staff
  • Content Count

    1,692
  • Joined

  • Last visited

  • Days Won

    55

Kudos

  1. Upvote
    MartinK received kudos from DH2020 in Clients not showing in ESMC   
    I would recommend to start by checking whether ESMC Agent installed on client machine is actually connecting to ESMC. For this purpose please follow troubleshooting part of documentation - especially status.html log present on client machine might be helpful in this case.
    In case ESMC Agent will be connecting to ESMC, most probable issue is that is is using different name in ESMC or is located in different group, which prevented ESMC to remove "dead" duplicate that is rendered as unmanaged.
    In case AGENT is not connecting to ESMC, it is crucial to resolve connectivity issues as described in referenced documentation.
  2. Upvote
    MartinK received kudos from igi008 in Clients not showing in ESMC   
    I would recommend to start by checking whether ESMC Agent installed on client machine is actually connecting to ESMC. For this purpose please follow troubleshooting part of documentation - especially status.html log present on client machine might be helpful in this case.
    In case ESMC Agent will be connecting to ESMC, most probable issue is that is is using different name in ESMC or is located in different group, which prevented ESMC to remove "dead" duplicate that is rendered as unmanaged.
    In case AGENT is not connecting to ESMC, it is crucial to resolve connectivity issues as described in referenced documentation.
  3. Upvote
    MartinK received kudos from m.gospodinov in dynamic groups expressions, update antivirus on list of computers, delete a trigger   
    I would have to verify by my self to be sure, but reason is probably that negation of specific condition is not very clear and it can be easily misunderstood. For example condition Installed software . Application version doesn't contain 7.1.2053.0 will be probably always true, as there will be also ESMC Agent with different version in list of installed applications. In case of version it makes no sense to use this kind of expression.
    My recommendation is to use positive conditions inside group definition, and instead negate result, i.e using NAND group type with following filters:
    Installed software . Application name = (equal) ESET Endpoint Antivirus Installed software . Application version = (equal) 7.1.2053.0  
  4. Upvote
    MartinK received kudos from MichalJ in Automatic FQDN rename not working   
    Is there any known method you are already using to fetch FQDN on those machines? For example some command line tool, shell command, etc.? Does output of any of following command:
    hostname hostname -f scutil --get ComputerName scutil --get HostName scutil --get LocalHostName sysctl -a mention value that could be possibly used as FQDN?
    We have already seen machines that were configured in a way that they were not aware of their's FQDN, it was available only on DNS servers, but that is problem for ESMC Agent which requires data to be available locally.
  5. Upvote
    MartinK received kudos from MichalJ in Automatic FQDN rename not working   
    Value of kern.hostname should be actually used by AGENT so setting it should resolve problem. There is definitely no need to reinstall AGENT -> hostname is not fetched very often, so easiest would be to restart AGENT's service. It can be done using following commands in root terminal:
    cd "/Applications/ESET Remote Administrator Agent.app" ./Contents/Scripts/restart_agent.sh  
  6. 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...