Configuration Manager Current Branch Antivirus Exclusions

brmcmill · ‎Feb 07 2021

Hey everybody! My name is Brandon McMillan and I am a Microsoft Endpoint Configuration Manager (ConfigMgr) CE at Microsoft. ConfigMgr Current Branch has been the standard service-based model since December 2015 with the release of version 1511. You may have noticed that with the continuous improvements, your antivirus exclusions also need to be kept up to date. I hope this will provide you with important antivirus exclusions you could consider implementing within a Current Branch environment.

This blog will provide a comprehensive list of the following referenced Microsoft Support and Microsoft Docs articles we have released along with other recommendations you could consider for your environment. Please reference the following articles for further guidance.

822158: Virus scanning recommendations for Enterprise computers that are running currently supported versions of Windows - Last Review: Mar 14, 2022
Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems, and Clients - Last Review: Oct 28, 2022
309422: How to choose antivirus software to run on computers that are running SQL Server - Last Review: Dec 22, 2022
Docs Article: Antivirus software that is not cluster-aware may cause problems with Cluster Services - Last Review: Feb 23, 2023
Docs Article: A 0-byte file may be returned when compression is enabled on a server that is running IIS - Last Review: Jan 24, 2022
900638: Multiple symptoms occur if an antivirus scan occurs while the Wsusscan.cab file or the Wsusscn2.cab file is copied - Last Review: Jan 25, 2021
Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server - Last Review: Nov 30, 2022

If you are using Microsoft Defender as your antivirus product, please reference the following articles for further information and recommendations. Microsoft Defender Antivirus already includes many automatic exclusions as defined by the specified server role.

Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server
Docs Article: Configure and validate exclusions based on file extension and folder location

Update: March 25th, 2023

Updated recommendations from the following articles:
- Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems, and Clients
- 309422: How to choose antivirus software to run on computers that are running SQL Server
- Docs Article: Antivirus software that is not cluster-aware may cause problems with Cluster Services
- Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server
Changes are highlights in blue.

IMPORTANT: Antivirus real-time protection can cause many problems on Configuration Manager site servers, site systems, and clients. We recommend to always test before implementing any of these changes in a production environment. We strongly encourage you to evaluate the risks that are associated with implementing these changes. We recommend that you temporarily apply these procedures to evaluate a system. If you choose to implement these changes in your environment, ensure you take any additional precautions necessary. Please refer to your antivirus vendor’s documentation for further guidance and recommendations.

The recommendations for each section are separated between "Operational" and "Performance" levels. Operational recommendations are highly encouraged to be added to your exclusions list. Performance recommendations should only be considered if you are experiencing such issues that may be a result of your antivirus product.

The following information will cover what could be recommended for your environment.

Details on the variables referenced:

<InstallDrive> can be multiple drives in some environments, so it is best to use a wildcard if possible for the antivirus solution you have deployed throughout your environment. Please refer to your vendor’s documentation for further instructions.
<InstanceName> is the name of the SQL instance you are using in your environment. Please be aware if you use any named SQL instances or the default, "MSSQLServer".
<SQL Version> is the version of SQL you are using in your environment. This may also differ between each SQL service referenced between versions SQL Server 2005-2008 R2 and SQL Server 2012 or higher. Please be aware of what version you have installed. KB309422 and the article below can provide you with more details.

How to determine the version, edition and update level of SQL Server and its components

Core Exclusions for Supported Versions of Windows

Operational

%allusersprofile%\NTUser.pol
%userprofile%\NTUser.dat
%windir%\Security\Database\*.chk
%windir%\Security\Database\*.cmtx
%windir%\Security\Database\*.csv
%windir%\Security\Database\*.edb
%windir%\Security\Database\*.jrs
%windir%\Security\Database\*.log
%windir%\Security\Database\*.sdb
%windir%\Security\Database\*.xml
%windir%\SoftwareDistribution\Datastore\Datastore.edb
%windir%\SoftwareDistribution\Datastore\Logs\edb.chk
%windir%\SoftwareDistribution\Datastore\Logs\edb*.jrs
%windir%\SoftwareDistribution\Datastore\Logs\tmp.edb
%SystemRoot%\System32\GroupPolicy\Machine\Registry.pol
%SystemRoot%\System32\GroupPolicy\Machine\Registry.tmp
%SystemRoot%\System32\GroupPolicy\User\Registry.pol
%SystemRoot%\System32\GroupPolicy\User\Registry.tmp
%ProgramData%\Microsoft\Search\Data\Applications\Windows\windows.edb

