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


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 (37)

  1. Anonymous says:

    @Value over 100 % –

    This can happen from discrepancies in perfmon at the time the data is collected, or a flaw in the math used in the script which collects the data.

    The bandwidth is collected from WMI in the script by looking at:

                   nCurrentBandwidth = GetWMIProperty(oInterface, "CurrentBandwidth", wbemCimtypeUint64, ErrAction_None)

                   nBytesSentPersec = GetWMIProperty(oInterface, "BytesSentPersec", wbemCimtypeUint64, ErrAction_None)

                   nBytesReceivedPersec = GetWMIProperty(oInterface, "BytesReceivedPersec", wbemCimtypeUint64, ErrAction_None)

                   nBytesTotalPersec = GetWMIProperty(oInterface, "BytesTotalPersec", wbemCimtypeUint64, ErrAction_None)

    The counter output is methematically generated by using the below formula:

                       Counters.Add CN_PercentBandwidthUsedRead, CalculatePercent(nBytesReceivedPersec,nCurrentBandwidth/8)                    

                       Counters.Add CN_PercentBandwidthUsedWrite, CalculatePercent(nBytesSentPersec, nCurrentBandwidth/8)

                       Counters.Add CN_PercentBandwidthUsedTotal, CalculatePercent(nBytesTotalPersec,nCurrentBandwidth/8)

    It is very possible there is some logic flaw in using this calculation.  I used a slightly different method in my calculation – but also heard some customers report it was above 100% in some cases.  I'd imagine that the formula needs some tweaking to be 100% perfect, given that this is a script and is performing a mathematical caluclation at runtime.

    Were your NIC's hammered at that time?  

    I have also seen issues in virtualized environments and on server 2003 where "Current Bandwidth" is reported incorrectly, and this will skew the results.

  2. Anonymous says:

    @Donald – I discussed this in a previous comment:

    You are correct – the free disk space alert description was changed.  There are no immediate plans to change this that I know about.  HOWEVER – if this impacts any customer's business process, the BEST way to have any MP changed, is to call PSS, open a case, and ask them to file a DCR or RFH on your .  That's it.  DCR = design change request and RFH = request for hotfix.  This has the most impact, because it is YOUR business case that effects change.  So, if you want to see this workflow design change, or ANY change to a MP, and can communicate the business impact, the next step is yours.  🙂  

  3. Anonymous says:

    @Damati –

    Two points:

    1.  Collecting performance data for disks with no drive label.  Actually – this is not correct.  We dont care if a disk has a label or not.  The issue is collecting perf for disks with no drive LETTER.  This never worked, in any version of the base OS MP – and no changes were made in this area.  The problem there is that the collection rule passes the "Device ID" variable (normally drive letter) to match on the perfmon instance.  However, for disks with no letter – we discover a different value in the device ID than the perfmon instance.  To address this, we need to add a new property to the logical disk class for perfmon instance and discover this correctly, OR, we need to change the logical disk discovery so that Device ID value matches perfmon instances.  \?Volume{ddff0c64-48ee-11df-8fe0-806e6f6e6963} == HarddiskVolume4.

    2.  You are correct – the free disk space alert description was changed.  There are no immediate plans to change this that I know about.  HOWEVER – if this impacts any customer's business process, the BEST way to have any MP changed, is to call PSS, open a case, and ask them to file a DCR or RFH on your .  That's it.  DCR = design change request and RFH = request for hotfix.  This has the most impact, because it is YOUR business case that effects change.  So, if you want to see this workflow design change, or ANY change to a MP, and can communicate the business impact, the next step is yours.  🙂

  4. Anonymous says:

    @Aengus –

    What is the specific error you are getting?  There should be a more specific error returned.  

    I recommend enabling remote errors on you reporting server so the report output will show you the full details of the error:  technet.microsoft.com/…/aa337165.aspx   (without remote errors enabled – you might only see the top two lines in the error above)

  5. Anonymous says:

    @Felyjos –

    There is nothing the MP to cause HB failures.  That sounds like you have a serious performance issue with your environment and the config update storm caused by the MP update kept your RMS so busy, that the healthservice was not able to keep up with HB.  I'd take a serious look at your configuration on the RMS and DB's from an IO perspective.

    No – you should not place all agents into maintenance mode when doing a MP import.

  6. Anonymous says:

    @Donald –

    Absolutely!  You can pick and choose which MP's you want.  Just dont import the reports MP.  If you dont want the (disabled) BPA monitor – dont import that MP!  If you dont have Cluster Shared volumes on Hyper-V, dont import that MP!

  7. Anonymous says:

    @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.  

  8. Anonymous says:

    Performance Utilization report

    1) PerfDS error when executing the report

    The report Performance Utilization does not correspond with the stored procedure it calls

    I opened the report with Visual Studio and in the definition of the report the dataset PerfDS calls the stored procedure

    dbo.[Microsoft_SystemCenter_Report_Performace_By_Utilization]; in the parameters defined for this the call to the stored procedure has as first parameter @DataAggregation: the stored procedure from the MP does not have this parameter. I adapted the report to remove the parameter in the PerfDS dataset, deployed it and then it works.

    2) At my company I have a datawarehouse which is used by two managementgroups; it would like to take the parameter @ManagementGroupId in consideration for the dataset Groups in the report

    3) The Groups DataSet gives all defined groups; it should only give groups where the members are of type Computer, e.g. in the list of group Active Directory, AD Domain Controller Group (Windows 2003 Server), … are present; when selecting these the report does not return data because I presume the members of the group are not of type Windows Computer

    It is a nice report but it could be beter at certainly the management pack should make sure the reports call the stored procedures with the correct parameters

    Roland

  9. Anonymous says:

    Jim – this was fixed in 6.0.6958.0.  It was reversed in 6.0.6957.0.  Are you sure you are on the latest version?  We re-released it very quickly and included several fixes.

  10. Anonymous says:

    Hi Kevin

    We are using SQL 2005 Standard version for OpsMgr and OpsMgr DW. Can we import other MP's except Reporting mp? or all MP's depends on SQL version?

  11. Anonymous says:

    Hi Kevin

    In the new version of the mp the Logical Disk Free Space monitor alert not showing the % or value free space left. Is there any bug is opened to fix this issue?

  12. Anonymous says:

    @Mike – mike – please see my previous response on the other article.

  13. Anonymous says:

    @roland_fortis –

    1.  Removing the dataset from the report is not the right approach.  The report will potentially redeploy and break it again unless you copied it to a new location.  The correct approach is to modify the stored proc in SQL to add in the missing item:   "@DataAggregation INT,"   I am not sure why this didnt deploy correctly in your specific environment, but I assure you it is environmental.  At least one other customer has reported this same behavior, but it is very rare.  Interesting.

    2.  You will need to re-write the report for that, or open a DCR.

    3.  You are correct – this report could be optimized from that perspective.

  14. Anonymous says:

    It is the Exchange environment which is occupying the first 6 position then one configuration manager server.

    I picked one exchnage mailbox server and running perfmon now…

    Bytes Received/sec ==> floating 40/60 …

    Bytes Sent/sec ==> Flat at 100

    Bytes Total/sec ==> Flat at 100

    Current Bandwidth ==> Flat at 100

    so I think it might still be real unfortunately.

    All are physical servers DL360 or PoewerEdge 1950

    I am checking with the Network team … as it seems to be the same subnet as well (:

    Thanks,

    Dom

  15. Anonymous says:

    @Tim –

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

  16. Anonymous says:

    Thanks a lot Kevin

    I will check the IO issues

  17. Anonymous says:

    Hello Kevin,

    Thanks for all these details which make easy to install this MP.

    Several facts I noticed:

    – During the installation of the MP I lost the heartbeat on all clients … "Heartbeat Failure" alert in SCOM with paging for mots of them…. (: any special thing i did not notice on this MP… is it heavier than previous ones which did not created these alerts…

    The SVCMOMACtion is logged in the Security Event log at the same time as both alerts: 8:09 am closed 8:41 am and then a second alert 8:49 closing by 9:22 am…

    Should I place all server in Maintenance Mode when applying the new MPs now?

    – DPM is giving me a hard time with these reports…

    Long Drive Name are not well displayed on the reports Performance By Utilization and Performance by System. If the Drive Name is over 3 Chareacters it becomes unreadable…

    As I have several issues within Individual Report for the various graphs where 10 servers listed are all red I need to expand these reports individually:

    e.g.: Logocal Disk: Average Percent Space Used

    How to get an individual report and work on more thna 10 occurences only for this report… (10 is fine for most graphs)

    Thanks,

    Dom

  18. Aengus says:

    Thanks for advising on availability, alas reports still not working for me.

    SQL 2008 reporting and DB and I elevated the reporting account to SA to confirm not permissions and I get;

    Query execution failed for dataset `PerformanceData' for the Performance by System report, and

    Query execution failed for dataset `PerfDS' for the Performance by Utilization report

    Am I missing something, is there additional reports config required?

    Thanks.

  19. John Bradshaw says:

    Thx Kevin. Appreciate your effort here.

    The new reports do not seem to be working.

    When running a Performance by System report…Just placing 1 server in as the name and running it from Yesterday, the report comes back empty with Number of Servers as 0. Nothing related in the Event Logs.

    Maybe I need to leave the new MP for a day to get data??

    Thx,

    John Bradshaw

  20. Aengus says:

    Thanks Kevin,

    I should have remembered to set that 🙂

    Looks like our issue is collation. The Db's are CP1 but the server default is Latin1_general and the create scripts in the reports don't specify collation.

    I knew the Db's needed to be CP1 but this is the first time we have encountered an issue where I am asking if the server default needs to be CP1 and a bit of research indicates it may need to be; technet.microsoft.com/…/bb309428.aspx

    I'll check out options to change with our Dba and take from there.

    Thanks for above and your great blog!

    Aengus

  21. Bob Cornelissen says:

    @John I found that if you select a whole week that it does show data. When selecting the from Yesterday option I didn't get data at first either.

    @Kevin, until now loving the new version of this MP!

  22. John Bradshaw says:

    Thx Bob…Yep even 1 day reports working fine now. Getting a good reception from users too!!

    JB

  23. mike says:

    Anynews on systems with more that 40 CPU's?

  24. Damati says:

    Still the updated Management Pack does not show Logical disk values in the alert description (Free MB and %) like the old one. the moment we updated the OS MP we started to receive calls from operations team complaining about this.

    another thing we noticed. we are monitoring some logical disks that have no label. previously we were able to get the performance counters for it. now with the new management pack it is not collecting any performance counter on those disks.

    Will Microsoft update this Management pack or we need to import the oldest one ?

    regards,

  25. Felyjos says:

    Hello Kevin,

    How to get an individual report to work on more than 10 occurences only for this report… (10 is fine for most graphs)…?

    Are they existing report already?

    Thanks,

    Dom

  26. stellar19 says:

    Just wondering if anyone else has seen an abnormal amount of Security login failures EventID 4625 for the SDK account post  installing this MP?  My domain admin notified me its hammering our DCs with upwards of 50000 failures a day.  

    An account failed to log on.

    Subject:

    Security ID: DOMAINDSISRVC_Q_SCOMSDK

    Account Name: DSISRVC_Q_SCOMSDK

    Account Domain: MTOLYMPUS

    Logon ID: 0x2e129

    Logon Type: 3

    Account For Which Logon Failed:

    Security ID: NULL SID

    Account Name:

    Account Domain:

    Failure Information:

    Failure Reason: An Error occured during Logon.

    Status: 0xc00002fd

    Sub Status: 0x0

    Process Information:

    Caller Process ID: 0xd3c

    Caller Process Name: C:Program FilesSystem Center Operations Manager 2007Microsoft.Mom.Sdk.ServiceHost.exe

  27. Value over 100 % says:

    Hello Kevin,

    I noticed on Network Adapter: Average Percent Bandwith Used I have value 109%, 105%, 102% what does this mean!!! How could it be over 100%!!!!

    Thanks,

    Dom

  28. Maekee says:

    After updating to this MP Version i started getting ALOT for these:

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "C:" with id:"{ACFAEF0C-2EE1-A392-1542-C7086D239AF6}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "J:" with id:"{D66C40BE-8BD4-7672-6280-B8B609859D7F}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "G:" with id:"{CFC2CCA9-B2ED-869A-B71F-EB77882AB37A}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "H:" with id:"{66316FE7-98BA-54A3-6D5B-CBFDA580BD45}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "E:" with id:"{FD8F9377-2F45-636C-9FE3-DFDE975F75B0}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "Q:" with id:"{E81FDAF2-F21B-1A7C-86CD-E5EDDF5E1E73}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "I:" with id:"{016411C8-3747-B397-BDA4-A5B90A68548C}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "F:" with id:"{60FE7A35-B9A9-613C-D7D5-79654A408166}" cannot be initialized and will not be loaded. Management group "MG001"

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "D:" with id:"{F44935A8-B4F9-1107-111E-496A2107F67D}" cannot be initialized and will not be loaded. Management group "MG001"

    Will these stop arriving soon? So far i have about 5887 of these events last 24 hours

    Help

  29. Logical Disk Free Space says:

    I have the same problem of Maekee with the version 6.0.6957.0 . I fix the problem editing the overrides Management packs manually, deleting the logical disk overrides, and recreating from the console, my question is ¿What happen if I import this version(6.0.6958.0) now?

    Thanks Kevin!!

  30. Tomas says:

    Did anyone see an error like this? I could not import reporting MP on Server 2008 sp2 with OpsMgr SP1+971541+2028594 with upgraded databases and reporting services from 2005 to 2008 ? Any idea? Thanks!

    Invalid Management Pack

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

    The element ‘Definition’ has invalid child element ‘Report’ in namespace ‘schemas.microsoft.com/…/reportdefinition&. List of possible
    elements expected: any element in namespace ‘schemas.microsoft.com/…/reportdefinition&.

  31. Per or Per Team? says:

    Hello,

    After checking with the Network Team the servers seem to be running high but not critical as it shows…

    Is the Bandwidth performance done per NIC or per Team?

    Thanks,

    Dom

  32. Jim Devries says:

    I'm not sure if this is a bug or a feature, but in the last release the new Performance by Utilization report was showing the logical disk instances with the highest percent of idle time, even though the report was supposed to show the servers most heavily utilized.  I had to edit the stored procedure to return the busiest instances.  Was that addressed at all?

    Thanks,

    -Jim

  33. Kyle says:

    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,

  34. Kyle says:

    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!

  35. Gorgeous George says:

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

    They said not now.

    🙂

  36. Tim says:

    @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 PacksWindows Server Base OS System Center Operations Manager 2007 MPMicrosoft.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?