Jump to content

Miami

Members
  • Posts

    43
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Miami

  1. Why not use the regex? With regex you can match versions the way you wish. If you need to care only about Agents version 7.2 versions use following regex (7\.2).* When you use it with application filter (to show only Eset Agents), it should match all 7.2 agent versions. OR, you can try to use following filter for outdated product. Its just my guess that it could work, I have not tested it, yet.
  2. I understand your situation, but to me this really looks like some policy interfere with the default policy/configuration. What I would do is to check group membership of that problematic computer. Maybe it is a member of some dynamic group and gets special agent policy. If first connection is ok, it means something is doing a configuration change and if you have more Agent policies deployed it can happen that they interfere. I am guessing that info about last applied policies can be still seen in client details, same as its group membership. Related to agent connection issue, I experienced a, more servers in the server list configuration b, policy interference c, DNS configuration
  3. I am sure you have already double checked your policies, but this looks like Agent is being reconfigured after some time. Maybe after first connection to the server is the default policy overwritten by a forced one or the one which is closer to the computer in you structure. Is there only one server listed in Agent server list configuration? For testing purposes you could create a group where no policies would be applied. Add a computer into that group and manually apply all policies that are applied to these problematic computers.
  4. Hello MartinK, thank you for response. Anything related with AD will not work for us as our environment contains also non AD clients, that we need to move around. I am aware that this is not possible, I was just forced by your colleague Marcos to move this topic from suggestions for "Future changes to ESET Security management center" topic. So what now?
  5. Thank you for the feedback. I was able to restore it from backup.
  6. Hello, we use dynamic group with following template configuration to show us all V6 Agents. I am sure you can adjust that to ver 7. Of course the group is populated on next connection of the client (agent).
  7. Question: Is it possible to to move computers between groups with a task. If not it would be great to have such functionality in ESMC Detail: If we want to move computers from Lost & Found to groups created based on AD. Currently this is not possible and we have to move computers manually. It would be good to have this for dynamic groups, if computer fall into such group it would be automatically moved to a desired destination group. Moving computers to groups at installation is not possible for us as we use only one installer for all the clients acros the globe.
  8. Hello Marcos, my post was a suggestion as that functionality is not available in ESMC, but as requested I will create a new help request in ESMC.
  9. Non domain computers are not included in domain structure, they are automatically stored in Lost & Found group. Currently we do separate these clients in Dynamic groups located within "Lost & Found" and we would like to move client from these dynamic groups into our "AD structured" static groups. So it looks like this: ALL\Lost & Found\ ... pc0001 ... pc0002 ALL\Lost & Found\ Dynamicgroup1 //grouped by ip, computername, etc. ...pc0043 ...pc0088 Now, we would like to move computers pc0043 and pc0088 to our domain structure ALL\Superdomain.local\Country\City\Nondomain\ Does it make sense? Not all computers are running on domain and we would like to keep them structured in a same way like domain machines.
  10. Description: It would be very helpful to have the possibility to move computers between groups (both types) with a task Detail: If we want to move computers from Lost & Found to groups created based on AD. Currently this is not possible and we have to move computers manually.
  11. Description: Possibility to change Dashboard for standard users Detail: Standard ESMC users (non admins) are not able to edit or adjust their dashboard configuration and they have to "stay" with the default template. Any change their made is not saved. It would help a lot if they could re-configure dashboard with available predefined reports.
  12. Hello there, I am trying to create a policy from requested client configuration. I was able to convert this configuration to a policy but it is not possible to change/disable some parts in it. For example I cannot disable some parts in "Real time & Machine learning protection", these reapear always enable. System details: ESET Security Management Center (Server), Version 7.2 (7.2.1266.0)ESET Security Management Center (Web Console), Version 7.2 (7.2.221.0) p.s. support ticket was created yesterday, but no feedback, yet.
  13. Our tempDB was configured with a size limit and It looks like the last module update was the reason why tempDB has grown to it's maximum size. Everything is working fine after size limit of tempDB was increased.
  14. Looks like issue was in the tempDB configuration within MSSQL.
  15. Has anyone experienced issues after last ESMC module updates? When update was finished, I was asked to reload the console. After doing that, error messages appeared in every "window" or dashboard. One hour later, ESMC console is just loading and loading. Any suggestions? Is there something still running in the background? Version details: ESET Security Management Center (Server), Version 7.2 (7.2.1266.0) ESET Security Management Center (Web Console), Version 7.2 (7.2.221.0) Update module1021 (20200218) Translation support module1805 (20200619) SysInspector module1278 (20200609) SSL module1048 (20200608) Push Notification Service module1064 (20200625) Configuration module1822.4 (20200505)
  16. I think that reporting about non working LiveGrid is new feature of 6.6 client. Eset LiveGrid need to have internet access. Check if required communication ports are open. Ports and addresses required to use your ESET product with a third-party firewall
  17. This is a problem of DB design and it should be solved. It is also not possible to combine reports like in V5. @ Failed / Trace message - some trace messages like "Task failed in the security product" are not telling us why this task failed. You should take more closer look on this. I will add also something: Description: LOG deletion uppon Computer deletion Detail: When I delete computer from ERA console, all coresponding logs in "Threats" are deleted too. This is a "no way" for security product.
  18. I am just curious why you want to do that? Isn't it more secure to set by default some company network as known network and anything else as public? Then you can build your FW rules base on this and still you can be sure that your rules are applied in correct network.
  19. Yes, you are right. Base on my tests, deactivated computer is still visible in "Lost & Found" group but without the "icons". For client activation you can create your own Activation task under Admin > Client Tasks. When creating new task choose "Client Activation" in TASK column. Edit: Additionaly to these icons, IP address is also not visible.
  20. Then I would try to uninstall Eset Client and then use Eset Uninstaller and use it for "cleaning" all client files. Agent would be still installed.
  21. I had similar issue which was caused when client was installed first and agent last. I didn't had time to play with that so I have uninstalled Agent and client and did new installation afterwards.
  22. I would suggest to check Agent logs first. C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs
  23. Try to use CONTAINS instead of MASK. Edit: You can still use regular expressions. If you want use these, you need to change CONTAINS to REGEX.
  24. Create new firewall rule with following settings: - local ports: 53, 88, 123, 137, 138, 139, 389, 443, 445, 464, 636, 3268, 3269, 49153 - 65535 - remote IP: all your AD servers ... if you have more of them
×
×
  • Create New...