For further information regarding recommended exclusions for server roles such as a Domain Controller, DFS, DHCP, or DNS, please refer to the article below.

Reference: 822158, Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server

ConfigMgr Core Installation Exclusions (All Versions)

Operational

<InstallDrive>\Program Files\Microsoft Configuration Manager\Inboxes\
<InstallDrive>\Program Files\Microsoft Configuration Manager\Install.map
<InstallDrive>\Program Files\Microsoft Configuration Manager\Logs
<InstallDrive>\SCCMContentLib
- NOTE: If you are using a remote content library, this may exist on a different server.

Performance

<InstallDrive>\<ConfigMgr Backup Directory>

Ex. D:\CMBackup

<InstallDrive>\<ConfigMgr Package Source Files>
- Ex. D:\CMSource

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,..., Configuration Manager 2012 Antivirus Exclusions

ConfigMgr Core Installation Exclusions (Current Branch Versions)

Operational

<InstallDrive>\Program Files\Microsoft Configuration Manager\cd.latest
<InstallDrive>\Program Files\Microsoft Configuration Manager\EasySetupPayload

Performance

<InstallDrive>\Program Files\Microsoft Configuration Manager\AdminUIContentPayload
<InstallDrive>\Program Files\Microsoft Configuration Manager\AdminUIContentStaging
<InstallDrive>\Program Files\Microsoft Configuration Manager\CMUClient
<InstallDrive>\Program Files\Microsoft Configuration Manager\CMUStaging
<InstallDrive>\Program Files\Microsoft Configuration Manager\ISVTemp
<InstallDrive>\Program Files\Microsoft Configuration Manager\PilotingUpgrade
<InstallDrive>\Program Files\Microsoft Configuration Manager\RLAStaging

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,...

ConfigMgr Management Point Exclusions

The following recommendations are dependent on the state of the system when the Management Point role is assigned. Please review the current state of your environment to determine which of the following paths should be excluded.

Operational

<InstallDrive>\Program Files\Microsoft Configuration Manager\MP\OUTBOXES
<InstallDrive>\Program Files\SMS_CCM\Logs
<InstallDrive>\Program Files\SMS_CCM\PolReqStaging\POL00000.pol
<InstallDrive>\Program Files\SMS_CCM\ServiceData
<InstallDrive>\Program Files\SMS\Logs
<InstallDrive>\Program Files\SMS\MP\OUTBOXES
<InstallDrive>\SMS_CCM\Logs
<InstallDrive>\SMS_CCM\PolReqStaging\POL00000.pol
<InstallDrive>\SMS_CCM\ServiceData
<InstallDrive>\SMS\Logs
<InstallDrive>\SMS\MP\OUTBOXES
%windir%\CCM\Logs

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,...

ConfigMgr Distribution Point Exclusions

Operational

<InstallDrive>\SCCMContentLib
<InstallDrive>\SMS_DP$
<InstallDrive>\SMSPKG<DriveLetter>$
<InstallDrive>\SMSPKG
<InstallDrive>\SMSPKGSIG
<InstallDrive>\SMSSIG$
%windir%\CCM\ServiceData

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,...

ConfigMgr Imaging Exclusions

Operational

<InstallDrive>\ConfigMgr_OfflineImageServicing
%windir%\TEMP\BootImages

Performance

%SystemDrive%\_SMSTaskSequence

Reference: Configuration Manager 2012 Antivirus Exclusions

ConfigMgr Process Exclusions

Operational

Client Side

%windir%\CCM\Ccmexec.exe
%windir%\CCM\CmRcService.exe
%windir%\CCM\Ccmrepair.exe
%windir%\CCMSetup\Ccmsetup.exe
%windir%\CCMSetup\autoupgrade\Ccmsetup*.exe
- NOTE: Starting in ConfigMgr Current Branch Version 1910, this file name has been changed to Ccmsetup.<Packageid>.<PackageVersion>.exe.

