bbahes

Description : Add variable for COMPUTER DESCRIPTION Details: We use COMPUTER DESCRIPTION to denote workstation position and/or users and would like to include this field in notification messages.

@MichalJ License key and Public ID are same as last year. It should be noted that this is test system and both ESMC and client are in virtual machines which where in saved state. It could be that ESMC did not sync with EBA. For me, confirmation that this is automatic process is solution. Thanks for response!

Description: Automatic product activation on license renewal Detail: I can't find option in ESMC for endpoint automatic license activation after renewal. I only find option on client "Activate this product if you already have a renewal key or a new license." It would be most welcome to have this feature automated. For example, when license is synced with EBA account, automatic activation of endpoint would be triggered either by endpoint like with updates, if you can't access activation server via proxy, then go directly to ESET servers. On my test system I had to create client task to

I was able to add this path to Firewall rule. Where are you adding this rules?

Description: Change CONNECT option from RDP to VNC on client.Detail: Please add ability to change RDP connection to client to VNC.

Description: Add ADD FILTERING option in "pop up" formsDetail: Please add ability to filter in all forms through the entire product. It's hard to scroll and read through so many options. One extra request would be to turn on by default filter by name. No filter: Filter available: Default filter by name:

Description: LAST EXECUTION column in Server TasksDetail: I can't seem to be able to find Last Execution column in Server Tasks? It would be useful to have same information in columns available for same categories of information. At the moment we have to open each task and select Executions tab. Server tasks: Client tasks:

We've had situations where ESET had problems with antivirus database (usually many false positives with web filtering) where we had to revert to previous version. However, that was not main focus for us since fix was delivered in few hours, but we had quick overview of what clients had which version in comparison to ESET server or ERA server.

Description: Agent logs in Endpoint productDetail: It would be practical to have agent log in Endpoint product Log Files for easier export and review.

Description: Policy revision Detail: It would be very welcome feature if policy had revision tab, so we can see what has changed over time. This revision tab would, if implemented, allow us to see all settings in tree view. At the moment we have to go to policy and drill down entire policy to get a look what settings we had in previous policy. Maybe this has already been requested in different form, like I had previously in this topic

I've noticed they have this task out of the box:

I would prefer if in future releases they automate this internally. I know about this problem in old releases but we have policy about who does what and when so we did not have this problems with v5.

This is big flaw in design and you should revert back to old one. If some organizations have problems with endpoint control, internal organization it should not have been reason to fix these problems with product philosophy. If for some reason endpoint is gone from ERA, than this is mayor security incident inside organization, that should be addressed in other way with internal policies or procedures. This design leads to many potential confusions in reports and management if situation would arise that endpoint was renamed and rename task fails.

Description: Consistent licensing/display with regards to renaming endpoint Detail: I'm testing ESMC v7 and Endpoint v7 and I see different results when: 1. Rename client (hostname) on client itself We use All-in-one installer for clients. They are installed when computer has generic name (in case of Windows 10 that is something like DESKTOP-0LALO37). The Endpoint and agent install and report back to ESMC successfully. If we then rename client (technical staff, by either on site or via remote support VNC) to something else we only see change in FQDN property. However in list

Description: Update First steps and best practices Detail: May I suggest that you update your help documentation or somehow automate this step, that when ESMC server is first launched, Update Operating System Task is one of first things to do? This is mainly because Alerts are shown "Operating system is not up to date". Also, I'm guessing, it's best security practice, since it's security product. Would you agree? Also while on this subject: Description: Task executions - more details would be welcome Detail: I have started Update Operating System task via context menu. Howe