Exchange 2007 Working and Conversion folder Exclusions: \Temp (some content conversions are performed in this folder) %ProgramFiles%\Microsoft\Exchange Server\MDBTEMP\ %ProgramFiles%\Microsoft\Exchange Server\Working\OleConvertor\
Drive\Documents and Settings\*the account that the search service is running as*\Local Settings\Temp\ Drive:\WINDOWS\system32\LogFiles
Note If you use a specific account for SharePoint services or application pools identities, you may also have to exclude the following folders, replace *ServiceAccount with account name: Drive:\Documents and Settings\*ServiceAccount*\Local Settings\Application Data Drive:\Documents and Settings\*ServiceAccount*\Local Settings\Temp
Drive:\Program Files\Microsoft Office Servers (And all subfolders)
Drive:\Program Files\Microsoft Office Servers\12.0\Data\ (This folder is used for the indexing process. If the Index files are configured to reside in a different folder, you also have to exclude that location.)
Microsoft SQL Server 2000/2005/2008 _ _ _ _ _ _ _ _ _ _ _ _
SQL Server data files: -
.mdf .ldf .ndf
SQL Server backup files: -
Analysis Manager Data and Temp folder.
DRIVE:\Program Files\Microsoft SQL Server\**\OLAP\Data\ (MSSQL folder name can be MSSQL.1 or MSSQL.2 etc etc. Using a '**' allows any number to be allowed in mcafee) DRIVE:\Program Files\Microsoft SQL Server\**\OLAP\Backup\ DRIVE:\Program Files\Microsoft SQL Server\**\OLAP\Log\
Folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in Windows SharePoint Services 3.0 or in SharePoint Server 2007 http://support.microsoft.com/kb/952167
Something that I haven't seen mentioned is whether or not there is a simple (read "easy") way to enter these many, many exclusions into your ePo-managed policies rather than the line-by-line-by-line-by-line method.
And, if there isn't, why not? 'Twould make sense if there were pre-configured generic exclusion packages based upon the OS being protected. Something for the future, perhaps?
I did it by exporting, modifiying and importing XML file. It wasn't too hard.
edit - I do agree though, it is a real pain that there is no way to simply import a text file with a list of exclusions etc, it really is a hassle.
As I say the best way around it I found is to enter the data once, then export those entries as an xml, then export the policies of the place you want to add it to, then modify that one, then re-import it. Not that hard, but still a pain in the butt, would be much better if we could simply import it.
Guess this is now getting off topic of the thread though...