Antivirus scanning exclusions for Skype for Business Server
Overview of antivirus scanner interoperation with Skype for Business Server.
This article contains recommendations that may help an administrator determine the cause of potential instability on a computer that is running a supported version of Microsoft Windows when it is used with antivirus software in an Active Directory domain environment or in a managed business environment.
We recommend that you temporarily apply these procedures to evaluate a system. If your system performance or stability is improved by the recommendations that are made in this article, contact your antivirus software vendor for instructions or for an updated version of the antivirus software.
This article contains information that shows how to help lower security settings or how to temporarily turn off security features on a computer. You can make these changes to understand the nature of a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect the computer for the files that are no longer being scanned by your antivirus software.
To ensure that the antivirus scanner does not interfere with the operation of Skype for Business Server, you must exclude specific processes and directories for each Skype for Business Server server or server role on which you run an antivirus scanner. The following processes and directories should be excluded:
Folder and file locations listed below are the default locations for Skype for Business Server. For any locations for which you did not use the default, exclude the locations you specified for your organization instead of the default locations specified in this topic.
Please note that some antivirus programs may need absolute, not relative paths, for their exclusion list.
Skype for Business Server processes:
Windows Fabric Host Service processes:
SQL Server Back-End processes:
Note that these paths are specific to SQL Server version.
%ProgramFiles%\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\SQLServr.exe
%ProgramFiles%\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
%ProgramFiles%\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Bin\MSMDSrv.exe
SQL Server Front-End processes:
%ProgramFiles%\Microsoft SQL Server\MSSQL12.LYNCLOCAL\MSSQL\Binn\SQLServr.exe
%ProgramFiles%\Microsoft SQL Server\MSSQL12.RTCLOCAL\MSSQL\Binn\SQLServr.exe
Standard Edition Installation RTC Instance
%ProgramFiles%\Microsoft SQL Server\MSSQL12.RTC\MSSQL\Binn\SQLServr.exe
Directories and files:
Note that these paths are specific to Skype for Business Server version.
%programfiles%\Skype for Business Server 2015
%programfiles%\Common Files\Skype for Business Server 2015\Watcher Node
%programfiles%\Common Files\Skype for Business Server 2015
%programfiles%\Common Files\Skype for Business Online
File share store (specified in Topology Builder). File stores are specified in Topology Builder.
SQL Server data and log files, including those for the back-end database, user store, archiving store, monitoring store, and application store. Database and log files can be specified in Topology Builder. For details about the data and log files for each database, including default names, see SQL Server Data and Log File Placement in the Deployment documentation.
SQL Server data and log files, including those for the Front-end database, Skype for Business store, and RtcDatabase store. They are normally under %localdrive%\CSData.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.