First published on CLOUDBLOGS on Sep 30, 2011
[Today’s announcement comes from
Brian Huneycutt
]
The Sustained Engineering team has released an update to the “Microsoft System Center Configuration Manager 2007 SP2 Management Pack for Microsoft System Center Operations Manager 2007 R2”.
Due to changes in naming convention, this update is now referred to as the “System Center Monitoring Pack for Configuration Manager 2007 SP2 (Converted)”. You can download the new release
here
.
This is a very limited scope release intended to address top customer issues reported after shipping the last Management Pack (MP). As you can see from the name this is still a converted MP although the Monitoring Pack for Configuration Manager 2012 will be native.
The following changes, also covered in the updated MP guide, are in version 6.0.6000.3.
-
Consolidation Event Rules have been disabled to prevent the generation of false alerts.
-
Operating system architecture detection logic was updated to determine 64-bit operating systems.
-
You no longer have to run the SQL Server query to clean up the localizedtext tables as part of the post-installation cleanup
-
Scripts that target site database servers now retrieve time values directly from servers running instances of SQL Server instead of site servers to avoid time-zone discrepancies.
-
Site hierarchy discovery now succeeds even if a site or component server does not have a fully qualified domain name (FQDN) configured.
-
The AlertLevel property can now be overridden, giving you control over the severity level.
-
All monitors and rules are now public.
-
The "ConfigMgr 2007 Collection Evaluations Tasks" script has been updated to let you monitor a collection that has a NULL StartTime value.The "ConfigMgr 2007 Collection Evaluations Tasks" script now uses CollectionID instead of Collection Name to track collection tasks.
The prior version of the MP will upgrade directly to the new release.
If you are running an alternate MP, such as one that was unsealed, modified, and then sealed again the upgrade steps will include the following:
-
Export and delete any MP that references the alternate ConfigMgr 2007 MP.
-
Delete the alternate MP.
-
Import the official MP.
-
Open any MP you exported in Step 1 using a text or XML editor and change the public key token in the ConfigMgr 2007 MP reference to match the Microsoft SN key.
-
Re-import referencing MP(s).
--
Brian Huneycutt
This posting is provided "AS IS" with no warranties, and confers no rights.
