Issue on recording a Web Browser Session in SCOM 2012 R2 with Windows 2012 R2

When recording a “Web Browser Session” I regularly bump into the same issue. The record button is missing while doing a capture. This is very annoying but I always follow the same solutions to fix the issue. Underneath a recap on how to fix this issue.

-Be sure the x64 version of internet explorer is running, you can check this in the task manager in the properties of the Internet Explorer, be sure that it’s located in C:\Program files\Internet Explorer\iexplore.exe
ScreenHunter_101 Jul. 09 11.49

-Enable Internet Explorer Options by clicking IE settings, internet options:
Advanced – Security – Enable Enhanced Protected Mode
Advanced – Browsing – Enable third-party browser extensions

Shutdown all IE browser sessions and open Regedit (runas Administrator)
– Browse to the following regkey: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main
– Add a new DWORD called TabProcGrowth and set it to 0
Next
– Browse to the following regkey: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64\
-You should see two subkeys labeled: (These are the cached BHO IE objects related to the Web Recorder)
{00021493-0000-0000-C000-000000000046}
{00021494-0000-0000-C000-000000000046}
Delete only the above two mentioned keys (This will force IE to recache them next launch)

Restart the web capture, when IE Launches enable the add-on again if you are prompted.
Web Recorder SCOM

– If you still don’t see the Web-Recorder pane in IE you can now show it by:
–  Internet Explorer Options by clicking IE settings, internet options, view, explorer bars, web recorder
ScreenHunter_103 Jul. 09 12.00

Problem solved!

 

 

Upgrade SCOM 2012 SP1 to R2

Below a quick note on how to upgrade SCOM 2012 SP1 to the R2 version. The easiest way to perform an “in place upgrade” of all SCOM 2012 SP1 Roles.

Be sure to do some preparation on backupping the machines and databases!

This example had SCOM running on the top of Windows 2008 R2 SP1 and SQL 2008 R2 SP2 and  has SCOM 2012 SP1 with CU4 installed.

– First reboot the machine to be sure that there is no issue.
– Download the SCOM 2012 R2 ISO file and mount it to the machine.

Next we download the prerequisites for the upgrade:
Microsoft System CLR types for SQL Server 2012 available on http://www.microsoft.com/en-us/download/details.aspx?id=35580 choose the ENU\x64\SQLSysClrTypes.msi option
Upgrade
Next, Next finish the setup.

Next we are going to install the Microsoft Report Viewer 2012 Runtime
– Go to  http://www.microsoft.com/en-us/download/details.aspx?id=35747 and download and run the setup
ICROSOFT REPORT VIEWER 2012 RUNTIME
Next, Next finish the setup

Lets upgrade

Ensure that your current Operating system is fully updated.
Let’s start with the in place upgrade. Insert the System Center Operations Manager R2 Media.
Note that all roles are combined on one machine.

– Check the Download the latest updates to the setup program and click install
ScreenHunter_43 May. 14 14.28
So as we can see, the wizard found the installed roles and will check the prerequisites for that upgrade.
ScreenHunter_44 May. 14 14.30
– Hit Next, select the Licence terms, choose a location (in my case D:\Program Files\Microsoft System Center 2012 R2\Operations Manager), Next

As we can see, you have the choice of Local System or domain account.
– If the database is running locally as it’s the case you can leave it at Local System.
– If the databases are on remote server it requires to use a domain account.
ScreenHunter_45 May. 14 14.44
– Select the account for the System Center Configuration and System Center Data Access service in my case domain\sa.scom and hit next

Notice that it will take a while for the upgrade to finalize, there is a progress bar for each role.During the Operational Database Configuration phase it also imports a whole set of management packs that takes some time.

After upgrade finishes, just close the setup screen.
Finished Upgrade

– You will find a warning that indicates the current version of the product is not licensed, please start the Operations Manager Shell and use the Set-SCOMLicense cmdlet to license the product.

That’s it!

 


 

17th October – Microsoft released Windows Server 2012 R2 & System Center 2012 R2

Today Microsoft released the newest release of the new R2 wave for the System Center suite.
The software is ready to download from the official Microsoft sites like Techned and MSDN.

System Center R2 Released

System Center R2 Released

The following links take you to the What’s New topics for System Center 2012 R2.

System Center 2012 R2 App Controller
System Center 2012 R2 Configuration Manager
System Center 2012 R2 Data Protection Manager
System Center 2012 R2 Operations Manager
System Center 2012 R2 Orchestrator
System Center 2012 R2 Service Manager
System Center 2012 R2 Virtual Machine Manager

