Jump to content
Marcos

Future changes to ESET Security Management Center / ESET Remote Administrator

Recommended Posts

Description: change behaviour of adding new file/folder exclusions #1
Detail: I need to exclude all *.mdb files in c:\test and all subfolders
Currently I can exclude *.mdb files only in the top folder (c:\test) but not in the subfolders

Description: change behaviour of adding new file/folder exclusions #2
Detail: I would like to exclude all *.vhdx files, but without specifying folder/drive (ESMC says when setting this in policy: "Invalid path")
If I type "\*.vhdx" into the field, I can save it, but if I scan a test file manually, the log file still shows: "Number of scanned objects: 1", so the exclusion doesn't work.


Description: change behaviour of adding new file/folder exclusions #3
Detail: if I import a txt file which contains correect and incorrect folder exclusion, ESMC says: "Not all input data have been imported".
And it imports the list partially, but doesn't show the not importable item(s). It would be nice, if ESMC show a message with the incorrect, not importable items.


 

Share this post


Link to post
Share on other sites

Description: change behaviour of adding new file/folder exclusions #4
Detail: in ESMC policy, adding folder exclusions
c:\test\*    works
c:\test*\*   doesn't work, "invalid path"

Share this post


Link to post
Share on other sites

Description: ability to add process path containing environment variable:
Detail: in ESMC policy, add process exclusion
%systemroot%\System32\Vmms.exe   doesn't accept, "Invalid value"
c:\windows\System32\Vmms.exe    this works

+1: same value can be added multiple times

Edited by ludolf
+1

Share this post


Link to post
Share on other sites

Description: ability to export folder exclusions from ESMC policy
Detail: to migrate exclusions from one policy to another

Share this post


Link to post
Share on other sites
Just now, ludolf said:

Description: ability to add process path containing environment variable:
Detail: in ESMC policy, add process exclusion
%systemroot%\System32\Vmms.exe   doesn't accept, "Invalid value"
c:\windows\System32\Vmms.exe    this works

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

Share this post


Link to post
Share on other sites

here: ESMC, select policy (product: Eset File Security for Windows Server), 

Detection Engine, Processes Exclusions, Processes to be excluded from scanning

 

Share this post


Link to post
Share on other sites

@ludolf I have reported those requirements to the EP development team, as they are EP related. ESMC just visualizes policy controls, made for Endpoint. But it´s OK, that you have reported it here, as ESMC s the primary interface for controlling Endpoints.

Share this post


Link to post
Share on other sites

Description: reconsider MariaDB support

Detail: RHEL8 is coming. ESMC should try to support MariaDB, and not lock itself to some old mysql 5.6 version. it is hard to install old mysql.

Share this post


Link to post
Share on other sites

@tbsky We are not planning to add mariaDB support. Due to our journey to the cloud and also multi-platform compatibility, we will most likely work on the support of MySQL 8 for next major release of ESMC 

Share this post


Link to post
Share on other sites
19 hours ago, MichalJ said:

@tbsky We are not planning to add mariaDB support. Due to our journey to the cloud and also multi-platform compatibility, we will most likely work on the support of MySQL 8 for next major release of ESMC 

Hi:

   I think mariaDB is multi-platform compatibility also. few people like Oracle/MySQL, but it is better than nothing. at least we can install ESMC at linux :)

Share this post


Link to post
Share on other sites

Description: Checkbox 'Automaticlly Reboot when needed' default set to disabled. / off.

Detail: Currently we are executing tasks with no need for a reboot and sometimes we do. But since we also execute tasks on our servers, leaving the default setting 'checked' being quite dangerous. 

See attatchment. This is the checkbox we would like to be disabled on default. 

 

chrome_2019-02-08_14-25-32.png

Share this post


Link to post
Share on other sites

Description: Create dynamic groups for the following problem: "macOS is preventing ESET Security Product from accessing some folders."


Detail: I would like to create a dynamic group for computers with the following problem, but I can't select this problem at the new template creation, even though it's a reported problem, it's not in the list: "macOS is preventing ESET Security Product from accessing some folders."

Edited by SysEPr

Share this post


Link to post
Share on other sites

@SysEPr Thank you for pointing this out. I have created a development task for both adding this one specific problem, but also having those problems in an update-able fashion, meaning we would be able to dynamically update those capabilities when a new client with a new error is being released. 

Share this post


Link to post
Share on other sites

Description: Policy settings reverse-lookup

Detail: The ability in SMC/Endpoint Security to see which policy is responsible for which setting in effect on the computer.
Basically something like a GPRESULT report available for diagnosing Active Directory Group Policy Objects.
A very simple example of that is shown here: https://4sysops.com/wp-content/uploads/2012/02/gpresult.exe-HTML-output.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×