Server Side

%windir%\CCM\Ccmexec.exe
%windir%\SMS_CCM\Ccmexec.exe
<InstallDrive>\Program Files\Microsoft Configuration Manager\bin\x64\Cmupdate.exe
<InstallDrive>\Program Files\Microsoft Configuration Manager\bin\x64\Sitecomp.exe
<InstallDrive>\Program Files\Microsoft Configuration Manager\bin\x64\Smsexec.exe
<InstallDrive>\Program Files\Microsoft Configuration Manager\bin\x64\Smssqlbkup.exe
<InstallDrive>\Program Files\Microsoft Configuration Manager\bin\x64\Smswriter.exe
<InstallDrive>\SMS_<SQLFQDN>\bin\x64\Smssqlbkup.exe

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,...

ConfigMgr Client Exclusions

Operational

%ProgramFiles%\Microsoft Policy Platform\authorityDb\*.sdf
%windir%\CCM\*.sdf
%windir%\CCM\Logs
%windir%\CCM\ServiceData
%windir%\CCMCache
%windir%\CCMSetup
%windir%\Setup\Scripts
%windir%\SMSTSPostUpgrade

Performance

%windir%\CCM\SystemTemp

Reference: Docs Article: Recommended antivirus exclusions for Configuration Manager Site Servers, Site Systems,...

SQL Server Exclusions

Operational

SQL Server Process Exclusions

<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\MSSQL\Binn\SQLServr.exe
<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\OLAP\Bin\MSMDSrv.exe
<InstallDrive>\Program Files\Microsoft SQL Server\1<SQL Version>\Shared\SQLDumper.exe

SQL Server data files

*.ldf
*.mdf
*.ndf

SQL Server backup files

*.bak
*.trn

SQL Audit files

*.sqlaudit

SQL Query files

*.sql

SQL Trace files

*.trc

Analysis Services data files

<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\OLAP\Backup
<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\OLAP\Data
<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\OLAP\Log

Full-Text catalog files

<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\MSSQL\FTData

Replication Files
- <InstallDrive>\Program Files (x86)\Microsoft SQL Server\<SQL Version>\COM
- <InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>\COM
Replication Snapshot Files
- <InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\MSSQL\ReplData
- These files typically have file name extensions of the following:
  - *.bcp
  - *.cft
  - *.dri
  - *.idx
  - *.prc
  - *.pre
  - *.sch
  - *.trg
Checkpoint and delta files

No specific file extension for the files
Files are present under the folder structure identified by the container of type FILE_STREAM from sys.database_files

DBCC CHECKDB Files
- Files will be of the format <DATABASE_DATA_FILENAME.EXTENSION>_MSSQL_DBCC< database_id_of_snapshot>
- These are temporary files
- For more information, see the following article:
  - 2974455 DBCC CHECKDB behavior when the SQL Server database is located on a ReFS volume
Exception Dump Files

*.mdmp

Extended Event Files

*.xel
*.xem
System generated files are saved in the LOG folder for that instance.

Filestream data files

SQL 2008 and later versions
Files are present under the folder structure identified by the container of type FILE_STREAM from sys.database_files.

In-memory OLTP Files
- Present in a xtp sub-folder under the DATA directory for the instance
- File formats include the following:
  - xtp_<t/p>_<dbid>_<objid>.c
  - xtp_<t/p>_<dbid>_<objid>.dll
  - xtp_<t/p>_<dbid>_<objid>.obj
  - xtp_<t/p>_<dbid>_<objid>.out
  - xtp_<t/p>_<dbid>_<objid>.pdb
  - xtp_<t/p>_<dbid>_<objid>.xml
Remote Blob Storage files

SQL 2008 and later versions

Windows Failover Clustering (If applicable)

Drive Locations
- <Quorum Drive> (Ex. Q:\)
- %windir%\Cluster
- Temp folder for the Cluster Service account. (Ex. ..\cliusr\Local Settings\temp)
- MSDTC directory in the MSDTC drive
Processes
- %SystemRoot%\Cluster\clussvc.exe
- %SystemRoot%\Cluster\rhs.exe

Backup locations for the database files and transaction logs

References: 309422, Docs Article: Antivirus software that is not cluster-aware may cause problems with Cluster Services

