[OpsMgr 2007 R2 SP1][OpsMgr 2012] System Center Management Pack for Windows Server Operating System - What's new in version 6.0.7026.0

The April 2013 update (version 6.0.7026.0) of the Windows Server Operating System Management Pack contains the following changes:

• Fixed a bug in Microsoft.Windows.Server.2008.Monitoring.mp where the performance information for Processor was not getting collected.
• Made monitoring of Cluster Shared Volume consistent with monitoring of Logical Disks by adding performance collection rules. (“Cluster Shared Volume - Free space / MB”,”Cluster Shared Volume - Total size / MB”,”Cluster Shared Volume - Free space / %”,”Cluster Disk - Total size / MB”,”Cluster Disk - Free space / MB”,”Cluster Disk - Free space / %”)
• Fixed bug in Microsoft.Windows.Server.ClusterSharedVolumeMonitoring.mp where the Cluster disks running on Windows Server 2008 (non R2) were not discovered.
• Fixed bug 'Cluster Disk Free Space Percent' and Cluster Disk Free Space MB' monitors generate alerts with bad descriptions when the volume label of a cluster disk is empty.
• Added feature to raise event when NTLM requests time out and customers are unable to use mailboxes, outlook stops responding, due to the low default value for Max Concurrent API registry Key (HLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters) , which is a ceiling for the maximum NTLM or Kerberos PAC password validations a server can take care of at a time. It uses the “Netlogon” performance counter to check for the issue.

Read more on Kevin Holman article  >>>>> HERE <<<<<

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Boris Yanushpolsky 's Tools by Daniele Muscetta - New update

Here is the latest update from Daniele :

•  May 9th 2013 with MPViewer 2.3 that now can also handle MP Bundles that contain multiple ManagementPacks in a single bundle.

Many thanks to him to always improve the tools !

Get latest updates directly on : http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2 SP1][OpsMgr 2012] System Center Management Pack for Windows Server Operating System - upgrade to version 6.0.7026.0

The System Center Management Pack for Windows Server Operating System provides the fundamental monitoring basics for computers running the Windows 2000 Server and Windows Server 2003, 2003 R2, 2008, 2008 R2 and 2012 Operating System.

Direct link to Microsoft site

File name:	Date Published:
OM_MP_WindowsOS.docx	5/6/2013
Version:	File size:
6.0.7026.0	146 KB

• The System Center Management Pack for Windows Server Operating System consists of the following management packs: Microsoft Windows Server Library, Microsoft Windows Server 2012 Discovery, Microsoft Windows Server 2012 Monitoring, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2008 R2 Monitoring BPA, Microsoft Windows Server Clustered Shared and Volume Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The System Center Monitoring Pack for Windows Server Operating System monitor the performance, health, and availability of Windows Server 2012, Windows Server 2008, 2008 R2, 2003and Windows 2000 Server. 

By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.

Feature Summary

• Availability
• Key Operating System Services: Required services are checked for status (for example, running, not running, or paused)
• Storage: Logical hard drives are checked for availability, sufficient free space, and integrity of the NTFS partition.
• Network: Network adapters are checked for connection health, name and IP address conflicts.
• Performance
• Processor: System processor(s) performance is checked system-wide. Processors can optionally be monitored on a per processor basis.
• Memory: Memory consisting of physical memory and virtual memory (also known as page files) is monitored using the following performance indicators:
• Available memory (in MB)
• Pages per second
• Page file percent usage
• Disks and Partitions: Logical disks/partitions and physical disks are monitored, and performance data is collected for average disk seconds per read, disk seconds per write, and disk seconds per transfer. Monitoring is also provided for fragmentation of logical disks. Depending on which version of the operating system is being monitored, either logical or physical monitoring is enabled by default. Refer to the MP guide for more detail.
• Network Adapter: Network adapters are monitored for the number of bytes received per second, the number of bytes sent per second, and the total bytes per second. In addition, the health state of the network adapter is evaluated and is set to Healthy if connected and Critical if disconnected.

The System Center Monitoring Pack for Windows Server Operating System consists of the following five management packs: Microsoft Windows Server Library, Microsoft Windows Server 2012 Discovery, Microsoft Windows Server 2012 Monitoring, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2008 R2 Monitoring BPA, Microsoft Windows Server Clustered Shared and Volume Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The Microsoft Windows Server management packs monitor the performance, health, and availability of Windows Server 2012, Windows Server 2008, 2008 R2, 2003 and Windows 2000 Server.

By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.

• Availability
• Key Operating System Services: Required services are checked for status (for example, running, not running, or paused)
• Storage: Logical hard drives are checked for availability, sufficient free space, and integrity of the NTFS partition.
• Network: Network adapters are checked for connection health, name and IP address conflicts.
• Performance
• Processor: System processor(s) performance is checked system-wide. Processors can optionally be monitored on a per processor basis.
• Memory: Memory consisting of physical memory and virtual memory (also known as page files) is monitored using the following performance indicators:
• Available memory (in MB)
• Pages per second
• Page file percent usage
• Disks and Partitions: Logical disks/partitions and physical disks are monitored, and performance data is collected for average disk seconds per read, disk seconds per write, and disk seconds per transfer. Monitoring is also provided for fragmentation of logical disks. Depending on which version of the operating system is being monitored, either logical or physical monitoring is enabled by default. Refer to the MP guide for more detail.
• Network Adapter: Network adapters are monitored for the number of bytes received per second, the number of bytes sent per second, and the total bytes per second. In addition, the health state of the network adapter is evaluated and is set to Healthy if connected and Critical if disconnected.
• Known Issue: If the BPA monitor is enabled, then there will be an error in the PowerShell script which is a know issue in the Agent. This has been fixed in Operations Manager next update which is coming up. 
• 
  

