Author Topic: conflicts with LANDesk  (Read 2137 times)

0 Members and 1 Guest are viewing this topic.

Offline greggs

  • Newbie
  • *
  • Posts: 2
conflicts with LANDesk
« on: November 08, 2013, 12:22:04 AM »
We are long-time users of LANDesk management software.  We are gradually phasing to Avast Endpoint Protection from another anti-virus product.  Our users are frequently getting a notification window from Avast that one of the LANDesk modules is a "dropper" and has been blocked.  Attached is a screen shot of the submission of the "false positive" report.

Is there a way in Avast to white-list all LANDesk software so that it is not triggering these notifications?

Thanks.

g

Offline jsnyder

  • Newbie
  • *
  • Posts: 10
Re: conflicts with LANDesk
« Reply #1 on: November 08, 2013, 08:02:33 PM »
You should be able to go into the file system shield and set an exclusion for: C:\Program Files\LANDesk\*

Let me know if that works or not.

Offline greggs

  • Newbie
  • *
  • Posts: 2
Re: conflicts with LANDesk
« Reply #2 on: November 22, 2013, 07:19:26 PM »
It sorta works.  The difficulty is that it's not global.  On multi-user computers, e.g. W7 Pro on an ADDS domain, a new profile is created for each user, and the exception appears to be stored in the profile.  So each new user encounters the same problem when LANDesk does its periodic inventory scan.

g

Offline jsnyder

  • Newbie
  • *
  • Posts: 10
Re: conflicts with LANDesk
« Reply #3 on: November 22, 2013, 07:28:50 PM »
Oh yea that's why you want to do it globally.  If you use the Enterprise Administration Console right click on computer catalog and choose properties.  Go to file system shield/exclusions and put in the exclusion there.  That will force all Avast clients to update and make it available for all users.