SQL Server Reporting Services (SSRS) Exclusions

Operational

SSRS for SQL 2016 and below

Process Exclusions

<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe

Reporting Services Files

<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\Reporting Services\LogFiles
<InstallDrive>\Program Files\Microsoft SQL Server\<SQL Version>.<InstanceName>\Reporting Services\RSTempFiles

SSRS for SQL 2017+

Process Exclusions

<InstallDrive>\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\Bin\ReportingServicesService.exe

Reporting Services Files

<InstallDrive>\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
<InstallDrive>\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\RSTempFiles

PowerBI Report Server

Process Exclusions

<InstallDrive>\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\Bin\ReportingServicesService.exe
<InstallDrive>\Program Files\Microsoft Power BI Report Server\PBIRS\ASEngine\Bin\msmdsrv.exe

Reporting Services Files

<InstallDrive>\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles
<InstallDrive>\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\RSTempFiles

Reference: 309422

IIS Exclusions

Operational

Folder exclusions

%SystemRoot%\IIS Temporary Compressed Files
%SystemDrive%\inetpub\logs
%SystemDrive%\inetpub\temp\ASP Compiled Templates
%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files
%SystemDrive%\inetpub\wwwroot

Process exclusions

%windir%\System32\inetsrv\w3wp.exe
%windir%\SysWOW64\inetsrv\w3wp.exe
%SystemDrive%\PHP5433\php-cgi.exe

References: Docs Article: A 0-byte file may be returned when compression is enabled on a server that is running ..., Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server

WSUS Exclusions

Operational

%SystemRoot%\SoftwareDistribution\Datastore
%SystemRoot%\SoftwareDistribution\Download
<InstallDrive>\WSUS\UpdateServicesDBFiles
<InstallDrive>\WSUS\WSUSContent

Reference: 822158, Docs Article: Configure Microsoft Defender Antivirus exclusions on Windows Server

WSUS Offline Scanning Exclusions - Microsoft Baseline Security Analyzer (MBSA)

There are four distinctive methods to choose when using MBSA and WSUS offline scanning. Method 1 has the least amount of risk. If this method does not work for you, we recommend you use Method 2. Methods 3 and 4 may increase your security risk. We recommend that you use Methods 3 or 4 only if required and ensure you please take necessary precautions.

Method 1:

Exclude the following files from scanning:
- Wsusscan.cab
- Wsusscn2.cab

Method 2:

Exclude all *.cab files from scanning

Method 3:

Exclude all archived files from antivirus scanning
- %windir%\SoftwareDistribution\ScanFile

Method 4:

Exclude the folder where the Wsusscan.cab file or the Wsusscn2.cab file is located
Exclude the path of the Wsusscan.cab file or the Wsusscn2.cab file on the local computer

MBSA was largely used in situations where neither Microsoft Update nor a local WSUS/ConfigMgr server was available, or as a compliance tool to ensure that all security updates were deployed to a managed environment. While MBSA version 2.3 introduced support for Windows Server 2012 R2 and Windows 8.1, it has since been deprecated and no longer developed. MBSA 2.3 is not updated to fully support Windows 10 and Windows Server 2016.

The following script may help you as an alternative to MBSA’s patch-compliance checking with later versions of Windows:

Using WUA to Scan for Updates Offline, which includes a sample .vbs script.
For a PowerShell alternative, see Using WUA to Scan for Updates Offline with PowerShell.

References: 900638, MBSA, Wsusscn2.cab

I received numerous feedback on this post and I wanted to highlight the contributions from the following individuals: Max Baldt, David Coulter, Aaron Ellison, Julie Andreacola, Klaus Kreyenberg, and Jorge Miguel Ferreira.

Special thanks to Kevin Kasalonis, Cameron Cox, Clifton Hughes, Rushi Faldu, and Santos Martinez.

Thank you!

Brandon McMillan, Customer Engineer

Additional References:

Disclaimer: The information on this site is provided “AS IS” with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of any included script samples are subject to the terms specified in the Terms of Use.

Products (50)

Special Topics (27)

Video Hub (462)

Most Active Hubs

Most Active Hubs

Video Hub

Configuration Manager Current Branch Antivirus Exclusions