Furthermore Windows 8.1 and Windows Server 2012 R2 are also released today and ready for download.

System Center 2012 R2 Release Date (SCOM, SCCM)

In 2012 Microsoft made public that they are going to release new versions of their major products at least once per year.
Because of their cloud based service they develop much faster as in the past.

Microsoft has already evaluation versions of System Center R2 available to eligible customers.
But the official release  available through the TechNet Evaluation Center. System Center 2012 R2 is available from TechNet and for new purchases on November 1st, 2013.

There’s even more good news:
Microsoft announced that Windows 8.1 will be available to consumers and businesses worldwide on October 18, 2013.

 

Step-by-step configuring the Native Exchange 2007 MP for Operations Manager

Just an old one but still good for a blog; Exchange 2007 monitoring.

-To Enable agent proxy on managed Exchange 2007 servers NOTE :Ok, as you now first roll out the OpsMgr agent to all Exchange servers and make sure they work properly before following the next steps.

  1. Click the Administration button in the Operations console, and then in the navigation pane, click Agent Managed.
  2. In the Agent Managed pane, right-click an Exchange server, click Properties, click the Security tab, and ensure that the Allow this agent to act as a proxy and discover managed objects on other computers check box is selected.
  3. Repeat the process for every managed Exchange 2007 server in the list.

  

-Create a New Management Pack for Customizations The overrides and customizations for management packs like Exchange 2007 are usually saved in the default management pack. Best practice is to create a new separate management pack for Exchange overrides.

  1. Click the Administration button in the Operations console, right-click Management Packs and then click Create Management Pack. The Create a Management Pack wizard displays.
  2. Type a name for the management pack in Name, the correct version number in Version, and a short description in Description. Click Next and then Create.
  3. Click next and create

 

– Import the Exchange 2007 management packs Next step is import the Exchange 2007 management packs

  1. In the Operations Console, click the Administration button.
  2. Right-click the Management Packs node and then click Import Management Pack(s)
  3. Click add and choose from catalog
  4. Search for Exchange and expand Microsoft Corporation, Exchange Server, Exchange Server 2007
  5. Import all Exchange 2007 Management packs
  6. After the import process is complete, and the dialog box displays an icon next to each Management Pack indicating success or failure of the importation, click the Close button.

-Enable Exchange 2007 Server Role Discovery After importing the Exchange 2007 MP, it will not start discovering Exchange machines immediately. This behavior is by design so that you can first test the management pack on a limited set of servers. To verify that Discovery Helper has discovered your Exchange 2007 servers:

  1. Ensure that you have not scoped your views.
  2. Go to the Discovered Inventory view in the Monitoring section of the Operations console.
  3. Right-click and choose Select Target Type.
  4. In the Look for field, type Exchange 2007 Discovery Helper, select it, and then click OK. A list of Exchange 2007 servers appears with a status of “Not Monitored.”

To enable Exchange 2007 Server Role Discovery

  1. Go to the Object Discoveries node located under Authoring in the Operations console.
  2. In the Look for field, type Exchange 2007 Server Role and click Enter. A list of Exchange 2007 server role discoveries appears. You need to enable the following server role discoveries to monitor the respective server role: ! Notice the Enabled by default column, most of the role discoveries are disabled Exchange 2007 CCR Clustered Mailbox Server Role Discovery  -Discovers CCR and SCC clustered Mailbox serversExchange 2007 CCR Node Role Discovery  -Discovers CCR node servers in a CCR cluster (the physical nodes)Exchange 2007 Standalone CCR Node Discovery  -Discovers stand-alone CCR node roles (nodes that are participating in log shipping but are not part of an active Mailbox server) and stand-alone mailbox rolesExchange 2007 CAS Role Discovery  -Discovers Client Access server rolesExchange 2007 Hub Transport Role Discovery  -Discovers Hub Transport server rolesExchange 2007 Edge Role Discovery  -Discovers Edge Transport server rolesExchange 2007 UM Role Discovery  -Discovers Unified Messaging (UM) roles
  3. ! Note: – To discover standalone Exchange Mailbox servers you have to enable Exchange 2007 Standalone CCR Node Discovery. – To discover active/pasive cluster Mailbox servers  you have to enable Exchange 2007 CCR Clustered Mailbox Server Role DiscoveryThe process for enabling every role is identical, for example, to enable discovery of all Hub Transport servers, right-click the Exchange 2007 Hub Transport Role Discovery and select Overrides\Enable the Object Discovery\for all objects of type Exchange 2007 Discovery Helper.
  4. In the Override Properties dialog box, set the Enabled parameter to True, choose a destination management pack and click OK

  