Release History:

• 5/6/2013 - Update release, version 6.0.7026.0
• 9/25/2012 - Update release, version 6.0.6989.0
• 6/6/2012 - Update release, version 6.0.6972.0
• 10/18/2011- Update release, version 6.0.6958.0
• 9/30/2011 - Update release, version 6.0.6957.0
• 3/19/2010 - Updated release, version 6.0.6794.0, to resolve an issue with discoveries failing to query the Win32_PowerPlan WMI class.
• 9/18/2009 - Updated release, version 6.0.6667.0, introduced support for the Windows Server 2008 R2 Operating System and made a series of updates. Refer to the MP guide for further details.
• 10/20/2008 – Updated release, version 6.0.6321.35. Refer to the MP guide for further details. 
• 7/27/2008 - Updated version, 6.0.6278.22: Introduced support for the Windows Server 2008 Operating System and addressed some issues from the previous release. Refer to the MP guide for further details.
• 5/27/2008 – Same version as released on SP1 media, version 6.0.6278.0, and released on Microsoft Download Center.
• 2/22/2008 - Updated release, version 6.0.6278.0, and released on SP1 media
• 1/15/2008 - Updated MP Guide - same version
• 11/8/2007 - Updated MP Guide - Software version still 6.0.5000.25
• 10/23/2007 - Updated MP Guide - Software Version still 6.0.5000.25
• 9/28/2007 - Updated release, version 6.0.5000.25
• 3/23/2007 - Initial Release, version 6.0.5000.0 

• Supported Operating System

  Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
  

  Other Requirements: All management packs (MPs) included in this download are supported on System Center Operations Manager 2007 (SP1, R2).
  
  The following should be considered when importing the management packs into a management group which does not have OpsMgr SP1 installed:
  
  • The Library, Windows 2000 Server and Windows Server 2003 specific management packs can be imported into a management group that does not have OpsMgr 2007 SP1.
  • The Windows Server 2008 specific management packs are not supported, and will not import, into a management that does not have OpsMgr 2007 Service Pack 1 installed. This is due to the fact that monitoring of Windows Server 2008 is not supported without Service Pack 1.
  The Windows Server Operating System Management Pack for Operations Manager 2007 is designed to monitor the following versions of the base Operating System:
  
  
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2003 R2
  • Microsoft Windows 2000 Server
  
  NOTE:
  
  • You need to install the English MP before you import localized language packs.
  • Note that the localized language packs are not updated with this release, and will not import on Operations Manager 2012. The language packs will be updated in an upcoming release.
  • The Microsoft.Windows.Server.Reports Management Pack will only import on systems that use SQL Server 2008 as the Database and is not currently supported on SQL Server 2005.
  
  All support is subject to Microsoft’s overall support lifecycle (http://go.microsoft.com/fwlink/?Linkid=26134) and the Operations Manager 2007 SP1 Supported Configurations (http://go.microsoft.com/fwlink/?Linkid=90676) document. 

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012 SP1] System Center Management Pack for Windows Azure Fabric - Preview

The Preview Management Pack for Windows Azure Fabric enables you to monitor the availability and performance of Azure fabric resources that are running on Windows Azure.

Direct link to Microsoft site

Quick details

Version:	1.0.0.0	Date published:	4/11/2013
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
MPGuide_AzureMP2.doc	347 KB	Download
System Center 2012 Management Pack for    Windows Azure.msi	828 KB	Download

Overview

The Management Pack for Windows Azure Fabric enables you to monitor the availability and performance of Azure fabric resources that are running on Windows Azure. The management pack runs on a specified proxy agent and then uses various Windows Azure APIs to remotely discover and collect instrumentation information about a specified Windows Azure resource, such as a Cloud Service, Storage or Virtual Machine. The Management Pack for Windows Azure Fabric provides no functionality on import. For each Windows Azure subscription that contains Azure resources you want to monitor, you must configure discovery and monitoring by first using the Windows Azure wizard in the administration section of the OM Console, then the Windows Azure Monitoring template in the authoring section of the OM Console.

                               

System requirements

Supported operating systems: Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2

You must have an Operations Manager 2012 SP1 or later environment, this Management Pack will not import on Operations Manager 2007 R2 or Operations Manager 2012 RTM

                               

Instructions

See the Management Pack Guide for detailed instructions on working with this management pack.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] VSAE – Include File Content

David Allen, has posted on April 3, 2013, an article to show how to include your own vbs, ps1 or JS script in your authored management pack.

Full article is here

The include syntax in this example is $IncludeFileContent/Scripts/MonitoringScript.vbs$, and this is generated based on the path of the file.  In this MP, I stored the VBS file in a folder called Scripts, which is why “Scripts/MonitoringScript.vbs” is added to “IncludeFileContent”.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Powershell script to list all references stored in all unsealed Management Pack

I'm actually doing some clean up in our 2007 R2 environment to be sure that all management pack are OK before importing them in our new SCOM 2012  environment.

