stefanzman

If there are no policies defined or assigned at all, will the endpoint operate on some sort of default behavior? See additional screen below.

Thanks for the reply Martin. I have changed the the access group to several different options, and the list is never populated. It always shows empty.

One of our clients is running a hosted ESMC 7. Here is the version info: ESET Security Management Center (Server), Version 7.0 (7.0.471.0)ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) For some reason, the list of Built-in Policies is empty. I have tried refreshing and clicking on Show Unassigned, but nothing shows (see screen below) Is it possible to restore these? If not, can some of the original default policies (like Balanced) be downloaded and imported from somewhere?

Thanks for the reply, itman. Yes. I did try mapping the containing folder to a drive and entering the process exclusion that way. It was still not accepted. Seems the ESET software knows it is a network drive. Very strange. This seems like a notable limitation or oversight, right? Cannot image this has not been encountered before.

We have an app / process that needs to be excluded from real-time protection, and it is located on a network share. When we try add the path to the .exe file, the application baulks saying the item is invalid. It seems only be an issue with with the process on the network share with a path like "\\myserver\myfolder\myprogram.exe", as doing the same with "C:\myserver\myfolder\myprogram.exe" works fine. The problem is that this process *is* located on the network, and I need to exclude it. How is this done? Thanks@