-Disk monitoring Because the Windows (the Server Operating System MP) is imported the disk usage is also monitort in the MP, causing duplication of disk space alerts.

To disable disk monitoring for Exchange servers from the Windows Server Operating System Management Pack

  1. In the Authoring section of the Operations console, go to the Monitors node.
  2. Click Change Scope. The Scope Management Pack Objects by target(s) dialog box appears.
  3. In the Monitors pane, in the Look for field, type Logical Disk, and then click Find Now. Select logical disk classes from all operating system versions where you are running Exchange 2007 servers (for example, Windows Server 2003 Logical Disk and Windows Server 2008 Logical Disk). Click OK.
  4. Expand Windows Server 2003 Logical Disk, expand Entity Health, and then expand Availability to see the Logical Disk Availability and Logical Disk Free Space monitors.
  5. Right-click the Logical Disk Free Space monitor, click Overrides, click Override the Monitor, and then click For a group.
  6. Select the Exchange 2007 Computer Group, and click OK.
  7. In the Override Properties dialog box, set the Enabled parameter to False, and then choose a destination management pack. ! Note Save the changes in de newly created Exchange management pack.
  8. Perform the same procedure for the enabled monitors under Performance (Average Disk Seconds Per Read, Average Disk Seconds Per Transfer, Average Disk Seconds Per Write).
  9. Repeat the same procedure for the Logical Disk Availability Monitor as well as logical disk monitors belonging to other operating system versions.

-Configuring Exchange 2007 Disk Monitoring

  1. In the Operations console, click Authoring and then click Monitors.
  2. Click the Scope button, and ensure that View all targets is selected. In the Look for field, type Disk. Select Exchange 2007 Mailbox Database Disk, Exchange 2007 Mailbox Log Disk, and Exchange 2007 Queue Disk, and then click OK.
  3. For Exchange 2007 Mailbox Database Disk, expand Availability, right-click the Exchange 2007 MDB Disk Free Space Monitor, click Overrides, click Override the Monitor, and then click For all objects of type: Exchange 2007 Mailbox Database Disk.
  4. Examine the monitor parameters. This monitor works in the same way as Windows Server operating system disk monitoring, except that it handles only Exchange 2007 disks. Note that you can set a megabyte warning or error threshold, as well as a percentage free space threshold. By applying overrides to this monitor, you can do it once for all Exchange 2007 disks with mailbox databases on them. Important This monitor raises an alert only if both the megabyte and percentage thresholds are exceeded.NOTE: Safe the changes in the newly created Exchange management pack
  5. Perform the same steps for the disk monitors for the Exchange 2007 Mailbox Log Disk and Exchange 2007 Queue Disk classes.

-Configuring IIS Monitoring The Exchange Server 2007 Management Pack contains service monitors for the WWW and IIS Admin Services on Client Access servers. If you are already monitoring IIS with the IIS Management Pack, you can disable these monitors in the Exchange Server 2007 Management Pack. To disable WWW and IIS Admin Service monitors

  1. Go to the monitors node in the Authoring section of the Operations console.
  2. Set your scope to Exchange 2007 Client Access Role.
  3. Expand Entity Health\Availability for the Exchange 2007 Client Access Role.
  4. Disable the Exchange 2007 IIS Admin Service Monitor on the Client Access server and the Exchange 2007 WWW Publishing Service Monitor for all instances of objects of type Exchange 2007 Client Access Role.

-Configure Synthetic Transactions The Exchange Server 2007 Management Pack supports local mail flow synthetic transactions on Mailbox servers, in which the server sends mail to itself.  By default, this occurs every 15 minutes; you can override the interval.

Mail flow synthetic transactions on Mailbox servers. It is possible to configure the following: -Local mail flow (a server sends mail to itself) -Intra-site mail flow (a server sends mail within a site) -Inter-site mail flow (a server sends mail between sites) -Inter-organization mail flow (a server sends mail to another organization/mailbox, which could also be used to send mail via the Internet as long as the recipient is able to generate a delivery receipt)

