OpsMgr: MP Update: New Base OS MP 6.0.6958.0 ships.

Kevin Holman

18 Oct 2011 4:52 PM

Comments 37
Likes

Recently I discussed that we released a new Base OS MP 6.0.6957.0 which added many new features to the base OS MP’s. In some of these new features, we got some feedback on some issues, and we are shipping an updated version of the MP to resolve the majority of the reported issues. See my previous post describing the new features here:

http://blogs.technet.com/b/kevinholman/archive/2011/09/30/opsmgr-new-base-os-mp-6-0-6956-0-adds-cluster-shared-volume-monitoring-bpa-and-many-changes.aspx

Get the new version 6.0.6958.0 from the download center: http://www.microsoft.com/download/en/details.aspx?id=9296

What’s new?

Disabled BPA Rules by default.

The Best Practices Analyzer monitor is now shipped disabled out of the box. Since most customers have a lack of adherence to the best practices on specific server roles, and this monitor would generate a significant amount of noise in most customer environments, it has been changed to disabled by default. You can enable this if you would like to compare your server roles against the built in Server 2008 R2 BPA and receive alerts on this.

Added appropriate SQL Stored Procedures credentials

The reports we shipped in the new Microsoft.Windows.Server.Reports.mp contained two stored procedures which required manual intervention to assign permissions, previously. This has been resolved.

***Note – this MP with these new reports was designed for SQL2008 reporting environments only. It will fail to deploy on SQL 2005 SCOM infrastructures. If you are using SQL 2005 for a backend for OpsMgr databases and reporting, either upgrade to SQL 2008 or later, or do not import this MP. If you have already imported this MP, delete it. It is not supported for SQL 2005.

Updated Knowledge for Logical Disks

The knowledge for the logical disk free space monitors was updated to reflect the new default values.

Updated Overrides for Logical Disks

In the previous release (6.0.6957.0) of this MP, some of your previous overrides would not apply. This has been resolved in the current version of the MP.

Fixed %Idle time sorting in the utilization report.

Comments

Kyle

15 Nov 2011 8:51 PM

Wierd, they've never changed the alerting for "Logical Disk Free Space" before.

It now says:

The disk $Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$ on computer $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ is running out of disk space. The values that exceeded the threshold are $Data/Context/Property[@Name='PctFree']$% free space and $Data/Context/Property[@Name='MbFree']$ free Mbytes.

Instead of what its always said:

$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$ on computer $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ is running out of disk space.

Why change it? now you have to click on the little drive icon on the alert to get the amount of space and percentage left on a drive. Lame !

Does anyone know if this will be changed back to the way it was at a later point?

Cheers,
Kyle

15 Nov 2011 9:01 PM

Sorry i meant to say

It now says:

$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$ on computer $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ is running out of disk space.

Instead of what its always said:

The disk $Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$ on computer $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ is running out of disk space. The values that exceeded the threshold are $Data/Context/Property[@Name='PctFree']$% free space and $Data/Context/Property[@Name='MbFree']$ free Mbytes.

DOH!
Kevin Holman

15 Nov 2011 11:38 PM

@Kyle -

That change was a big suprise to me and I dont like the regression either. The best way to ensure this gets changed back is to open a case with Microsoft and request it as a bug or DCR (design change request). I have been planning on re-writing this workflow to get back to the old way it was handled, but it is really complicated because they changed the way the core script datasource works and it no longer outputs this information.
Gorgeous George

17 Nov 2011 8:45 PM

Opened a Premier case with M$ begging them to fix the disk space % values alert issue.

They said not now.

:)
Kevin Holman

17 Nov 2011 9:48 PM

@Gorgeous George

In that case, here is a workaround.

blogs.technet.com/.../opsmgr-logical-disk-free-space-alerts-don-t-show-percent-and-mb-free-values-in-the-alert-description.aspx
Tim

29 Dec 2011 1:56 PM

@TomaS

I also have the same situation, but I'm still on SQL 2005.

RMS/DB on win2003x64 w/ SCOM sp1 + cu1 rollup

when trying to import Microsoft.Windows.Server.Reports.mp getting Invalid Management Pack

Invalid Management Pack : C:\Program Files (x86)\System Center Management Packs\Windows Server Base OS System Center Operations Manager 2007 MP\Microsoft.Windows.Server.Reports.mp .: XSD verification failed for management pack. [Line: 1594, Position: 12]

the R2 best practice also fails to import, but it does not enter this error first. the only clue i found was perhaps there was an override or something in place causing this issue?
Kevin Holman

29 Dec 2011 3:11 PM

@Tim -

The reports MP is not supported on SQL 2005. Dont import it.

Your comment has been posted. Close

Thank you, your comment requires moderation so it may take a while to appear. Close

Kevin Holman's System Center Blog

OpsMgr: MP Update: New Base OS MP 6.0.6958.0 ships.

OpsMgr: MP Update: New Base OS MP 6.0.6958.0 ships.