Antivirus Exclusions for SharePoint 2013

We were doing an on-premises install of SharePoint 2013 this week, and realized there wasn’t an easy to find, friendly versions of the following antivirus exclusion information. It’s best to set the scan exclusion on these folders before letting business users into Production.

If you have an issue where your users are getting the dreaded “Access Denied” message when trying to upload documents, then it’s possible you may have forgotten this step. And it may take you ages to figure out why.

I won’t repeat the details and links from Colin Phillips’ post on Antivirus Exclusions for SharePoint 2010 and SQL Server 2012 (link), so…

Microsoft tells you that if you’re running file-level antivirus software in your SharePoint applications, then you need to exclude certain folders from scans (link). There are lots of great details there, but I’ll assume that you’re here for quick access to the SharePoint Server 2013 info:

Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15Logs

Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15DataApplications

Drive:WindowsMicrosoft.NETFramework64v4.0.30319Temporary ASP.NET Files

Drive:UsersServiceAccountAppDataLocalTempWebTempDir 

Drive:ProgramDataMicrosoftSharePoint

Drive:Usersaccount that the search service is running asAppDataLocalTemp 

Drive:WINDOWSSystem32LogFiles 

Drive:WindowsSyswow64LogFiles

Drive:Program FilesMicrosoft Office Servers15.0Data 

Drive:Program FilesMicrosoft Office Servers15.0Logs 

Drive:Program FilesMicrosoft Office Servers15.0Bin 

Drive:Program FilesMicrosoft Office Servers15.0Synchronization Service

If the index files are configured to be located in a different folder, you also have to exclude that location.

Any location in which you decided to store the disk-based binary large object (BLOB) cache (for example, C:Blobcache).

Play safe, and keep your stick on the ice.