SCOM 2012 : Recommended Agent OS Fixes and Updates

Find the below article on recommended Hot fixes and updated need for SCOM 2012:

http://support.microsoft.com/kb/2843219

SCOM 2012 SP1 upgrade fails with error "Failed to set DW upgrade scenario"

Reason:

This can occur if there is an invalid Data Warehouse server name or SRS database instance name in the registry on the Management Server.

Resolution:

To resolve this, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:

Data Warehouse server name Reg key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

SRS database instance name REG KEY:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance

Once its done, you can do the upgrade and should work fine

Exchange 2013 Management Pack for SCOM

Microsoft has release Microsoft Exchange Server 2013 Management Pack

You can Download it from here Click here

The following are some of the new features in the Exchange 2013 Management Pack:

• Simplified dashboard -->The dashboard of the Exchange 2013 Management Pack has been                          simplified and refined into the following three categories

Active Alert           - Provides a list of all outstanding alerts in your organization.

                    Organization Health - Provides an overview of the overall service health in your organization.

                     Server Health       - Provides an overview of the health of individual servers in your                           organization.

• User focused monitoring--> Exchange 2013 introduces a monitoring and recovery infrastructure called Managed Availability. Managed Availability focuses on the user experience. All Exchange 2013 components have built-in monitors that detect problems and attempt to recover the service availability. Any issues that can't be recovered automatically are escalated to the Exchange 2013 Management Pack as an alert.

Event Id 2115 in SCOM

Event Id 2115 in SCOM

Symptom:

Operations Manager Management Servers, agents or servers may be affected by a deadlock.


Cause:

This event id happens because of KB2775511.


Resolution:

Removal of KB2775511 will correct the issues.


Microsoft has recommended not install the KB till Deadlock issue is resolved

SCOM Managment server grayed out after removing from All Management Servers resource pool

• This occurs because the run-as data warehouse accounts are configured by default to  distribute to the All Management Servers resource pool only.  

• When the management server is removed from the All Management Servers resource pool the data warehouse account is no longer distributed to it, therefore any workflows requiring this account will fail and unload. The failing and unloading of the workflows will cause the management server to become grayed out.

• To resolve this issue, go to the “Data Warehouse Account” and “Data Warehouse Report Deployment Account” profiles and determine which account(s) you are using. Then, go to those accounts under Run As Configuration and change their deployment type to either “less secure”, to the specific management servers, or to the new resource pool that the management servers belong to.

Antivirus exclusion list for SCOM 2012 and SCOM 2007 R2

Process Exclusion:

• monitoringhost.exe (Operations Manager 2007)
• monitoringhost.exe (Operations Manager 2012)

Directories and Filetype to be Excluded:

SQL Server:

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

Change the drive letter appropriate to your environment where the Install,data and logs are.

Exclude the below file types

• MDF
• LDF

Management Servers, Gateway server and Agents:

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

Exclude the below file types

• EDB
• CHK
• LOG

Also exclude the Pagefiles from real-time scanning.

How to get Rule Name from Instance ID.

Lot of times in SCOM you will get the Instance ID and Workflow name of the rule that is causing the error.

This is of no use in troubleshooting as you dont knwo the Rule that is causing the issue.

Follow the below steps to decode the Rule Name from WorkFlow Name

• From the Error Copy the "WorkFlow Name"
• Now connect to the "OperationsManager" database and run the below SQL query

               SELECT * FROM Rules WHERE RuleName = ‘MomUIGeneratedRulexxxxx’

 Replace "MomUIGeneratedRulexxxxx" with the data you got from WorkFlow Name

• The query will retun lot of column's, you need to check the "RuleID field" coloum and copy the information

• Now login to you SCOM RMS and open Command Shell and thpe the below command

                                  Get-Rule -Id XXXX-XXX-XXXX

Replace "XXXX-XXX-XXXX" with the info that you got from the "RuleID field" coloum of the SQL query

• This command will return information about this rule, Copy the DisplayName and find the rule in the Operations Console and troubleshoot it.