Screencasts - Hilfsvideos

Exclusions still being scanned.

Created: 15 Jan. 2013 | 5 Kommentare

I have a server that has exclusions made to a directory. D:\folder. When the scan run at its scheduled time, it seems to be locking up the system and scanning D:\folder, despite the exclusion. The exclusion is made locally on the system. The exclusion to the folder was added to the server afterwards and seems to have cleared it up. Where can I look to see if this exclusion is working properly? Or where to see if the scan is actually locking up the server when it scans the so called excluded folder?

Kommentare KommentareZum neuesten Kommentar

das Bild der Brɨans

Check the registry and esnure exclusions are there:

How to Verify if an Endpoint Client has Automatically Excluded an Application or Directory
Article:TECH105814  |  Created: 2008-01-05  |  Updated: 2011-03-02  |  Article URL http://www.symantec.com/docs/TECH105814
 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

das Bild der Rafeeqs

Enable this to check if it really scans

How to log all files and directories scanned during On-Demand / Scheduled Scan with Symantec Endpoint Protection 11.0
 
http://www.symantec.com/business/support/index?page=content&id=TECH103126
das Bild der jcocozzos

Thanks for the link Rafeeq. I have saved the link and will have to run a scan on this later due to it being a production server with a lot of data. I have to run a scan at a later time.

das Bild der jcocozzos

Do you know of any logs or places to look to see why this did not work properly, or verify that the scan locked the server up when getting to that exclusion. The scan was apparently locking up the server with the exclusions in place. The issue with doing the debug and scan, is that if it does not pick up the exclusion, it can lock up the server.

das Bild der Brɨans

You can turn on SMC debugging per this article:

How to debug the Symantec Endpoint Protection client

padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;color: #666666; background-color:#f2f2f2">Article:TECH102412 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2;"> |  padding: 0px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2;">Created: 2007-01-06 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2"> |  padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2">Updated: 2012-03-16 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2"> |  padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2">Article URL http://www.symantec.com/docs/TECH102412

The debug.log file may show something of relevence about this.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.