Video Screencast Help

Exclusions still being scanned.

Created: 15 Jan 2013 | 5 comments

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?

Comments 5 CommentsJump to latest comment

_Brian's picture

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


Rafeeq's picture

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
jcocozzo's picture

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.

jcocozzo's picture

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.

_Brian's picture

You can turn on SMC debugging per this article:

How to debug the Symantec Endpoint Protection client

Article:TECH102412  |  Created: 2007-01-06  |  Updated: 2012-03-16  |  Article URL

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