Author Topic: Problem concerning local File System Shield Exclusions  (Read 6113 times)

0 Members and 1 Guest are viewing this topic.

Offline e2p2

  • Newbie
  • *
  • Posts: 10
Problem concerning local File System Shield Exclusions
« on: February 22, 2013, 05:16:39 PM »
On a client I can set exclusions specific to that workstation or server.  However when computer group settings are deployed my local exclusions are lost.  I need to be able to set some unique exclusion for each server.  How can I accomplish this?

Offline j.phillips

  • Newbie
  • *
  • Posts: 10
Re: Problem concerning local File System Shield Exclusions
« Reply #1 on: February 25, 2013, 04:04:58 PM »
I'm having the same problem.  It seems as if one of my clients it doesn't matter if I set it on the individual "expert settings" on the client, or in the AEA, the client doesn't maintain the exclusion lists.

Offline Che Johnson

  • Moderator
  • Full Member
  • *
  • Posts: 140
Re: Problem concerning local File System Shield Exclusions
« Reply #2 on: February 27, 2013, 11:18:06 AM »
Well first you have to set all changes to the policy of a client in the Console, if it's done from the client it will undo any changes made.  To make the exclusions, it's best to set them in the File System Shield Exclusions and/or Auto Sandbox and behavior shield, If the application is a windows based application. If the application is Web, then add the exclusions or url to the web shield exclusions.

It's best practice to include the entire folder, not just the .exe in the path.

Remember, all exclusions must be set in the Console, unless the client is using a stand alone version and is not connected to the Console. You can make the changes to each group by right clicking on the group, go to properties, and then add the exclusions of the application in the shields that were mentioned.

Offline e2p2

  • Newbie
  • *
  • Posts: 10
Re: Problem concerning local File System Shield Exclusions
« Reply #3 on: February 27, 2013, 04:36:24 PM »
@CHE

You must understand.  That while while some exclusions can be applied globally, some must be local.  We have several Backup Exec servers that use local storage.  The entire drives must be excluded from real-time scanning.  Excluding an entire drive is not something that you want to do globally.  Until the product supports the capability of both local and global exclusions I am afraid I will not be able to deploy it at our campus.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11808
    • AVAST Software
Re: Problem concerning local File System Shield Exclusions
« Reply #4 on: February 27, 2013, 04:53:54 PM »
The exclusion can be applied to one machine only - Che just says you need to do it via the Console, not from that particular machine.

Offline Che Johnson

  • Moderator
  • Full Member
  • *
  • Posts: 140
Re: Problem concerning local File System Shield Exclusions
« Reply #5 on: February 28, 2013, 02:13:50 PM »
If you have exclusion that must be set locally then I would recommend that you create a group for these clients that need to have exclusions that are not global but local. They can still be managed but their policy exclusions can differ from the other clients in the console.  They must be done from the Console, all policy changes should be made from here but if you have unique settings for the Back Up servers, I would recommend to put them in a separate group  with policies and exclusions different from the others.