tmuster2k 22 Posted April 14, 2021 Share Posted April 14, 2021 I have a drive letter that I need to exclude from scanning. I wanted to add for example e:\* but when i do this in my Policy for Performance exclusions it doesn't like it and shows in red. If I do e:\*. then it will go through. Will this wildcard make sure that no files will get scanned in real time? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,909 Posted April 14, 2021 Administrators Share Posted April 14, 2021 It is not possible to exclude whole drives for security reasons. Could you please elaborate more on the use case? Link to comment Share on other sites More sharing options...
tmuster2k 22 Posted April 14, 2021 Author Share Posted April 14, 2021 1 hour ago, Marcos said: It is not possible to exclude whole drives for security reasons. Could you please elaborate more on the use case? @Marcos Please reference this web page >> https://helpdesk.egnyte.com/hc/en-us/articles/218926917 NOTE: customer did process exclusions for EgnyteClient.exe, EgnyteDrive.exe, EgnyteSyncService.exe, EgnyteUpdate.exe in the policy but the article is suggesting exclusion of the whole drive letter for Egnyte drive letter. I am not familiar with this program as it is something the customer implemented a while back. This link has info on what it does >> https://www.egnyte.com/blog/2021/02/12780evaluating-mysql-recursive-cte-at-scale/?_ga=2.213699793.418197318.1618429060-2050841226.1618429060 Based on what this program does, do the process exclusion should suffice? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,909 Posted April 15, 2021 Administrators Share Posted April 15, 2021 I'd recommend trying process exclusions. Generally exclusions are not a panacea to prevent issues 100% since clashes may occur before exclusions are evaluated so without a test it's impossible to predict what could happen. Link to comment Share on other sites More sharing options...
Recommended Posts