I had cnfg the exclusions on amon on the server where xmon is scanning exchange (SBS2003). Everything seemed to be ok and amon stopped scanning and bringing up alerts. But now amon is active again. I read this: To definately exclude a file from scanning by AMON, it has to be entered twice. Once in todays naming convention, (complete path) and once in the 8.3 naming convention. (complete path) Is this related to an older ver of nod? I browsed for the files so I don't really follow this advice and why the path is not ok as it is. Does this relate to exchange exclusions? Apparently amon has become very active on the server and workstations. Why would this be occurring? Any ideas?