Recommendations for antivirus exclusions that relate to Operations Manager

Article ID: 975931 - View products that this article applies to.
INTRODUCTION
This article introduces some recommendations for antivirus (AV) exclusions that relate to System Center Operations Manager.

INTRODUCTION This article introduces some recommendations for antivirus (AV) exclusions that relate to System Center Operations Manager 2007 and System Center Operations Manager 2012
Expand all | Collapse all

On This Page

More information

Exclusions by process executable

You must be very careful when you add exclusions that are based on executables. Incorrect exclusions prevent some potentially dangerous programs from being detected. Therefore, we do not recommend that you rely on exclusions that are based on any process executables for for Operations Manager servers. However, if you have to make exclusions that are based on the process executables, use the following processes:
  • monitoringhost.exe (Operations Manager 2007)
  • monitoringhost.exe (Operations Manager 2012)

Exclusions by Directories

 The following directory-specific exclusions for Operations Manager include real-time scans, scheduled scans, and local scans. These directories that are listed are default application directories. Therefore, you may have to modify these paths based on your specific environment. Only the following Operations Manager-related directories should be excluded.  

Important When a directory that is to be excluded has a directory name greater than 8 characters long, add both the short and long directory names of the directory to the exclusion list. These names are required by some AV programs to traverse the subdirectories.

SQL Database Servers

These exclusions include the SQL Server database files that are used by Operations Manager components and the system database files for the master database and for the tempdb database. To exclude these files by directory, exclude the directory for the .ldf and .mdf files.

For example:
  • C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
  • D:\MSSQL\DATA
  • E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Log

Operations Manager (Management Servers, Gateways and Agents)

These exclusions include the queue and log files that are used by Operations Manager. 

For example:

C:\Program Files\System Center Operations Manager <version>\Health Service State\Health Service Store

Where <version> is 2007 for Operations Manager 2007 or 2007 R2

or

C:\Program Files\System Center 2012\Operations Manager\<Component>\Health Service State\Health Service Store

Where <Component> is Agent or Server for Operations Manager 2012

Exclusion of File Type by Extensions

The following file name extension-specific exclusions for Operations Manager includes real-time scans, scheduled scans, and local scans.

SQL Database Servers

These exclusions include the SQL Server database files that are used by Operations Manager components and the system database files for the master database and for the tempdb database.

For example:
  • MDF
  • LDF

Operations Manager (Management Servers, Gateways and Agents)

These exclusions include the queue and log files that are used by Operations Manager.

For Example:
  • EDB
  • CHK
  • LOG
Note Page files should also be excluded from any real-time scans.

Properties

Article ID: 975931 - Last Review: July 31, 2012 - Revision: 1.3
Applies to
  • Microsoft System Center Operations Manager 2007
  • Microsoft System Center Operations Manager 2007 R2
  • Microsoft System Center Operations Manager 2007 Service Pack 1
  • Microsoft System Center 2012 Operations Manager
Keywords: 
kbinfo kbhowto kbsurveynew kbexpertiseinter KB975931

Give Feedback