As you know, best practices is to create one override MP by MP you want to tune. One of the tasks we wanted to do is to ensure that all overrides stored in unsealed MPs are corresponding to the sealed assocaited MP.

Listing all references of unsealed MPs is a good help to identify what unsealed MP has a reference on a MP (and also override) that should not be referenced !

Download the file :

<<<<<<<<<< Here >>>>>>>>>>

Or create a file : ListReferenceUnsealedMPs.ps1

1. param([string]$Path)
2. $Exportfile = [string]$Path + "\ListAllReferencesForNonSealedMPs.csv"
3. $Exportfile
4. # SCOM 2007R2
5. $mps = get-managementpack | where-object {$_.Sealed -eq $false}
6. # SCOM 2012
7. # $mps = Get-SCOMManagementPack | where-object {$_.Sealed -eq $false}
8. "Management Pack Name;Reference Name;Reference Key Token;Reference Version;Reference ID;Reference Version ID" >> $Exportfile
9. Foreach ($mp in $mps)
10.  {
11.  $References = $mp.References
12.  foreach ($Ref in $References)
13.   {
14.   $mp.Name + ";" + $Ref.name + ";" + $Ref.KeyToken + ";" + $Ref.Version  + ";" + $Ref.Id + ";" + $Ref.VersionId >> $Exportfile
15.   }
16.  }

 Then you can use the ListReferenceUnsealedMPs.ps1 "C:\temp" command line in a powershell connected to your SCOM (don't forget to comment line 5 + un-comment line 7 for using in 2012).

This will create a c:\Temp\ListAllReferencesForNonSealedMPs.csv that contains all References by unsealed MP.

Openning the .csv file with excel will give you :

 Enjoy !

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] System Center Monitoring Pack for System Center 2012 - Orchestrator

The monitoring pack fmonitors the health and availability of Microsoft System Center 2012 - Orchestrator.

Direct link to Microsoft Article

Quick details

Version:	7.0	Date published:	4/1/2012
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
OpsMgr_MP_Orch2012.docx	82 KB	Download
SC2012OrchestratorMP.EXE	322 KB	Download

Overview

The Microsoft System Center Monitoring Pack for System Center 2012 - Orchestrator monitors the health and availability of Microsoft System Center 2012 - Orchestrator.

Feature Summary
The Microsoft System Center Monitoring Pack for System Center 2012 - Orchestrator provides the following capabilities.

• Orchestrator Management Server Health - This scenario checks Orchestrator Management Servers for service status and critical log file events.
• (monitor) Orchestrator Management Service
• (monitor) Orchestrator Runbook Server Monitor
• (alerting rule) Orchestrator Management Server Database Connection Error
• (alerting rule) Orchestrator Runbook Server Monitor Database Connection Error
• Orchestrator Runbook Server Health - This scenario checks Orchestrator Runbook Servers for service status and critical log file events
• (monitor) Orchestrator Runbook Service
• (monitor) Orchestrator Remoting Service
• (alerting rule) Orchestrator Runbook Policy Module Fault Alert
• (alerting rule) Orchestrator Runbook Server Database Connection Error
• (alerting rule) Orchestrator Runbook Update Error
• (alerting rule) Orchestrator Runbook Server ActionServerStorage Call Refused Error
• (non-alerting rule) Orchestrator Runbook Policy Module Working Set Peak Collection
• (non-alerting rule) Orchestrator Runbook Policy Module Thread Count Collection
• (non-alerting rule) Orchestrator Runbook Policy Module % Processor Time Collection
• Orchestrator Web Components Health - This scenario implements health roll-up for monitored IIS 7 components that represent the Orchestrator Web Components
• (dependency monitor) Web Components Availability Rollup

Please refer to the Monitoring Pack Guide included in the downlaod for more details

Release History

• 4/2/2012 - Original English Release, version 7.0

System requirements

Supported operating systems: Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2

The Monitoring Pack for System Center 2012 - Orchestrator has the following prerequisites:

• The Monitoring Pack for System Center 2012 - Orchestrator supports both System Center 2012 - Operations Manager as well as System Center Operations Manager 2007 R2 or later. A dedicated management group is not required.
• The Windows Server 2008 Internet Information Services 7 Management Pack (version 6.0.6658 or later) must be imported to the management group prior to importing the Monitoring Pack for System Center 2012 - Orchestrator.
• Windows PowerShell is required on Orchestrator Management Servers and Runbook Servers

Instructions

Once you have reviewed the Monitoring Pack Guide and meet the prerequisites for the Monitoring Pack for System Center 2012 - Orchestrator you can import this management pack module using the Microsoft Operations Manager administrative console and following these steps. The MP file “Microsoft.SystemCenter.Orchestrator.Library.mp” should be imported first.

1. Open the Microsoft Operations Manager Operator console
2. Click on the Administrator pane at the bottom left corner
3. Expand the Management Packs node in the tree view
4. Click on the Import Management Pack on the “Actions” pane on the right and then browse to the folder where you extracted the MP and then import it.
5. Follow the instructions until you have finished importing the management pack module.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] System Center 2012 Monitoring Pack for RemoteAccess 2012

Microsoft System Center Monitoring Pack for Remote Access helps you monitor the health and availability of computers configured for Remote Access server role and running Windows Server 2012.

 Direct Link to Microsoft Article

Quick details

Version:	7.0.8560.0	Date published:	1/25/2013
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
Microsoft Windows Server 2012 Remote Access MP for OM 2012.msi	568 KB	Download
OM2012_MgtPack_RAS Guide.doc	432 KB	Download