Client Access Server Synthetic Transactions tt is possible to configure the following: -Applies The Microsoft Exchange Server 2007 Management Pack supports a number of synthetic transactions that run on Client Access servers and perform transactions against the Client Access server itself and also the back-end Mailbox servers within the same site as the Client Access server. Examples of these transactions are to check Exchange ActiveSync, Outlook Web Access, and Web Services connectivity. The transactions are implemented using Windows PowerShell cmdlets built into the Exchange 2007 product. Documentation for the Client Access server synthetic transactions supported by the management pack can be found here: -Test-OwaConnectivity (http://go.microsoft.com/fwlink/?LinkId=137732) -Test-ActiveSyncConnectivity (http://go.microsoft.com/fwlink/?LinkId=137733) -Test-WebServicesConnectivity (http://go.microsoft.com/fwlink/?LinkId=137734) -Test-PopConnectivity (http://go.microsoft.com/fwlink/?LinkId=137735) -Test-ImapConnectivity (http://go.microsoft.com/fwlink/?LinkId=137736)

-Configure Client Access Server monitoring Configure client access monitoring

  1. click the Authoring button in the Operations Console, right click Add monitoring Wizard, Exchange 2007 Client Access Server Monitoring
  2. Give the rule a name like “Client Access Server Monitoring for source server “webmail01” and choose the custom ExchangeMP
  3. Select the source server
  4. Select the tests; we’ve checked the all
  5. Select the target servers; we’ve checked the all
  6. Do this for every CAS Server

-Exchange 2007 Intra-Organisation Mail Flow Monitoring Configure mail flow synthetic transactions

  1. click the Authoring button in the Operations Console, right click Add monitoring Wizard, Exchange 2007 Intra-Organisation Mail Flow Monitoring Give the rule a name like “Exchange 2007 Intra-Organisation Mail Flow Monitoring “ExchMB01″ and choose the custom ExchangeMP
  2. Select the source server
  3. Select the frequency
  4. Select the target servers; we’ve checked the all
  5. Do this for every Mailbox Server

 

-Configuring Exchange Servers to Support Client Access Synthetic Transactions To use the Client Access server synthetic transaction, you must first configure each agent-managed Mailbox server that you want to use as a target server for the Client Access server synthetic transactions. The Test-OwaConnectivity cmdlet requires a test mailbox.

To create the test mailbox, log on to each agent-managed Exchange Server 2007 Mailbox server with a user account that is both an Exchange administrator and an Active Directory administrator with permissions to create users.

  1. Open the Exchange Management Shell, locate the Scripts directory under the installation path for Exchange Server 2007 (usually \Program Files\Microsoft\Exchange Server\Scripts), and execute the script New-TestCasConnectivityUser.ps1.
  2. Repeat this process on each agent-managed Exchange Server 2007 Mailbox server that is to be tested. Note that if you have several organizational units named “Users” in your directory, you will need to specify the organizational unit in which to store the user.

-Possible issues Time The management pack needs time to discover and find the Exchange organization. If you are not sure configure the MP and let it rest for a while.

Exchange 2007 Test Active Sync Connectivity Alert Check from the source servers if items like Active Sync are reachable; browse to the virtual directory: https://webmail001.site.nl/Microsoft-Server-ActiveSync it can be an access issue.

 

System Center 2012 SP1 – SCOM 2012 – Evaluation (VHD)

Microsoft launched the public VHD’s for System Center 2012 SP1.
The VHD’s enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012.
The download consists of files that you extract into a single pre-configured VHD file for this System Center component.

No MSDN or TechNet subscription is required for this download.

System Center 2012 Service Pack 1 components that ship Evaluation VHDs can be found at the following locations:

System Center 2012 SP1 Released

System Center 2012 Service Pack 1 has reached its “release-to-manufacturing” (RTM) milestone, Microsoft announced recently.
ScreenHunter_162 Dec. 21 08.33

RTM typically refers to feature-complete products, although the final “general availability” release of System Center 2012 SP1 is scheduled for early January.
The “release candidate” version of the product had been issued previously, but was just available to Microsoft’s Technology Adoption Program testers. The last public release announcement seems to have been a beta delivered in September.

The software is now available on the MSDN site for partners and customers with SA.
It’s available on http://msdn.microsoft.com/en-us/subscriptions/downloads/.

A list of what’s new in SP1 for System Center 2012:
1. There are new Monitoring Capabilities under APM functionality:
                         o Monitoring of Windows Services Built on the .NET Framework.
                         o Automatic Discovery of ASP.NET MVC3 and MVC4 Applications.
                         o New Transaction Types: MVC Pages and WCF Methods.
2. Enabled APM of SharePoint 2010.
3. Integration with Team Foundation Server 2010 and Team Foundation Server 2012.
4. New monitoring capability allows for opening of APM exception events from Visual Studio IDE as if the exception was captured during the IntelliTrace historical debugging session. Developers can stay within their familiar environment to examine complete exception call stack.
5. New Management Packs and Support for Windows Server 2012 and IIS 8.
6. The System Center 2012 Service Pack 1 (SP1) Beta version of Operations Manager can show you different perspectives of application health in one place—360 .NET Application Monitoring Dashboards. The 360 .NET Application Monitoring Dashboards displays information from Global Service Monitor, .NET Application Performance Monitoring, and Web Application Availability Monitoring to provide a summary of health and key metrics for 3-tier applications in a single view.
7. ACS support is now added for Dynamic Access Control – new feature in Windows Server 2012, where business data owners to easily classify and label data allowing access policies to be defined for data classes that are critical to business.
8. Support is added for CentOS, Debian, and Ubuntu Linux.

The arrival of SP1 for System Center 2012 is a big deal because it will add management support for Windows Server 2012 and Windows 8 and SQL 2012.

Without this service pack, there’s no management support for those operating systems in System Center 2012.

Nice!

What about System Center Server licensing?

In sales and presales conversations my experience is that knowledge of the licensing suite is sometimes crucial to close the deal. Therefore this post about how the licensing suite in System Center is build.

To make things clear;
This part only counts for Server Operating Systems; not for clients (workstations)

Basically it is very simple; You can only buy the complete System Center suite, if you only use SCCM or only SCOM you still have to buy the complete suite.
Advantage is that if you license one product you get the right to use:
–  Configuration Manager
–  Service Manager
–  Virtual Machine Manager
–  Operations Manager
–  Data Protection Manager
–  Orchestrator
–  App Controller
–  Endpoint Protection
Now we’re talking !!

Licence models
System Center 2012 management licenses will be released in 2 editions differentiated by virtualization rights only:

-System Center Datacenter: Maximizes cloud capacity with unlimited Operating System Environments (OSEs) for high density private clouds.

Each Data Center license covers up to two physical processors, so you must count the number of physical processors on the server, divide that number by two, round up to the nearest whole number, and acquire and assign that number of licenses to your server.

-System Center Standard: For lightly or non-virtualized private cloud workloads. Standard Edition allows the management of up to two  “Operating System Environments” per license.

For each managed server count the number of physical processors and the number of managed OSE’s. You need the number of licenses to cover the greater number (processors or OSE’s).

Extra information:
– Both licenses includes SQL Runtime or SQL CAL
– Licensed Per processor
– Always includes Software Assurance (SA)

________________________________________________________________________

Time for a quick recap of the licensing suite:
Standard for servers with low or no virtualization
Datacenter for high density virtualisation

Underneath an example on what licence is to most suitable.

Are there separate offerings without SQL Server Technology?
No. All System Center 2012 products include the right to run a runtime version of SQL Server Technology (SQL Server Standard Edition) to support System Center so there are no longer separate offerings.

How much do the Server MLs cost?
The Microsoft Volume Licensing Open License No Level (NL) U.S. Estimated Retail Price (ERP) is
– $1,323 for System Center 2012 Standard
– $3,607 for System Center 2012 Datacenter.

For your specific pricing, contact your Microsoft reseller. Actual prices may vary. Microsoft does not determine pricing or payment terms for licenses acquired through resellers.

Why do the Server MLs cover up to two processors?
The server management licensing is simplified by standardizing on a processor-based licensing model. Each license covers up to two physical processors because the vast majority of servers contain an even number of physical processors.

Endpoint Protection?
Endpoint Protection is included in de suite. It is possible to install Endpoint protection stand-alone. For managing the Endpoint Protection software SCCM 2012 is required. For monitoring there is a management pack available. Without SCCM 2012 it is possible to manage the clients with policies but this is not an optimal situation and I do not recommend this.

Extra information:
Standalone Standard or Enterprise Server Management Licenses will be exchanged for a minimum of 1 System Center 2012 Standard Edition licenses per server or for the actual number of processors in use.
At the end of the current agreement term, you should do a self-inventory, documenting the number of processors in each server in use with System Center Server Management Suite Enterprise Edition or standalone Server Management Licenses covered with Software Assurance.
This will enable customers to receive the appropriate number of processor licenses based on System Center 2012 to continue their current deployments.
You should do this self-inventory using the Microsoft Assessment and Planning (MAP) Toolkit or other inventory tools and processes to accurately archive a time/date stamped inventory of hardware tied to System Center installations.
If you do not perform the self-inventory, they will receive two System Center 2012 licenses for each System Center Server Management Suite Enterprise Edition and one license for each standalone Server Management License.

Antivirus exclusions for Operations Manager 2012; Management, Gateway and SQL servers

SCOM 2012 Antivirus exclusions; Management, Gateway and SQL servers

For information on exclusions on the SCOM 2012 and 2007 agents click here.

This question comes up all of the time in new environments; so I decided to make a blog about exclusions to let the SCOM 2012 and the SQL 2008 R2 servers run efficiently.

Note: replace %programfiles% to the fysical location like C:\Program Files\System Center Operations…. do this for all entries below. Make also sure the path you use is correct ! !

Excluded Processes
Forefront – Excluded processes
McAfee – On Access Low risk processes
SCOM 2012
%programfiles%\System Center Operations Manager\Agent\HealthService.exe
%programfiles%\System Center Operations Manager\Agent\MonitoringHost.exe
-%programfiles%\Microsoft\Exchange Server\v14\Bin\Microsoft.Exchange.Monitoring.CorrelationEngine.exe
-%programfiles%\System Center 2012\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe

C:\Windows\system32\AdtAgent.exe
%programfiles%\System Center 2012\Operations Manager\Server\Microsoft.Mom.Sdk.ServiceHost.exe
%programfiles%\System Center 2012\Operations Manager\Server\APMDOTNETAgent\InterceptSvc.exe
-%programfiles%\System Center 2012\Operations Manager\Server\cshost.exe

SQL 2008 R2
-%ProgramFiles%\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLServr.exe
-%ProgramFiles%\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
-%ProgramFiles%\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Bin\MSMDSrv.exe

 

Excluded Directory’s
Forefront – Excluded files and locations
McAfee – Exclusions
SCOM 2012
-%programfiles%\System Center Operations Manager\Agent\Health Service State\*

SQL 2008 R2
-%ProgramFiles%\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\DATA\*
-%ProgramFiles%\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\BACKUP\*
-%ProgramFiles%\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\FTDATA\*

Excluded file types
Forefront – Excluded File Types
McAfee – Exclusions
SCOM 2012
.EDB
.CHK
.LOG

SQL 2008 R2 Server data and backup files
.mdf
.ldf
.ndf
.bak
.trn

Antivirus exclusions for Operations Manager / SCOM 2012 and 2007 Agents

SCOM 2012 and 2007 Antivirus exclusions; Agents

For information on exclusions on the SCOM 2012 management, gateway and SQL servers click here.

This question comes up all of the time in new environments; so I decided to make a blog about exclusions to let the SCOM 2012 agents run efficiently.

Note: replace %programfiles% to the fysical location like C:\Program Files\System Center Operations…. do this for all entries below. Make also sure the path you use is correct ! !

SCOM 2012 Agent Exclusions:

-SCOM 2012 Agent – Excluded Processes
Forefront – Excluded processes
McAfee – On Access Low risk processes
  -%programfiles%\System Center Operations Manager\Agent\HealthService.exe
  -%programfiles%\System Center Operations Manager\Agent\MonitoringHost.exe

-SCOM 2012 Agent – Excluded Directory’s
Forefront – Excluded files and locations
McAfee – Exclusions
  -%programfiles%\System Center Operations Manager\Agent\Health Service State\*

-SCOM 2012 Agent – Excluded file types
Forefront – Excluded File Types
McAfee – Exclusions
  .EDB
  .CHK
  .LOG
____________________________

SCOM 2007 R2 Agent Exclusions:

-SCOM 2007 R2 Agent – Excluded Processes
Forefront – Excluded processes
McAfee – On Access Low risk processes
  -%programfiles%\System Center Operations Manager 2007\HealthService.exe
  -%programfiles%\System Center Operations Manager 2007\MonitoringHost.exe

-SCOM 2007 R2 Agent – Excluded Directory’s
Forefront – Excluded files and locations
McAfee – Exclusions
  -%programfiles%\System Center Operations Manager 2007\Health Service State\*

-SCOM 2007 R2 Agent – Excluded file types
Forefront – Excluded File Types
McAfee – Exclusions
  .EDB
  .CHK
  .LOG