Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 18984 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Variable Folder Exclusions in Settings

Dekkar

Hi, moving to the current version of SEC after deciding to leave my old SEM infrastructure asleep for the past year or so.

My old SEM On-Access Scan Settings allowed me to exclude things like

%temp%\NetRight

%USERPROFILE%\AppData\Roaming\Interwoven\

The newer version doesnt seem to have this ability, if I enter one of the above I get Invalid exclusion entered. (I tried Folder and FIle)

Having these exclusions is a pre-requisite of our DMS, so its critical that this is possible.

Is there something Im doing wrong?

Thanks,
Nathan

:58108


This thread was automatically locked due to age.
Parents
  • 0

    Hello Nathan,

    we need to exclude

    basically a scan delays an open (or close) and thus should be transparent for an application as far as the application's logic is concerned. Problems usually arise when an application either employs some nifty access or makes unjustified assumptions about a file system's behaviour.

    we never had problems

    Likely there aren't any - scanners and how they implement "real-time" scanning have been improved over time and many reservations are no longer well-founded.

    excluding folder

    as said (I haven't tested it recently but it should be fairly easy to do) a "qualified" file exclusion should work for a specific folder (but this exclusion the applies to all file systems - you can't restrict such an exclusion to just C:\Users).You can't use the *.* pattern but you can use ?s in one part and * in the other.  

    Christian

    :58129
Reply
  • 0

    Hello Nathan,

    we need to exclude

    basically a scan delays an open (or close) and thus should be transparent for an application as far as the application's logic is concerned. Problems usually arise when an application either employs some nifty access or makes unjustified assumptions about a file system's behaviour.

    we never had problems

    Likely there aren't any - scanners and how they implement "real-time" scanning have been improved over time and many reservations are no longer well-founded.

    excluding folder

    as said (I haven't tested it recently but it should be fairly easy to do) a "qualified" file exclusion should work for a specific folder (but this exclusion the applies to all file systems - you can't restrict such an exclusion to just C:\Users).You can't use the *.* pattern but you can use ?s in one part and * in the other.  

    Christian

    :58129
Children
No Data
Unfiltered HTML