Overview

​Microsoft System Center Monitoring Pack for Remote Access helps you monitor the health and availability of computers configured for Remote Access server role and running Windows Server 2012.

System Center Monitoring Pack for Remote Access combines monitoring for DirectAccess and RRAS into a single management pack. Monitoring capabilities for DirectAccess have been enhanced to cover more components and encompass larger set of health scenarios. This management pack monitors the following conditions:

1. DirectAccess Monitoring
• Issues with internal and external network adapter connection and settings such as forwarding
• State of transition technologies such as teredo, 6to4 etc
• State of underlying services
• Heuristics around network security such as DOS attack, spoof attack etc
2. VPN Monitoring
• Connection failures
• Erroneous configuration
• Other erroneous conditions such as hardware device error, IP-Sec related failures etc
• Support for monitoring performance counters and instrumentation
All existing support for VPN Server monitoring has been ported to this combined pack.

Release History

• 1/25/2013 - Original English release, version 7.0.8560.0

System requirements

Supported operating systems: Windows Server 2012

• Other Software - System Center 2012 - Operations Manager

Instructions

Please refer to MP Guide

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012 SP1] System Center Global Service Monitor Management Packs

These management packs enable the System Center Global Service Monitor functionality within System Center Operations Manager 2012 SP1

Direct link to Microsoft site

Quick details

Version:	1.0.1800.0	Date published:	1/14/2013
Language:	English

File name	Size
System Global Service Monitor.msi	1.5 MB	Download

Overview

This management pack enables the System Center Global Service Monitor functionality within System Center Operations Manager 2012 SP1.

To use System Center Global Service Monitor you need a valid account, sign up using this link : Global Service Monitor Trial

Management packs are dependent on the Alert Attachment MP (Microsoft.SystemCenter.AlertAttachment.mpb) which exists on the installation media for System Center Operations Manager 2012 SP1

Release History

• 01/15/2013 - Original English release, version ​1.0.1800.0

System requirements

Supported operating systems: Windows Server 2008 R2, Windows Server 2012

• Other Software: System Center Operations Manager 2012 SP1
• Valid account to use System Center Global Service Monitor

Instructions

Download MSI and extract Management Packs. Import Management Packs into System Center Operations Manager 2012 SP1. (Management packs are dependent on the Alert Attachment MP which exists on the installation media for System Center Operations Manager 2012 SP1)

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2] System Center Monitoring Pack for Duet Enterprise 2.0

The System Center Monitoring Pack for Duet Enterprise 2.0 can be used to monitor important events and errors that can occur on SharePoint servers on which Duet Enterprise 2.0 Server components have been installed.

Direct link to Microsoft Article

Quick details

Version:	2.0	Date published:	1/16/2013
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
Duet Enterprise 2.0 Management Pack.msi	512 KB	Download
System Center Monitoring Pack guide for Duet Enterprise 2.0.docx	87 KB	Download

Overview

The System Center Monitoring Pack for Duet Enterprise 2.0 can be used to monitor important events and errors that can occur on SharePoint servers on which Duet Enterprise 2.0 Server components have been installed. The specific components of Duet Enterprise 2.0 that can be monitored are as follows:

• Duet Enterprise Workflow component
• Duet Enterprise Role Synchronization timer job

In addition to alerting on important error scenarios, this management pack helps indicate possible remedial actions to take based on the error state reported by the monitors.

Feature Summary
The System Center Monitoring Pack for Duet Enterprise 2.0 provides monitoring for the following core components:

• Duet Enterprise Workflow component
• Duet Enterprise Role Synchronization timer job

Release History

• 6/17/2011 - Release of Management Pack for Duet Enterprise 1.0
• 1/16/2013 - Release of Management Pack for Duet Enterprise 2.0

System requirements

Supported operating systems: Windows Server 2008, Windows Server 2008 R2

• Other Software: System Center Operations Manager 2007 R2

Instructions

Import the management pack found in the 'Program Files' folder once you run the MSI. Refer to the management pack guide included in this download for detailed instructions on this mangement pack.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] System Center Security Monitoring Pack for Endpoint Protection

This monitoring pack provides real time monitoring capabilities of security incidents detected by Endpoint Protection clients.

 Direct link to Microsoft site

Quick details

Version:	2.1.1116.0111	Date published:	1/8/2013
Change language:	English

File name	Size
fep2010 security mp.msi	681 KB	Download

Overview

The System Center Security Monitoring Pack for Endpoint Protection provides real-time monitoring of your Endpoint Protection clients by using System Center Operations Manager. Alerts can be configured for virus activity, firewall downtime, or update failures. In addition to real-time event monitoring, the Endpoint Protection Security Management Pack also provides automated response capabilities to remediate security related issues.

Feature Summary

• Monitor Endpoint Protection Client health
• Monitor Definition State
• Monitor Malware State
• Alert on active Malware
• Alert on Pending Actions
• Alert on Definitions out of date
• Alert on RTP Off
• Alert on Re-Infection
• Alert on Malware Outbreak

Release History

