I guess you already know that page on the Technet where a list of microsoft Management pack is done : Direct link to Technet site.
In March 2013 Stefan Stranger has published a command line to scrape some of the information about Management Packs using PowerShell. Using the line bellow will list provide you the list of management pack and the download link to get it !
Based on this command line, Stanislav Zhelyazkov wrote a script to download all MPs from the link and create folders by MP name, and subfolders by version
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 !
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.
DELL Printer Management Pack for System Center Operations Manager and System Center Essentials
The Dell Printer Management Pack v5.0 for Microsoft System Center 2012 SP1 Operations Manager, Microsoft System Center 2012 Operations Manager, Microsoft System Center Operations Manager 2007 R2 and System Center Essentials 2010 integrates Dell Printers monitoring into Operations Manager. The Management Packs provide a list of Dell-specific views that you can use to observe and drill down the system status in a network.
This file format consists of an archive of files that may be decompressed to a directory on the hard drive. The installation can then be done from that directory.
This posting is provided "AS IS" with no warranties.
Today, I've had a request to retrieve all informations for a rule that was generating too much alerts. The rule was give, by it's name and the name was not really user friendly : _08C092E8_FD6F_48b2_BA1E_473C3B84A2F3_.RaiseAlert
Thanks to the Exchange Server 2010 Management pack developper team :)
So I've create a short powershell function to add to my powershell profile :
Daniele Muscetta bring the SCOM community on June the 23th a really interesting file that contains an “AllEvents” list – and then the same events are broken down by event source.
After installing the SQL Management Pack version 6.3.173.1 in System Center Operations Manager 2007 R2, you will see default columns selected in the monitoring views for the new SQL 2012 components.
However, if you upgrade to this Management Pack from an earlier version without removing the old one first, the columns will remain unchanged from your previous view settings.
This is by design, although you can go to Personalize View under Actions and check the desired columns to display.
More information
This behavior may also occur with other Management Packs.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties
Article ID: 2809231 - Last Review: January 28, 2013 - Revision: 1.1
Applies to
Microsoft System Center Operations Manager 2007 R2
Keywords:
KB2809231
This posting is provided "AS IS" with no warranties.
The Active Directory Domain Services Management Pack for System Center provides both proactive and reactive monitoring of your Active Directory deployment.
The Active Directory Domain Services Management Pack for System Center provides both proactive and reactive monitoring of your Active Directory deployment. It monitors events that various Active Directory components and subsystems place in the Application, System, and Service event logs. It also monitors the overall health of the Active Directory system and provides alerts for critical performance issues.
The monitoring that this management pack provides includes monitoring of domain controllers and monitoring of health from the perspective of clients that use Active Directory resources. To monitor domain controllers, ADMP provides a predefined, ready-to-run set of processing rules, monitoring scripts, and reports that are designed specifically to monitor the performance and availability of domain controllers.
Because client computers in your Active Directory environment can experience connectivity and service issues even when domain controllers appear to be operating correctly, ADMP includes the Active Directory Client Management Pack, which can help you identify such issues. The Active Directory Client Management Pack monitors the services that domain controllers provide. It provides information—in addition to the information that is collected directly on the domain controllers—about whether domain controllers are available by running transactions, such as Lightweight Directory Access Protocol (LDAP) binds and pings, against the directory service.
The December 2012 revision of the Active Directory Domain Services Management Pack for System Center includes the following changes:
Product knowledge improvements
Excessive alert fixes
Script error fixes
Rule error fixes
For more details about these fixes, see the included management pack guide.
Feature Summary
Replication
Lightweight Directory Access Protocol (LDAP)
Domain Controller Locator (DCLocator)
Trusts
Net Logon service
File Replication Service (FRS)
Intersite Messaging service
Windows Time service
Key Distribution Center (KDC)
Service availability monitoring
Key performance data collection
Comprehensive reports, including reports about service availability and service health, plus reports that you can use for capacity planning
Release History
1/9/2013 - Updated release, version 6.0.8070.0, with fixes to bugs reported by customers.
3/30/2012 - Updated release, version 6.0.7822.0, with fixes to bugs reported by customers.
10/6/2011 - Updated release, version 6.0.7670.0, with fixes to bugs reported by customers and architectural issues to facilitate future Operations Manager's releases
11/3/2009 - Updated release, version 6.0.7065.0, with added Windows Server 2008 R2 support
11/7/2008 - Initial release for 2000/2003/2008, version 6.0.6452.0
03/26/2008 - QFE, version 6.0.6278.10
03/17/2008 - QFE, version 6.0.6278.3
1/15/2008 - Updated Guide - same version
3/23/2007 - Initial Release, version 6.0.5000.0
System requirements
Supported operating systems: Windows Server 2003, Windows Server 2003 R2 (32-Bit x86), Windows Server 2003 R2 x64 editions, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
Other Supported Systems:
Virtual environment
Clustered servers
Writeable domain controllers
Read-only domain controller (RODC)
Domain member computers (Client and Server)
Note: Agentless monitoring and stand-alone or workgroup member computers are not supported.
Important: Migration from Microsoft Operations Manager (MOM) 2005 to Systems Center Operations Manager 2007 is not supported, but a side-by-side installation of these two products is supported. All support is subject to the Microsoft overall Help and Support life cycle and the Operations Manager 2007 R2 Supported Configurations document.
The Microsoft Dynamics NAV 2013 Management Pack for System Center allows you to discover and monitor computers that are running Microsoft Dynamics NAV 2013 components and services.
This management pack enables Operations and IT Management teams to more easily identify and resolve issues affecting the health of numerous distributed Microsoft Dynamics NAV 2013 installations. It lowers client support costs by surfacing critical statistics and alerts in context of running Microsoft Dynamics NAV 2013 components. It also reduces IT management complexity by automating routine administration and providing basic actions for working with Microsoft Dynamics NAV 2013 components.
This extension package provides users of Microsoft System Center Operations Manager with the ability to detect and monitor computer systems running Microsoft Dynamics NAV 2013, including the following components:
Computers on which Microsoft Dynamics NAV Server is installed and Microsoft Dynamics NAV Server Instances are installed.
Computers on which Microsoft Dynamics NAV Web Server components are installed. These include the websites for the Microsoft Dynamics NAV Web client.
Note: In order to obtain proper monitoring information from the Microsoft Dynamics NAV 2013 Server Instances, apply Platform Hotfix for Microsoft Dynamics NAV 2013 described in KB 2784398 (build 7.0.34040 and above).
Management Pack Release History:
09 Jan 2013 - Initial release, version 7.0.0.0 targeted System Center 2007R2 Operations Manager and Windows Server Internet Information Services 7
09 Jan 2013 - Initial release, version 7.0.1.0 targeted System Center 2012 Operations Manager and Windows Server Internet Information Services 7 and Windows Server 2012 Internet Information Service 8
System requirements
Supported operating systems: Windows 7 Enterprise, Windows 7 Professional, Windows 7 Professional 64-bit, Windows 8 Pro, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
Windows 8 Professional or Enterprise (32-bit or 64-bit editions)
Windows 7 Professional, Enterprise, or Ultimate (32-bit or 64-bit editions)
Windows Server 2008 R2 SP1 (32-bit or 64-bit editions)
Windows Server 2008 Service Pack 2 (32-bit or 64-bit editions)
Windows Server 2012
Other software:
Microsoft Dynamics NAV 2013 (with KB 2784398 applied)
System Center 2007R2 Operations Manager
System Center 2012 Operations Manager
This posting is provided "AS IS" with no warranties.
This security update resolves two privately reported vulnerabilities in Microsoft System Center Operations Manager. The vulnerabilities could allow elevation of privilege if a user visits an affected website by way of a specially crafted URL. An attacker would have no way to force users to visit such a website. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the affected website.
This security update is rated Important for all supported editions of Microsoft System Center Operations Manager 2007. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that Microsoft System Center Operations Manager accepts input. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
Known Issues. None
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.
Affected Software
Software
Maximum Security Impact
Aggregate Severity Rating
Updates Replaced
Microsoft System Center Operations Manager 2007 Service Pack 1[1]
Cumulative Update 7 for System Center Operations Manager 2007 R2 has been released by Microsoft !
Cumulative Update 7 contains a number of fixes for Operations Manager 2007 R2, as well as all of the fixes from Operations Manager 2007 R2 CU6. A number of fixes may require manual steps to install.
Tao Yang have updated the script provided by Steve Rachui ( Place a Group in Maintenance Mode with PowerShell ) to use SDK rather than SCOM 2007 PS Snap-in so the script works on both SCOM 2007 and OM12.
He's also made few other changes including change the duration from number of hours to number of minutes to suit his needs.
You can read his full article on Tao's blog and download his modified script here.
This posting is provided "AS IS" with no warranties.
The Team Foundation Server 2012 Monitoring Management Pack provides both proactive and reactive monitoring of Microsoft Team Foundation Server 2012. It monitors TFS components such as application tier server instances, team project collections, build servers, and proxy servers.
The Team Foundation Server 2012 Monitoring Management Pack provides both proactive and reactive monitoring of Microsoft Team Foundation Server 2012. It monitors TFS components such as application tier server instances, team project collections, build servers, and proxy servers.
Feature Summary The monitoring provided by this management pack includes availability and configuration monitoring, performance data collection, and default thresholds. You can integrate the monitoring of Team Foundation Server components into your service-oriented monitoring scenarios.
Auto discovery of TFS components
Implements containment hierarchy, reflecting logical architecture of the Product
Implements a proper health model using Monitors
Contains tasks, diagnostic and recovery for certain failures
Provides events that indicate service outages
Provides alerts that show configuration issues and connected data source changes
Verification that all dependent services are running
Release History
11/19/2012 - Original English release, version 1.0.0.0
System requirements
Supported operating systems: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012
Other Software:
Team Foundation Server 2012
System Center Operations Manager 2007 or System Center Operations Manager 2012
Instructions
Please see the included MP guide for complete installtion instructions.
This posting is provided "AS IS" with no warranties.
This Knowledge Base article talks about an issue where you are unable to access the Operations Manager 2007 Web Console and Event 33857 is recorded in the Operations Manager event log:
Consider the following scenario:
- You are unable to access the Operations Manager 2007 Web Console - Event 33857 is recorded in the Operations Manager event log:
Log Name: operations managerSource: Health Service ModulesDate: <date>Event ID: 33857Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: webconsoleserver.contoso.comDescription:Failed to retrieve the state of the following site: 'Operations Manager 2007 WebConsole'. The operation will be retried. HRESULT: 0x800710d8 Details: The object identifier does not represent a valid object. One or more workflows were affected by this. Workflow name: Microsoft.Windows.InternetInformationServices.2008.WebSite.WebSiteStatusCheck.Monitor Instance name: Operations Manager 2007 WebConsole Instance ID: {CEE899C4-4FD5-AD3B-AE4F-307F2871E1E0} Management group: group Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
Cause
This can occur if the services for the Web Server role have been modified or reinstalled once the Operations Manager Web Console has been installed. If one of the components below is modified the Web Console may stop functioning:
• HTTP Redirection • ASP.NET and additional roles • ASP • Basic Authentication (if using Forms Based auth and SSL) • Windows Authentication (if using Windows account authorization) • IIS 6 Management Compatibility and/or sub-roles
Resolution
To resolve this issue, remove the Operations Manager Web Console from the Server and reinstall any component required for the Web Server role for the Operations Manager Web Console. Once the Web Server prerequisites have been installed, you can reinstall the Operations Manager Web Console.
This posting is provided "AS IS" with no warranties.
The Dell Client Management Pack v5.0 for Microsoft System Center 2012 Operations Manager, System Center Operations Manager 2007 R2, and System Center Essentials 2010 integrates monitoring of Dell Business Client Computers into Operations Manager.
The Management Packs provide a list of Dell-specific views that you can use to observe and drill down the system status in a network. The version 5.0 release consists of: Management Pack: 1) (Dell.WindowsClient.mp) - Dell Client Management Pack for discovery and monitoring Dell Business Client Computers. Utility Management Pack: 1) (Dell.Connections.HardwareLibrary.mp) - Dell Base folder utility for the basic folder structure and Root node. Install Guide: 1) DellMPv5.0_Client_IG.pdf :- contains installation and upgrade instructions for user to get started on using the Dell Client Management Pack effectively. Readme: 1) DellMPv5.0_Client_Readme.txt - Readme contains more details on Management of Dell Business Client Computers
Release Date:
10/26/2012
Importance:
Optional
Version:
Vendor Version : 5.0
Dell Version : A00
The following formats are available for the file you have selected
File Format: Hard-Drive File Name: Dell_Client_Management_Pack_v5.0_A00.exe Description: This file format consists of an archive of files that may be decompressed to a directory on the hard drive. The installation can then be done from that directory. Download Type: HTTP File Size: 574KB
This posting is provided "AS IS" with no warranties.
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
Download the MSI.
Double click the MSI to install.
View the Management Pack Guide for importing and configuration instructions.
This posting is provided "AS IS" with no warranties.
This Monitoring Pack enables operators and administrators to manage Microsoft SharePoint 2013 Products including SharePoint Server, Project Server, and Search Server.
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
Download the MSI.
Double click the MSI to install.
View the Management Pack Guide for importing and configuration instructions.
This posting is provided "AS IS" with no warranties.
Here is a new Microsoft article. Javascripts used by System Center Operations Manager 2007 Management Packs for monitoring fail to execute on a specific agent and the following error is generated:
CScript Error: Can't find script engine "JScript" for script "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 8\1596\DiscoverHealthServiceCommunicationRelationships.js".
MattGoedtel(MSFT)haspublished a very interesting articledetailing how toinclude atextboxin your custom reports by using the Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.Textbox control.
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.
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.