caveats for NOD32 file scanner on an Exchange server

Are there any recommendations or caveats for running NOD32 on a server running Exchange? I'm referring to the file system scanner, not NOD32 for Exchange. I would assume some file/folder exclusions would be good, such as the Exchange database folder, the transaction log folder, and the Mailroot folder as those are hugely active folders. Their content (email) basically will get scanned by NOD32 for Exchange, regardless.

Just wanted to make sure there weren't any special procedures for putting a NOD32 file system scanner onto a server running Exchange.
Thanks.

 

try here, exclusions for exchange are under number 7

 

Good deal, thanks. Pretty much what I had figured, but they added a couple of interesting folders to the exclusion list I might not have considered, notably the inetsrv folder. (And since we're not running the full protection suite, only the basic nod32, I don't have to worry about much of the other settings.)