• 10/26/2012 – Update Release, version 2.1.1116.0111. Supports an updated version of the client, which allows the client software for Forefront Endpoint Protection (FEP) 2010 and System Center 2012 Endpoint Protection to install on and support a computer that runs Windows 8 or Windows Server 2012.
• 4/2/2012 - Update Release, version 2.1.1116.107. Adds support for System Center 2012 Operations Manager and System Center 2012 Endpoint protection. Supported languages are: English, Chinese Simplified, Chinese Traditional, French, German, Italian, Japanese, Korean, Portuguese(Brazil), Russian, and Spanish
• 12/15/2010 - Original English Release, version 2.0.0267.1
• 1/8/2013 - Update release, version 2.1.1116.0111, available in English, Simplified Chinese, Traditional Chinese, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish

System requirements

Supported operating systems: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012

• Other Software:
• System Center Operations Manager 2007 R2
• System Center 2012 Operations Manager
• Forefront Endpoint Protection 2010
• System Center 2012 Endpoint Protection

Instructions

Important:
You must have Windows PowerShell 2.0 installed on all computers that you intend to manage with this updated monitoring pack. If you do not have this version of Windows PowerShell installed, the Stop Scan task will not work. Windows PowerShell 2.0 is installed by default with Windows 7 and later operating systems. Additionally, the Windows PowerShell Script Execution Policy must be set to RemoteSigned for the Stop Scan task to run correctly.

For more information, see the MP guide.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2] Windows Server Print Server Management Pack for System Center Operations Manager 2007 R2

This management pack monitors the performance and availability of the Print Server role running on various Windows Server operating systems.

Microsoft Article

Version:	6.0.7004.0	Date published:	12/8/2012
Change language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
OM2007_MP_PrintSvr.doc	382 KB	Download
System Center Management Pack for Windows Print Server.msi	760 KB	Download

Overview

The Microsoft Windows Server Print Server Management Pack monitors the performance and availability of print servers running on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012. In addition to monitoring the health of print servers, the management pack can also provide insight into the status of shared printers. By detecting, alerting on, and automatically responding to critical events and performance indicators, this management pack helps indicate, correct, and prevent possible operating system service outages.

Feature Summary
The management pack provides functionality to:

• Monitor performance and Windows events
• Display detailed monitoring data through views
• Allow operator to manage print servers
• Ensure correct configurations

Release History

• 6/1/2007 - Original release of the English version, version 6.0.5000.0
• 3/18/2008 - Updated release, version 6.0.5000.36
• 8/25/2008 - Updated release to add support for Windows Server 2008, version 6.0.6392.0
• 12/07/2012 - Updated release to add support for Windows Server 2008 R2 and Windows Server 2012, version 6.0.7004.0

System requirements

Supported operating systems: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012

• Other Software: System Center Operations Manager 2007 R2

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] System Center Monitoring Pack for Sharepoint Foundation 2013

This Monitoring Pack enables operators and administrators to manage Microsoft SharePoint Foundation 2013.

Microsoft Article



Quick details

Version:	15.0.4425.1000	Date published:	11/8/2012

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
Microsoft.Sharepoint.Foundation. ManagementPacks.msi	940 KB	Download
System Center Monitoring Pack guide for Microsoft SharePoint Foundation 2013.docx	196 KB	Download



Overview

The System Center Monitoring Pack for Sharepoint Foundation 2013 is designed to be used for monitoring SharePoint Foundation 2013 events, collecting SharePoint component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically correlating critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage SharePoint servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, and health monitoring.

Feature Summary

• Health monitoring of SharePoint Foundation 2013
• Monitors Events and Services and alerts when service outages are detected
• Monitors Performance and warns users when SharePoint performance is at risk
• Forwards users to up-to-date TechNet knowledge articles

Release History

• 11/8/2012 - Original English release, version 15.0.4425.1000

System requirements

Supported operating systems: Windows Server 2008 R2

• Other: Software:System Center Operations Manager 2007 R2 or later

Instructions

1. Download the MSI.
2. Double click the MSI to install.
3. View the Management Pack Guide for importing and configuration instructions.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] System Center Monitoring Pack for Sharepoint Server 2013

This Monitoring Pack enables operators and administrators to manage Microsoft SharePoint 2013 Products including SharePoint Server, Project Server, and Search Server.

Microsoft Article

Quick details

Version:	15.0.4425.1000	Date published:	11/8/2012
Change language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
Microsoft.Sharepoint.Server.ManagementPacks.msi	1.2 MB	Download
System Center Monitoring Pack guide for Microsoft SharePoint Server 2013.docx	119 KB	Download

Overview

This Management Pack enables operators and administrators to manage Microsoft SharePoint 2013 Products including SharePoint Server, Project Server, and Search Server.

Feature Summary
The Microsoft SharePoint Server 2013 Management Pack is designed to be used for monitoring SharePoint 2013 Products events, collecting SharePoint component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically correlating critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage SharePoint servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, and health monitoring.

• Health monitoring of SharePoint Server 2013
• Monitors Events and Services and alerts when service outages are detected
• Monitors Performance and warns users when SharePoint performance is at risk
• Forwards users to up-to-date TechNet knowledge articles

Release History

• 11/8/2012 - Original English release, version 15.0.4425.1000



System requirements

Supported operating systems: Windows Server 2008 R2

• Other Software: System Center Operations Manager 2007 R2 or later

Instructions

1. Download the MSI.
2. Double click the MSI to install.
3. View the Management Pack Guide for importing and configuration instructions.



This posting is provided "AS IS" with no warranties.

[Orchestrator 2012][OpsMgr 2012] Orchestrator dashboard in Operations Manager 2012

