Best way to exclude folders in FIM 6.1

I think you simply exclude it in your selection when you are setting up your conditions and browsing for Drives and Folders to watch. I don't know if there is another way for accomplishing the same goal.

Regarding the multiple hits on the same file, I am also wondering about that. FIM is reporting too many instances of the exact same events under FIM.

The way I am doing it now is selecting each folder in a the tree and choosing the non-recursive option. What I don't know is if the overhead on the server is more with a bunch of non-recursive selections, then if I do the entire root folder recursively. It may be the only way to do it.

I'm also looking for an answer to this question.   As an example scenario, I'm monitoring a file system on a SQL Server database server.  I want to know every time a file is created on the system with a few exceptions.  I don't want to know when .MDB or .LDB files are created.  I don't want to know when certain logs are written to.  Is there a NOT ( ! ) option that will allow me to define a folder, a wildcard, or an individual file I want to ignore?  

I agree, this would be a nice enhancement. I had the same question when I came to this board.

I just started rolling FIM out for a PCI requirement and noticed this issue as well....We have some folders in our environment with special config files we don't want touched, this same folder has app logs that are constantly changing.

It would be nice if we could configure "exclusions".  Right now we're looking at making 20 individual file monitors...making 2-3 exclusion would be easier, or having the ability to ignore extensions.....like exclude " *.log " in the folder.

I have a feature request open for FIM to address the differing amounts of windows read events created when a file is opened (one per thread). What I want is a FIM event that triggers when >1 windows event is created, furthermore I want to ignore the NT\Authority events and focus on the DOMAIN\user event.

I have also noticed the file type seems flawed, when I set FIM on a .csv file I get events when my FIM is set at *.* but not when it is set at *.csv

I think FIM has the potential to be a great tool with a bit more work