Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2009-07-22
This topic describes the effects of file-level antivirus programs on computers that are running Microsoft Exchange Server 2007. If you implement the recommendations described in this topic, you can enhance the security and health of your Exchange organization.
File-level scanners are frequently used. However, if they are configured incorrectly, they can cause problems in Exchange 2007.
There are two types of file-level scanners:
The following problems may occur when you use file-level scanners with Exchange 2007:
If you are deploying file-level scanners on Exchange 2007 servers, make sure that the appropriate exclusions, such as directory exclusions, process exclusions, and file name extension exclusions, are in place for both scheduled and real-time scanning. This section describes directory exclusions, process exclusions, and file name extension exclusions for each server or server role.
You must exclude specific directories for each Exchange server or server role on which you run a file-level antivirus scanner. This section describes the directories that you should exclude from file-level scanning for each server or server role.
Get-StorageGroup -server <servername>| fl *path*
Get-MailboxDatabase -server <servername>| fl *path*
Get-PublicFolderDatabase -server <servername>| fl *path*
Get-MailboxServer <servername>| fl *path*
All the items listed in the Mailbox server role list, and the following:
Get-TransportServer <servername>| fl *logpath*,*tracingpath*
Get-TransportServer <servername>| fl *dir*path*
In addition to the directories that contain antivirus engine and configuration files, exclude the directory on the shared storage used for ForeFront data.
To determine the path that ForeFront uses on an SCC, check the value of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Exchange Server\DatabasePath
Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.
Many file-level scanners now support the scanning of processes. This too can adversely affect Microsoft Exchange if the incorrect processes are scanned. Therefore, you should exclude the following processes from file-level scanners.
Cdb.exe
Microsoft.Exchange.Search.Exsearch.exe
Cidaemon.exe
Microsoft.Exchange.Servicehost.exe
Cluster.exe
Msexchangeadtopologyservice.exe
Dsamain.exe
Msexchangefds.exe
Edgecredentialsvc.exe
Msexchangemailboxassistants.exe
Edgetransport.exe
Msexchangemailsubmission.exe
Galgrammargenerator.exe
Msexchangetransport.exe
Inetinfo.exe
Msexchangetransportlogsearch.exe
Mad.exe
Msftefd.exe
Microsoft.Exchange.Antispamupdatesvc.exe
Msftesql.exe
Microsoft.Exchange.Contentfilter.Wrapper.exe
Oleconverter.exe
Microsoft.Exchange.Cluster.Replayservice.exe
Powershell.exe
Microsoft.Exchange.Edgesyncsvc.exe
Sesworker.exe
Microsoft.Exchange.Imap4.exe
Speechservice.exe
Microsoft.Exchange.Imap4service.exe
Store.exe
Microsoft.Exchange.Infoworker.Assistants.exe
Transcodingservice.exe
Microsoft.Exchange.Monitoring.exe
Umservice.exe
Microsoft.Exchange.Pop3.exe
Umworkerprocess.exe
Microsoft.Exchange.Pop3service.exe
W3wp.exe
If you are also deploying ForeFront Security for Exchange Server, exclude the following processes.
Adonavsvc.exe
Fscstatsserv.exe
Fsccontroller.exe
Fsctransportscanner.exe
Fscdiag.exe
Fscutility.exe
Fscexec.exe
Fsemailpickup.exe
Fscimc.exe
Fssaclient.exe
Fscmanualscanner.exe
Getenginefiles.exe
Fscmonitor.exe
Perfmonitorsetup.exe
Fscrealtimescanner.exe
Scanenginetest.exe
Fscstarter.exe
Semsetup.exe
In addition to excluding specific directories and processes, as a secondary measure, in case directory exclusions fail or files are moved, you should exclude the following Exchange-specific file name extensions.
.ci
.wid
.001
.dir
.000
.002
.avc
.dt
.lst
.cab
.fdb
.mdb
.cfg
.fdm
.ppl
.config
.ide
.set
.da1
.key
.v3d
.dat
.klb
.vdb
.def
.kli
.vdm
The file name extensions listed for ForeFront Security for Exchange Server are the signature files from various antivirus directory engines. In most cases, these file name extensions do not change, but file name extensions may be added in the future as third-party antivirus vendors update their antivirus signature files.
Ideally, you should be scanning for virii/spam at either the Edge or Hub Transport servers (or a perimeter device that email is delivered thru, such as IronPort) plus employing a desktop AV solution that's email-aware. As mentioned above, you can also just use an Exchange-aware AV product, one that utilizes the VSAPI. I've never understood file-level scanning on Exchange servers - If you are scanning at the perimeter and at the desktop/Inbox, how is a virus supposed to get to your Exchange servers? At that point you have much bigger worries than a file-level Exchange scan.
· The temporary folder that is used to perform content conversion. By default, this is the server’s TMP folder. --> I'm probably reading more into this but wanted to validate the correct folder (running Win2008 64BIT). Is the "TMP" folder actaully "C:\Windows\Temp" or another folder? There is a "TMP" folder under documents and settings for each local user profile but that doesn't make sense. I'm sure this is simple but wanted to validate 100% for the exclusion list. Thanks