Anders Bengtsson (MSFT) has published an article related to an Orchestrator dashboard in System Center Operations Manager 2012.

He provides a management pack that collects some information in the Orchestrator DB :

• Queue

1. Pending Jobs, show number of runbooks with pending status, meaning they are waiting to start
2. Top minutes in queue, show number of minutes top 1 job have been in the queue.

• Runbook Results

1. Success, show number of runbooks that have ended with success result
2. Warning, show number of runbooks that have ended with success result
3. Failed, show number of runbooks that have ended with success result

• Runbook Jobs. This widget show number of times each runbook have run with success result. You can easy see which runbook that most often executed. The names you see is the name of the runbook.
• Orchestrator Server Status, show status of my Orchestrator roles. In this sandbox all roles are on the same server, SCO01.
• Orchestrator Alerts show alerts generated by my Orchestrator machine.

You can download his example MP here, NOT SUPPORTED – Contoso.Orchestrator – v2 . Note that this is provided “AS-IS” with no warranties at all. This is not a production ready management pack or solution for your production environment, just a idea and an example.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Microsoft Office Web Apps Server Management Pack Guide for System Center Operations Manager

Microsoft Office Web Apps Server Management Pack Guide for System Center Operations Manager guide has been released. It contains a Quick Start section to help you set up the environment, import management packs, and configure the system for monitoring by using SCOM. It also contains monitors and rules for Office Web Apps Server and links that will connect you to information about common tasks that are associated with System Center management packs.

Download it in pdf or docx format from here

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Managing SCOM Alerts with powershell scripts

I've recently read an article here that show us how to close unclosed alerts comming from rules in a left SCOM environment and this give me the opportunity to post some scripts to help you to manage alerts in Operations Manager.

