Right from the online CHM file entry on virus scanning exclusions. I had a bit of trouble finding this, even though I knew it was there. A colleague reminded me of this, so I thought I would throw up a quick reference so I can always find it. I had a client ask me this question, and my response was “the entire install structure, the standard SQL exclusions, and the file share location.
Here is the link to the official material, and below is the data copied from that link so I don’t have to go hunting for it! Note that the Lync file share is not on this list; however, I have seen some issues with meeting content when the server is actively scanning that location. I cannot say for certain that the virus scanning on the server was causing the issue, but I do know that disabling the virus program on the server fixed the issue. On the client side, it appears that some client virus engines get in the way of certain Lync functions unless you specifically add the Communicator.exe program to the engine’s allowed programs.
Specifying Anti-Virus Scanning Exclusions
To ensure that the antivirus scanner does not interfere with the operation of Microsoft Lync Server 2010, you must exclude specific processes and directories for each Lync Server 2010 server or server role on which you run an antivirus scanner. The following processes and directories should be excluded:
- Lync Server 2010 processes:
- SQL Server processes:
- %ProgramFiles%\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\SQLServr.exe
- %ProgramFiles%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
- %ProgramFiles%\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Bin\MSMDSrv.exe