First, the article make the difference between alerts comming from monitors (I'll say autoclose alerts) and alerts comming from ruleS (Manual close alert) but forgot to speak about manual reset monitors that generate alerts.

So to close all alerts that are raised by rules :

#Resolve alerts that are created by a rule
#Note the Get-Alert become Get-SCOMAlert with OpsMgr 2012get-alert -criteria ‘ResolutionState != ”255”’ | where-object {($_.IsMonitorAlert -eq $False)}| resolve-alert -comment "Resolving all opened alerts generated by all rules."

What about closing alerts generated by manual reset monitors.

• first, here is a script to retrieve all manual reset monitors

# Search all Manual Reset Monitor$mg = (Get-ManagementGroupConnection).ManagementGroup
$monitorType = $mg.GetUnitMonitorTypes("Microsoft.Windows.SingleEventLogManualReset2StateMonitorType")[0];
$monitorCriteria = new-object Microsoft.EnterpriseManagement.Configuration.MonitorCriteria("IsUnitMonitor='1'");
$monitorTypeCriteria = new-object Microsoft.EnterpriseManagement.Configuration.UnitMonitorTypeCriteria("Name LIKE '%EventLogManualReset%'");
$monitorTypes = $mg.GetUnitMonitorTypes($monitorTypeCriteria);
$monitors = $mg.GetMonitors($monitorCriteria);
$manualResetMonitors =  @()
foreach($monitor in $monitors){
    foreach($monitorType in $monitorTypes){
        if(([Microsoft.EnterpriseManagement.Configuration.UnitMonitor]$monitor).TypeId.Id -eq $monitorType.Id){
   $manualResetMonitors += $monitor
        }
    }
}
# list all manual reset monitors
$manualResetMonitors

•  You're now able to get all information for manual reset monitors and create a script to get alerts for each monitor in $ManualresetMonitors

Script should ne like (not tested yet)

$manualResetMonitors | % {
 #Close all alerts of the specific monitor get-alert | where-object {$_.ResolutionState -eq "0" -and $_.MonitoringObjectId -eq '"'+ $_.Id +'"'} |resolve-alert -comment "Resolving all alerts for all manual reset monitors."
 }


I would like to add an other script that could be usefull when you remove a MP. Save the following script in CloseAlertsForMP.ps1 and call it in a powershell windows connected to the management group in which you want to close the alerts with MP name as argument.

Param ([String] $MPName)
If ($MPName -eq "") { $MPName=(Read-Host "Enter a Management Pack Name ") }
   $mp=Get-ManagementPack | where {$_.name -eq $MPName
   }
If ($mp -eq $null) {
   "The ManagementPack you have put in argument is incorrect or not found"
   "List of available MP"
   Get-ManagementPack | sort -property Name | ft Name
   Exit
   }
$mp.getclasses() | foreach {$criteria="ResolutionState != 255";$alerts+=get-alert -criteria $criteria}$alerts | ft name,customfield1,ResolutionState, Customfield7
$continue =(Read-Host "Do you want to continue ? (y/n)")
if ($continue -ne "y") {
   "No alerts closed"
   "Exit"
   Exit
   }
$alerts | resolve-alert -comment "Closing Alert before Management Pack retirement"

 Hope these fiew line will help you to manage alerts in your environment.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Microsoft Service Bus Management Pack for System Center Operations Manager

This Management pack supports monitoring of the Service Bus Farms.

Direct Link to Microsoft article

Quick details

Version:	1.0.0.0	Date published:	10/19/2012
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
MicrosoftServiceBusMPGuide.doc	506 KB	Download
ServiceBusMP.msi	620 KB	Download

Overview

The Microsoft Service Bus Management Pack for System Center Operations Manager supports monitoring of the Service Bus Farms.

Feature Summary
The Microsoft Service Bus Management Pack for System Center Operations Manager supports monitoring the following core areas and scenarios:

• Farms
• Hosts
• Farm Management and Gateway DB
• Front End, Back End and Gateway Roles

Release History

• 10/19/2012 - Original release, version 1.0.0.0

System requirements

Supported operating systems: Windows Server 2008 R2 SP1, Windows Server 2012

• This Management depends on the following Management Packs: SQL Server 2012 MP 6.3.173.0 or later

Instructions

Refer to the management pack guide included in this download for detailed instructions on working with this management pack. For the latest MP Guide, please download the .doc file below.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Microsoft Workflow Manager Management Pack for System Center Operations Manager

This Management pack supports monitoring of Workflow Farms.

Direct link to Microsoft Article

Quick details

Version:	1.0.0.0	Date published:	10/19/2012
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
MicrosoftWorkflowManagerMPGuide.doc	669 KB	Download
WorkflowManagerMP.msi	592 KB	Download

Overview

The Microsoft Workflow Manager Management Pack for System Center Operations Manager supports monitoring of the Workflow Farms.

Feature Summary
The Microsoft Workflow Manager Management Pack for System Center Operations Manager provider Availability and Performance monitoring for:

• Farms
• Nodes
• Front-End Roles
• Back-End Roles

Release History

• 10/19/2012 - Original release, version 1.0.0.0

System requirements

Supported operating systems: Windows Server 2008 R2 SP1, Windows Server 2012

• This Management depends on the following Management Packs: SQL Server 2012 MP 6.3.173.0 or later and Microsoft Service Bus MP 1.0.0.0 or later

Instructions

Refer to the management pack guide included in this download for detailed instructions on working with this management pack. For the latest MP Guide, please download the .doc file below.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Management Pack samples - Authoring

Brian Wren published in summer 2012 MP samples that have been on OpsManJam for some time.

Direct link to Brian's article

• Sample Management Pack - Business Hours

Sample management pack for Operations Manager 2007 and System Center 2012 Operations Manager.

This management pack provides an example of configuring monitors and rules to run only during business hours.  Examples are provided for a service monitor, a monitor running a script, and monitors and rules based on a Windows event.  Two different monitor types are used for events.  These have identical functionality but illustrate two different strategies for configuring monitor types.
Each monitor and rule must specify parameters for the System.ScheduleFilter module.  StartTime and EndTime provide the time that the monitor or rule should begin functioning, while EndTime specifies the time that it should stop functioning.  DaysOfWeekMask specifies the days of the week that the schedule applies to as described in the following article: http://msdn.microsoft.com/en-us/library/ee692976(v=MSDN.10).aspx.
Both event monitors trigger a critical state from an event with a number of 101 and a source of EventCreate.  They return to healthy with an event number of 102.  The service monitor watches the running state of the Alerter service,  The script monitor will set a state according to the Successful parameter on the monitor type.  If the Successful parameter is false, then a critical state is set.  If the Succesful parameter is true, then a healthy state is set.
All rules and monitors are targeted at a class called MPAuthor.BusinessHours.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\BusinessHours. This registry key must be on the same agent computer where the test events are created.

• Sample Management Pack - Network Devices

 This is a sample management pack for Operations Manager 2007 R2.
This management pack provides an example of monitoring network devices.  This includes providing custom monitoring for different brands of SNMP devices and monitoring Syslog mesages from devices that do not support SNMP.
A class is created for each type of SNMP device based on Microsoft.SystemCenter.NetworkDevice.  This provides a target for monitors and rules specific to each type.  For devices that do not support SNMP, a class is created based on System.HardwareComponent.  A device for each type of device is created based on this class that provides the target for monitors and rules specific to that type.

Discovery for SNMP devices is targeted at Microsoft.SystemCenter.NetworkDevice since this represents network devices that have already been discovered.  The name of the target is used to determine the type of device and which class should be created.  Discovery for devices not supporting SNMP is performed from a text log that lists the Name, IP Address, and Type for each device to discover.  This discovery is targeted at a proxy agent that is discovered from a registry key at HKLM\SOFTWARE\MPAuthor\NetworkDevices.  This registry key must also contain a value called ConfigFIle that contains a path to the configuration file.

The classes for the devices are all unhosted.  Unhosted object are typically managed on the RMS, but the discovery scripts create a special containment relationship that causes the object to be managed on the proxy agent.  Any monitors or rules targeted at these classes are loaded on the agent computer.  The managed devices should be configured to send SNMP traps and Syslog messages to the proxy agent.

• Sample Management Pack - Working with a Property Bag

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a script returning multiple values in a property bag.  A single monitor type is used that accepts a parameter to specify the desired property. Also illustrated is the use of data source modules returning different data types.  Rules and monitors can use the data source returning the type they require, while they all share the same script.

The script collects different pieces of data from a file.  The name of the file must be specified in the FileName parameter of any rule or monitor.

All rules and monitors are targeted at a class called MPAuthor.PropertyBag.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\PropertyBag. This registry key must be on the same agent computer with the file.

• Sample Management Pack - Diagnostics and Recoveries

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a recovery running after a diagnostic.  The recovery only runs if specific criteria is received from the diagnostic output.  It also illustrates how to pass property bag data from the monitor to the diagnostic and the recovery.

In this example, the diagnostic runs in response to a service monitor.  If the specified service is stopped, then the diagnostic runs.  The service used is the WMI Performance Adapter (WmiApSrv), but this can be changed in the properties of the monitor.  The diagnostic runs a script that collects an error code value from the registry at HKLM\SOFTWARE\MPAuthor\DiagnosticAndRecovery\ErrorCode.  If the error code is 3, then the recovery will run.  If it is any other value, the recovery will not run.  The recovery is a script that restarts the service.

A sample diagnostic and recovery are provided for both VBScript and PowerShell.  The functionality of each are identical and only one of the diagnostics should be enabled at a time.

• Sample Management Pack - Process Data Source

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager. 
This management pack provides an example of a script processing the output of a data source.  The data source is followed by a probe action that changes the output data type to a property bag. Monitors and rules using the data type specify the property bag values that they require.  Two samples are provided, one using Windows PowerShell and the other using VBScript.
The specific example expects XML in the description of an event.  This simulates a condition where all errors in the application create a Windows event with the same name number and source. The XML includes the specific number and description of the error.  The expected XML format is below.  Sample rules expect an event with a number of 101 and a source of EventCreate.  The EventCreate utility can be used to create sample events.
All rules and monitors are targeted at a class called MPAuthor.ProcessDataSource.PowerShell.Target or MPAuthor.ProcessDataSource.VBScript.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\ProcessDataSource. This registry key must be on the same agent computer that the sample event is created on.

• Sample Management Pack - Registry Monitor

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a monitor based on a registry value.  A monitor type is included that will periodically check a specified registry value and compare it to a desired value.  The monitor provides the path to the value, the duration to check, and the value to compare it to.
The included monitor checks the value at HKLM\SOFTWARE\MPAuthor\RegistryMonitor\TestValue and sets the monitor to a critical state if the value is not "ThisValue".  A different registry value and desired value can be used by changing the configuration of the monitor.
All rules and monitors are targeted at a class called MPAuthor.RegistryMonitor.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\RegisterMonitor. This registry key must be on the same agent with the registry value being checked.

• Sample Management Pack - Linked Reports

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of linked reports.  Two linked reports are included as follows:
Availability Report - The user is not required to provide values for any of the parameters other than the objects.  The data included is from the previous seven days.  The dialog box to select the objects is filtered to only include instances of MPAuthor.LinkedReports.Target.
Performance Report - The user must select the object and date range but does not need to select the details of the report.  It is configured to include performance data from two rules - MPAuthor.LinkedReports.CollectScriptPerformance and MPAuthor.LinkedReports.CollectWMIPerformance.
All rules and monitors are targeted at a class called MPAuthor.LinkedReports.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\LinkedReports. This registry key must be on at least one agent computer.  The sample rules and monitor will run on these agents.

• Sample Management Pack - Cookdown

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of workflows running scripts that support cookdown.  Two example rules are provided in both VBScript and PowerShell with with one supporting cookdown and the other not supporting cookdown.
The sample rules collect as performance data the file size for all files in a specified folder.  The rules are targeted at the class MPAuthor.Cookdown.File, so the agent will run a separate instance of the rule for every file.  The data source module for the rule not supporting cookdown requires the path of the file as a parameter.  Since this will be different for every instance, the module cannot cookdown.  The first data source module for the rule supporting cookdown also requires the file path, but this is used in a condition detection module.  The data source module running the script does not require this parameter.  Since the folder path parameter will be the same for all files, that data source module does cookdown.
Each rule will create an event in the Operations Manager event log to verify each running instance.  The rules that cookdown should create a single event while the rules not supporting cookdown should create multiple events.  Each of the rules is disabled and needs to be enabled before they run.
The event numbers created are as follows:
821 - No Cookdown - VBScript
822 - Cookdown - VBScript
823 - No Cookdown - PowerShell
824 - Cookdown - PowerShell
The discovery for MPAuthor.Cookdown.File is targeted at a class called MPAuthor.Cookdown.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\Cookdown. This key must have a value named FolderPath that contains the path of the folder containing the files.  The folder must exist on the agent computer and contain one or more files to discover.

• Sample Management Pack - Discovery

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager. 
This management pack provides several examples of different kinds of discovery. Several classes and relationships are included in the management pack to support the sample discoveries.   A basic description is provided for each below, and a more complete description is provided for each Discovery in the management pack.

- Registry Discovery
Creates an instance of a particular class if certain conditions are true.
- Script Discovery
Script to discover instances of a particular class. 
- Script Discovery for Unhosted Class
Script to discover instances of an unhosted class.
- WMI Discovery
WMI discovery to discover instances of a particular class. 
- Discover Containment Relationship with Script
Script to discover instances of a containment relationship.  A script is used because logic is required to parse the a property collected from a registry value.
- Discover Containment Relationship with Registry
Discover a containment relationship from registry values without using a script.  This discovery can only be used when the property value collected from the registry does not need to be parsed.
- Group Population for a Group
Uses GroupPopulator to populate a group with all instances of a particular class.
- Group Population for Distributed Application
Uses GroupPopulator to populate a distributed application with all instances of a particular class.
- Group Population for Computer Group
Uses GroupPopulator to populate the a group  with all instances of Microsoft.Windows.Computer that have an instance of another class.dfg

This posting is provided "AS IS" with no warranties.