OpsMgr: MP Update: New Base OS MP 6.0.6958.0 adds Cluster Shared Volume monitoring, BPA, new reports, and many other changes


***Note:  This post is edited to reflect the newly shipped MP version 6.0.6958.0

 

Get it from the download center here:  http://www.microsoft.com/download/en/details.aspx?id=9296

 

 

This really looks like a nice addition to the Base OS MP’s.  This update centers around a few key areas for Windows 2008 and 2008 R2:

 

  • Adds Cluster Shared Volume discovery and monitoring for free space and availability.  This is critical for those Hyper-V clusters on Server 2008 R2.
  • Adds a new monitor to execute the Windows Best Practices Analyzer for different discovered installed Roles, and then generate alerts until these are resolved.
  • Changes to many built in rules/monitors, to reduce noise, database space and I/O, and increase a positive “out of the box” experience.  Also added a few new monitors and rules.
  • Changes to the MP Views – removing some old stuff and adding some new
  • Addition of some new reports – way cool

 

Let take a look at these changes in detail:

 

Cluster Share Volume discovery and monitoring:

We added a new discovery and class for cluster shared volumes:

image

 

We added some new monitors for this new class:

image

 

NTFS State Monitor and State monitor are disabled by default.  The guide states:

  • This monitor is disabled as normally the state of the NTFS partition is not needed (Dirty State notification).
  • This monitor is disabled as it when enabled it may cause false negatives during backups of the Cluster Shared Volumes

I’d probably leave these turned off.  Smile

 

The free space monitoring for CSV’s is different than how we monitor Logical disks.  This is good – because CSV’s are hosted by the cluster virtual resource name, not by the Node, as logical disks are handled.   What CSV’s have is two monitors, which both run a script every 15 minutes, and compare against specific thresholds.  Free space % is 5 (critical) and 10 (warning) while Free space MB is 100 (critical) and 500 (warning) by default.  Obviously you will need to adjust these to what’s actionable in your Hyper-V cluster environment.

BOTH of these unit monitors act and alert independently, as seen in the above graphic for state, and below graphic for alerts:

image

 

Some notes on how free space monitoring of CSV’s work:

  • Each unit monitor has state (critical or warning) and generate individual alerts (warning ONLY)
  • There is an aggregate rollup monitor (Cluster Share Volume – Free Space Rollup Monitor) that will roll up WORST STATE of any member, and ALSO generate alerts, when the WORST state rolls up CRITICAL.  This is how we can generate warning alerts to notify administrators, but then also generate a new, different CRITICAL alert for when error thresholds are breached.  I really like this new design better than the Logical Disk monitoring…. it gives the most flexibility to be able to generate warning and critical alerts when necessary.  Perhaps you only email notify the warning alerts, but need to auto-create incidents on the critical.  The only downside is that if a CSV volume fills up and breaches all thresholds in a short time frame, you will potentially get three alerts.

 

There are also collection rules for the CSV performance:

image

 

 

Best Practices Analyzer monitor:

 

A new monitor was added to run the Best Practices Analyzer.  You can read more about the BPA here:

http://technet.microsoft.com/en-us/library/dd392255(WS.10).aspx

This monitor is shipped DISABLED out of the box to reduce noise, however, you can enable it if you would like to create alerts when your Server 2008 R2 computers are not following best practice configurations.

 

image

 

We can open Health Explorer and get detailed information on what’s not up to snuff:

 

image

 

Alternatively – we can run this task on demand to ensure we have resolved the issues:

 

image

 

 

Changes to built in Monitors and Rules:

 

Many rules and monitors were changed from a default setting, to provide a better out of the box experience.  You might want to look at any overrides you have against these and give them a fresh look:

  • “Logical Disk Availability Monitor” renamed to “File System error or corruption”
  • “Avg Disk Seconds per Write/Read/Transfer” monitors changed from Average Threshold monitortype to Consecutive Samples Threshold monitortype.
    • This is VERY good – this stops all the noise for the default enabled Sec/Transfer monitor, caused by momentary perf spikes.
    • The default threshold is set to “0.04” which is 40ms latency.  This is a good generic rule of thumb for the typical server.
    • The default sample rate is once per minute, for 15 consecutive samples.
    • Note – make sure you implement or at least evaluate hotfixes 2470949 or 2495300 for 2008R2 and 2008 Operating systems, which affect these disk counters.
    • Make sure you look at any overrides you had previously set on these – as they likely should be reviewed to see if they are still needed.
  • Disabled “Percentage Committed Memory in Use” monitor
    • This monitor used to change state when more than 80% of memory was utilized.  This created unnecessary noise due the fact that more and more server roles utilize all available memory (SQL, Exchange) and this monitor was not always actionable.
  • Disabled “Total Percentage Interrupt Time” and “Total DPC Time Percentage”. 
    • These monitors would often generate alert and state noise in heavily virtualized environments, especially when the CPU’s are oversubscribed or heavily consumed temporarily.  These were turned off by default, because there are better performance counters at the Hypervisor host level to track this condition than these OS level counters.
  • Added “Free System Page Table Entries” and “Memory Pages per Second” monitors.  These are both enabled out of the box to track excessive paging conditions.  Also added MANY perf collection rules targeting memory counters, some disabled by default, some enabled.
  • “Total CPU Utilization Percentage” monitor was increased from 3 to 5 samples.  The timeout was shortened from 120 to 100 seconds (to be less than the interval of 120 seconds).
  • Disabled the following perf counter collection rules by default:
    • Avg Disk Sec/Write
    • Avg Disk Sec/Read
    • Disk Writes Per Second
    • Disk Reads Per Second
    • Disk Bytes Per Second
    • Disk Read Bytes Per Second
    • Disk Write Bytes Per Second
    • Average Disk Read Queue Length
    • Average Disk Write Queue Length
    • Average Disk Queue length
    • Logical Disk Split I/O per second
    • Memory Commit Limit
    • Memory Committed Bytes
    • Memory % Committed Bytes in use
    • Memory Page Reads per Second
    • Memory Page writes per second
    • Page File % use
    • Pages Input per second
    • Pages output per second
    • System Cache Resident Bytes
    • System Context Switches per second
  • Enabled the following perf counter collection rules by default:
    • Memory Pool Paged Bytes
    • Memory Pool Non-Paged bytes The Windows Computer discovery added a “ProductType <> WinNT” to further filter out incorrect discoveries.
  • The Windows Disk partition discovery changed a propertyname from “Bootable” to “BootPartition” to fix an old issue.
  • Added a new Monitortype for NetworkAdapter.PercentBandwidthUsed
  • “Available Megabytes of Memory” monitor script was updated.  The default value for threshold was changed to “2.5” to “100”.
  • Minor update to the Logical disk defrag monitor
  • Modified the tolerances and ToleranceTypes of several optimized performance collection rules.

 

A full list of all disabled rules, monitors and discoveries is available in the guide in the Appendix section. The disabling of all these logical disk and memory perf collections is AWESOME. This MP really collected more perf data than most customers were ready to consume and report on. By including these collection rules, but disabling them, we are saving LOTS of space in the databases, valuable transactions per second in SQL, network bandwidth, etc… etc.. Good move. If a customer desires them – they are already built and a quick override to enable them is all that’s necessary. Great work here. I’d like to see us do more of this out of the box from a perf collection perspective.

 

Changes to MP views:

 

The old on the left – new on the right:

imageimage

 

Top level logical disk and network adapter state views removed.

Added new views for Cluster Shared Volume Health, and Cluster Shared Volume Disk Capacity.

 

 

New Reports!  Performance by system, and Performance by utilization:

 

There are two new reports deployed with this new set of MP’s (provided you import the new reports MP that ships with this download – only available from the MSI and not the catalog)

***Note:  These two new reports are shipped in their own new MP: the Microsoft.Windows.Server.Reports.mp.  These reports are supported only when your SQL servers supporting the OpsMgr backend are SQL 2008 or later.  They will not deploy on SQL 2005. 

 

 

image

 

To run the Performance by System report – open the report, select the time range you’d like to examine data for, and click ‘”Add Object”.  This report has already been filtered only to return Windows Computer objects.  search based on computer name, and add in the computer objects that you’d like to report on.  On the right – you can pick and choose the performance objects you care about for these systems.  We can even show you if the performance value is causing an unhealthy state – such as my Avg % memory used – which is yellow in the example:

image

 

Additionally – there is a report for showing you which computers are using the most, or the least resources in your environment.  Open “Performance by Utilization”, select a time range, choose a group that contains Windows Computers, and choose “Most”.  Run that, and you get a nice dashboard – with health indicators – of which computers are consuming the most resources, and potentially also impacted by this:

Using the report below – I can see I have some memory issues impacting my Exchange server, and my Domain Controller is experiencing disk latency issues.

image

 

By clicking the DC01 computer link in the above report – it takes me to the “Performance by System” report for that specific computer – very cool!

 

 

 

 

Summary:

In summary – the Base OS MP is already a rock solid management pack.  This made some key changes to make the MP even less noisy out of the box, and added critical support for discovering and monitoring Cluster Shared Volumes.

 

 

Known Issues in this MP:

 

1.  A note on upgrading these MP’s – I do not recommend using the OpsMgr console to show “Updates available for Installed Management Packs”.  The reason for this, is that the new MP’s shipping with this update (for CSV’s and BPA) are shipped as new, independent MP’s…. and will not show up as needing an update.  If you use the console to install the updated MP’s – you will miss these new ones.  This is why I NEVER recommend using the Console/Catalog to download or update MP’s…. it is a worst practice in my personal opinion.  You should always download the MSI from the web catalog at http://systemcenter.pinpoint.microsoft.com  and extract them – otherwise you will likely end up missing MP’s you need.

2.  The “Available Megabytes of Memory” monitor script was updated in this version.  Along with this update, the default threshold was changed from “2.5” to “100”.  The current monitor – the “100” reflects “MBytes”.  This value is a good indication of memory pressure, however, in your environment this might create a lot of alerts that might not be actionable depending on your environment.  You should review any previous overrides you have set on this monitor, and adjust the default setting as necessary.

3.  The “Logical Disk Free Space” monitors were completely re-written.  The datasource and monitortype was changed from a script that runs once per hour and drives monitor state, to a new script that runs once every 15 minutes, and drives monitor state after 4 consecutive samples.  That seems like a good design change to control any noise from fluctuating disks.  However, running the script every 15 minutes might increase the performance impact with more scripts per hour executing on your agents.  The script datasource no longer outputs the %Free and MBFree values in the propertybag, therefore – these had to be removed from the Alert Description and Health Explorer.  The monitor still works as designed – it creates an alert whenever the threshold is breached.  The only change exposed to the end user – is that these values for actual free space in MB and % are not going to be exposed to the alert notification recipient.

4.  When you try and run the report “Performance By Utilization” you get an error:

An error has occurred during Report Processing.

Query execution failed for dataset ‘PerfDS’.

Procedure or function Microsoft_SystemCenter_Report_Performance_By_Utilization has too many arguments specified.

On a reporting server without remote errors enabled – you might only see the top two lines in the error above.  I recommend enabling remote errors on you reporting server so the report output will show you the full details of the error:   How to Enable Remote errors on SQL reporting server

If you are getting the “too many arguments specified” error, this is caused by the Windows 2003 MP.  It also contains the stored procedure definition for Microsoft_SystemCenter_Report_Performace_By_Utilization, however the definition in the Windows 2003 MP is missing the “@DataAggregation INT,” variable.  Depending on the MP import process, it is possible that the stored procedure from the Microsoft.Windows.Server.Reports.mp will not be deployed, which does contain this variable.  In order to resolve this issue – we need to modify the existing stored procedure, and add the “@DataAggregation INT,” line just below the “Alter procedure” line.  Ensure you back up your Data Warehouse database FIRST, and if you are not comfortable editing stored procedures, open a case with Microsoft on this issue.  An alternative, is to use the SCOM Authoring console, open the Microsoft.Windows.Server.Reports.mp file, go to reporting, Data Warehouse Scripts, Microsoft.Windows.Server.Reports.PerformancebyUtilization.Script properties, Install tab, and copy the actual script.  You can run this script in a SQL query window targeting your DW database, and it will create/modify your sproc.

The above instructions ONLY cover the SPECIFIC “Too many arguments” error.  If you are getting ANY OTHER error, the above method will not resolve your issue and you should open a case for resolution.


Comments (104)

  1. Anonymous says:

    There seems to be an updated version since yesterday. And now with threshold instead of theshold. I haven't looked yet if other issues are also fixed, but this one was the most important one for me.

  2. Anonymous says:

    @ Roland and Kevin,

    I was getting the same "too many arguments" error.  After confirming that the @DataAggregation parameter was missing from the stored procedure, and not being as skilled as Roland I just used the authoring console to open the Microsoft.Windows.Server.Reports.mp, from there I went into the reporting tab > reports > Microsoft.Windows.Server.Reports.PerformanceByUtilication >> Click on the dependencies tab then edit the script.  Then I copied the whole script and ran it against the DW (using SSMS).  The @DataAggreration parameter was there and the Utilization Reports are now working.  

  3. Anonymous says:

    Logical Disk Free Space Monitor Stopped Working with Upgrade to Windows Server Management Pack v6.0.6958

    See social.technet.microsoft.com/…/ba74f435-0262-48e7-88a8-cfce7a5ad9d1

  4. Anonymous says:

    @ Azren –

    This new feature is all or nothing.  It simply runs the OS built in functionality for retuning ANY errors from the BPA.  In SCOM – you can either turn it on, or off.  I expect many customers will disable this and consider it noise, unless they have a commitment to run all servers in accordance with the BPA.

  5. Anonymous says:

    @moter –

    It takes up to an hour to deploy the reports.  This is normal.  Did you wait long enough?  If you have a report that is not deploying – you will see some srtitical events on the RMS OpsMgr event log stating the "why".

  6. Anonymous says:

    @Vijay H –

    I have heard these reports are limited in output.  I imagine they did this in order to make them be able to return data in a timely fashion, as this is a lot of data to pull back with lots of different counters.  I imagine it was more scoped to indinvidual app and server team owners.  You could take these reports in XML and use them to create your own, modifying the SQL statements so that they return more than 50.

  7. Anonymous says:

    @moter –

    I only have SQL 2008R2 running here.  Would be very odd if there was something in this report that didnt work on SQL 2005…. I'd bet we will be hearing more about it if that's the case.

  8. Anonymous says:

    Personally – I would consider waiting for a few months on this MP, to see if we ship a newer version quickly or not.  That's usually driven by customer feedback.

  9. Anonymous says:

    Hi,

    We are in process of upgrading the Base OS MP. As per the note for Report MP it can not imported on a SQL 2005 DW. If i mport rest all Mps will my old reprts will still work for me to get availability report and perf reports?

  10. Anonymous says:

    @worldzfree –

    You are 100% correct.  I raised a bug on this internally.  There is no way for you to change this back, as this is the alert description, and the alert description is not modify-able via overrides…. so you cannot change it.  Your only option when you dont like a specific alert description in a sealed MP, is to disable the workflow and recreate the workflow in your own custom MP, with your own custom alert description.  The alert still works and still alerts when the configured threshold is crossed, so technically the MP still works as designed.  It's funny – because on the new cluster shared volume free space alerts – we do display the measured value that breached the threshold in the alert description.

  11. Anonymous says:

    @GeorgeQ –

    The problem is that you have created an override for "TimeOutSeconds" previous on the old MP – and this overrideable parameter was removed in the current version of the base OS mp disk monitor.

    The new monitor doesnt have this exposed, so it is complaining about your override MP – no more changes can be made to it (add or delete) so you must export your override MP to XML, delete the overrides manually, and then reimport.  Read through all the other comments as I talk about this for other params.

  12. Anonymous says:

    Gary – this is interesting.  I recently heard some guys on the msmom list talking about issues like this, but I have not seen it myself.

    They were trying to isolate the netman process.  This was from Eric Stanaway and Ryan Reitz – are they part of your issue or seperate?

    We did include a new script based network utilization monitor… I wonder if we are creating a leak or something by using this new script, exposing an OS issue that is not otherwise seen because we query it on a regular basis?  We have seen in the past leaks (memory, handles, threads) created by querying services, such as support.microsoft.com/…/2618982, support.microsoft.com/…/981314, support.microsoft.com/…/968760, and the DNS WMI provider leak.  All are Operating System issues, but exposed by SCOM querying something over and over.

    What OS and SP level are you seeing this on?  Have you monitored for a leak in any process?

  13. Anonymous says:

    @Sören –

    You are correct.  I pointed out that we changed the script for this monitor…. apparently the old "2.5" caused a lot of confusion as it is.  The new monitor makes a lot more sense.  Certainly I wish the MP authors would do a better job of documenting all these little changes, as they do impact customers in the fact that customer overrides are impacted.

  14. Anonymous says:

    @Adam –

    SQL_Latin1_General_CP1_CI_AS is the ONLY supported collation for the SQL instances hosting SCOM database server roles, and for the SCOM databases themselves.  I would guess that you are running an unsupported configuration.

  15. Anonymous says:

    Ok guys – I will look into this and see what I find out.

  16. Anonymous says:

    @Azam – did you see in the article where I discussed that some collection rules were changed to disabled by default?  You might examine which counters those reports use and ensure that the collection rule is enabled.

  17. Anonymous says:

    I think they should pull this updated MP until some of the more major flaws are fixed.  Having people rename SystemDriveWarningMBytesThreshold in their overrides is just going to cause problems when this is eventually fixed (they will have to manually update the overrides again.  There are so many spelling mistakes in Alert names, alert descriptions, product knowledge, etc., that I hope the product teams would strive to fix the existing mistakes and not introduce any new ones.

    I'll be holding off until an update MP is released to address these issues, I think anyone who hasn't already imported this update should do the same.

  18. Anonymous says:

    @ bsuresh –

    This means someone set an override and modified the debugflag setting previously.  This should not be used.  The new version of the monitor – does not have a debugflag option.

    Simply find the override(s) for debugflag and remove them.

  19. Anonymous says:

    Thanks Kevin.  

    All of our clusters are 2008 R2 Hyper-V clusters. So, with the new cluster discovery feature would we still need the the Windows Cluster MP?

    Thanks,

    Tom

  20. Anonymous says:

    Kevin,

    I have imported updated version MP in my environment. When I try to override any monitor for Windows 2003, I am getting below error.

    : Verification failed with [1] errors:

    ——————————————————-

    Error 1:

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskb8eb2ab4a9674948945518a134ec651d].

    Cannot find OverridableParameter with name [DebugFlag] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    ——————————————————-

    Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskb8eb2ab4a9674948945518a134ec651d].Cannot find OverridableParameter with name [DebugFlag] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskb8eb2ab4a9674948945518a134ec651d].

    Cannot find OverridableParameter with name [DebugFlag] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Cannot find OverridableParameter with name [DebugFlag] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    From your posts, I could see that [DebugFlag] was deleted and it will be fixed on next release. Can you please tell the workaround for this?

    Thanks in advance!!!

    Suresh

  21. Anonymous says:

    @Scott M. – yes that VBS is misspelled – however, it works as designed so this is zero impact to the MP.

  22. Anonymous says:

    Oh I'm sorry. My previous remark is wrong. The issue is still present :(

  23. Anonymous says:

    Hi Kevin,

    thanx for the reply, reports started to fetch the data now, but when i asking to generate a report for last 7 or 10 days its not fetching the data for last two days.

    Regards.

  24. Anonymous says:

    @Peter – yes – you should remove that MP.  It was only developed for SQL 2008, and I dont believe there is any timeline to update this for SQL 2005.

  25. Anonymous says:

    Hi Kevin,

    After importing the MP, the performance system report is not displaying the "Average Percentage memory used" and "Network Adapter data".

    regards

  26. Anonymous says:

    Yes – your old reports will work just fine – the only thing you will lose is a few brand new reports that we just wrote for this MP.  Nothing else will be impacted.

  27. Anonymous says:

    @Roland –

    Interesting!  Can you try and scope the Utilization report to a smaller group?  What group did you choose?  I wonder if there are too many group members – if this might be the cause.  Also – there is a limit to SQL 2005 and how many object tables it can bind together – I wonder if you are on SQL 2005 or SQL 2008?  Also – does it matter if you choose from Yesterday to Today – only scoping the report to the last 24 hours?

  28. Anonymous says:

    @Robert – this is either due to your specific execution policy and this powershell clashing – or something environmental.  Normally I would expect "remote signed" to work just fine.  If you manually perform a Get-ExecutionPolicy -List on a server – do ALL types show RemoteSigned?  It is possible that this specific monitor code does not work under RemoteSigned policy, I can't say I have heard this.

  29. Anonymous says:

    @martit01 –

    The new MP only discovers and monitors Cluster Share Volumes.  The actual Cluster MP does much more – it discovers and monitors entire cluster resources and resource groups.  Yes, you'd still need the cluster MP for end-to-end cluster monitoring.

  30. Anonymous says:

    Ok guys – I see whats wrong.

    Yes – there is a bug here.  They did modify how this monitor works – I dont know why…. but the composition of the monitortype is completely different.  They removed some of the previous override-able parameters… like debugflag and timeoutseconds.  However – the key problem that you are experiencing is that they mispelled the Overidable parameter for the 2003 disk free space monitortype.  

    Previously it was correctly spelled:

    SystemDriveWarningMBytesThreshold

    Now it is defined as:

    SystemDriveWarningMBytesTheshold

    It is missing the "r" in "Threshold".

    This is now breaking the Override MP verification and causing your issue.  Here are your options for a workaround:

    1.  Go directly into the XML, and delete that override which references that property.  Then re-create it back again normailly using the UI.

    or

    2.  Go into the XML, find all the overrides that reference this monitortype, and then edit the XML for the override-able property to the new mispelled word.  :-)

    Note – I will report this… but if we "fix it" with a new version it will break your adjusted overrides again… so keep that in mind.

  31. Anonymous says:

    @Mehmet Ali Buyukkarakas – There is no reason that you could not monitor disk space on every server.  There are workarounds posted to each issue.

    @Moe – no – I have not heard about this one yet.  At what frequency are you seeing the spikes?  It is common for CPU to spike when an object runs a WMI query, but these should only last a few seconds generally unless the server is virtualized and the host CPU is oversubscribed.

  32. Anonymous says:

    Hi Kevin

    We have a similar error message as it moter describes.

    The content of our error message is:

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '8a477b44-6d7b-fef5-beff-b328e34b7400', Management Pack Version-dependent Id: 'b7931af6-807c-4780-9a89-c2543de3ffef'; Target: Database, Server name: 'ServerDB', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Cannot assign a default value to a local variable.

    Must declare the scalar variable "@loop".

    Must declare the scalar variable "@loop".

    Incorrect syntax near the keyword 'FROM'.

    Must declare the scalar variable "@loop".

    additional we have the following error message

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '8a477b44-6d7b-fef5-beff-b328e34b7400', Management Pack Version-dependent Id: 'b7931af6-807c-4780-9a89-c2543de3ffef'; Target: Database, Server name: 'ServerDB', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Cannot assign a default value to a local variable.

    Must declare the scalar variable "@loop".

    Must declare the scalar variable "@loop".

    Incorrect syntax near the keyword 'FROM'.

    Must declare the scalar variable "@loop".

    Do you have any idea? May you give us some help with it?

    Thanks a lot.

  33. Anonymous says:

    Hi,

    We are experiencing the same issue as Sylvain and others with SQL Server 2005 DWH db.

    Anyone found a solution to this, besides upgrading to SQL Server 2008.

    Thanks and regards,

    Maurice

  34. Anonymous says:

    @Sylvain –

    Just FYI – we dont test/support mixed versions of SQL server between the OpsDB instance, Warehouse DB instance, and SQL Reporting Services instance….. these all need to be the same version.  While it technically "should work" as stated, it is not recommended, tested, or supported in that state.  I'd recommend upgrading your SQL DB engine to the same version fo SQL as your reporting.

  35. Anonymous says:

    @worldzfree

    The best way to get action taken for any requested change is to open a support case and request a DCR (Design Change Request) or a RFH (Request for Hotfix) with a business case.  Customer cases get the focus and evaluation for changes.  Like I said I have opened a bug internally on this topic, but customer impact is what will drive it.

  36. Anonymous says:

    @Vijayh – Can you be specific.  Exactly which workflows, on which OS?

  37. Anonymous says:

    @ worldzfree –

    Why on earth would you export out your override MP first?  SCOM is designed so that's never necessary.  The whole purpose of using sealed MP's was that you can upgrade them without fear or issue – your override MP's stay intact and still apply.  There isnt any reason to export or remove your unsealed MP's except for simple backup purposes.  

    As to your specific issue – I am not aware that were changed any overrideable parameters in the Free space monitortypes….

  38. Anonymous says:

    sorry, I have sent 2 times the same error

    here is the correct error

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'f652ee20-fdfd-1cb2-5491-c2cc5fb8daa6'; Target: Database, Server name: 'nvabbst093SCOMP03', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near the keyword 'ELSE'.

  39. Anonymous says:

    Hi Kevin

    We have created lot of overrides for the Parameter="SystemDriveWarningMBytesThreshold". Just curious whether we need to wait for this bug to fix or implement by changing the Parameter="SystemDriveWarningMBytesTheshold".  

  40. Anonymous says:

    I cannot find the Microsoft.Windows.Server.Reports.mp. I downloaded the msi and extracted but the reports mp isn't in there.. Any ideas?

    Kind regards

  41. Anonymous says:

    Thanks a ton Kevin!!!

    I have found that I had an override set for [DebugFlag] and it was mapped to xxx unsealed MP. Now I have deleted the references present in xxx unsealed MP and reimported the same. This resolved by problem :-)

    Now I am able to override Windows 2003 MP with NO errors.

    Question:

    I have imported latest Reports MP but it is giving graph in vertical bars. This is becoming challenging(more than 30 vertical bars are so conjested) when I pull the data for more than one month for trending.

    Any clues to have the graph in Landscape with dates mentioned for each bar. While pulling report for more days, dates are missing for each vertical bar. Any way to fix this in XML?

    Now I have exported the sealed Reports MP and deleted some rows to have only Logical Disk – "Average Percent Space" Used rather than all counters. Waiting for reports to display in Reporting.

    Thanks,

    Suresh

  42. Anonymous says:

    The problem of the Performance Utilization report is caused by the fact that Windows Server 2003 Operating System management pack also contains a definition for the stored procedure Microsoft_SystemCenter_Report_Performace_By_Utilization which does not contain the parameter @DataAggegation

    I extracted the definition of the stored procedure of the Microsoft.Windows.Server.Reports.mp and deployed this manually to the datawarehouse database; when this is done the report works.

    I believe the solution to the problem of the Performance Utilization report is the incompatibility between the Windows Server 2003 Operating System MP and the Microsoft.Windows.Server.Reports.mp

    Roland

  43. Anonymous says:

    Gary – I have seen enough now.  While it looks like an issue with the OS – SCOM querying the WMI provider is likely what causes the fault in netman.dll.

    blogs.technet.com/…/opsmgr-network-utilization-scripts-in-baseos-mp-version-6-0-6958-0-may-cause-high-cpu-utilization.aspx

    I'd just disable those workflows.

  44. worldzfree says:

    i exported out my override mp and imported this MP.  now when i try to re-import my old overrides i get the following error.  looks like a parameter name has changed?  any ideas on how to find the new name and fix it?

    Error 1:

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskf9fec03585104ba99c78728d27130271].

    Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    ——————————————————-

    Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskf9fec03585104ba99c78728d27130271].Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]).

  45. Roland De Clerck says:

    When running the report Performance by Utilization I got an error from the reportserver

    System.Data.SqlClient.SqlException: Procedure or function Microsoft_SystemCenter_Report_Performace_By_Utilization has too many arguments specified

    For the new report Performance by system I'll try this tomorrow as its based on the daily counters of the dataset

  46. Tayn says:

    Hi

    I have the same problem than worldzfree.

    I make upgrade of the mp Windows 2003, but now I cant add a new override on my override MP because I have the same error:

    Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.

    : Verification failed with [1] errors:

    ——————————————————-

    Error 1:

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDisk4a64b8b661d04d7299b8a050ae70475c].

    Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    ——————————————————-

    Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDisk4a64b8b661d04d7299b8a050ae70475c].Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDisk4a64b8b661d04d7299b8a050ae70475c].

    Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Cannot find OverridableParameter with name [SystemDriveWarningMBytesThreshold] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    How i can fix it?

    Thx

  47. Tayn says:

    Thx it is ok after modify! But the problem is for Windows 2003 AND Windows 2008.

  48. Robert says:

    After importing the MP, soon I began to receive this error for all my 2008 servers (219) except for 1.

    "There has been a Best Practice Analyzer engine error for Model Id: 'Microsoft/Windows/ApplicationServer' during execution of the Model. (Inner Exception: One or more model documents are invalid: {0}Discovery exception occurred processing file '{0}'.

    Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of "RemoteSigned". Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information, please see "Get-Help Set-ExecutionPolicy.") For more information on the BPA issues detected, view the diagnostic output in the State Change Events tab for the Windows Server 2008 R2 Operating System BPA Monitor in Health Explorer. Alternately, the View Best Practices Analyzer compliance results task can be manually executed to have the results returned."

    On all my 2008 servers, powershell ExecutionPolicy is forced to RemoteSigned by a GPO (except the one that is working, it's Unrestricted).

    How could I override this ?

    Thanks

  49. Azren says:

    How do I override BSA rule in such away that my RMS and DW server are not flagged as needing to the WSUS role added ?

    Server Role:  Microsoft/Windows/WSUS

    ====================================

    Title      : The Windows Server Update Services Role should be installed

    Problem    : The Windows Server Update Services Role is not installed.

    Impact     : The WSUS Best Practices Analyzer scan will not run unless the WSUS Role is installed on the machine.

    Resolution : Install the WSUS Role through Server Manager.

  50. moter says:

    The new MP looks great, however I've imported the new Reports MP, and the new reports just aren't in the console.  Is there some issue with them being hidden or anything?  The reporting MP is there, I've even removed it and reimported with success, it's just not in the reporting section.  Any ideas?

  51. moter says:

    at the reimport of the MP my scom server logged this alert:  

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'f652ee20-fdfd-1cb2-5491-c2cc5fb8daa6'; Target: Database, Server name: 'SCOMDB01SCOM,1036  ', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near the keyword 'ELSE'.

  52. moter says:

    DW SQL 2005 version is 9.0.4053.  The error makes me think the minmum SQL version/servicepack/cumulative update hasn't been met.

  53. moter says:

    Indeed.  Seems to me that most syntax error stuff like what's in the error i posted is usually due to changes between cumulative updates or service packs.  4053 is from a security update in October of 2009.  heh, upgrading SQL for scom tough to do?

  54. Robb Dilallo says:

    @moter, I've imported Microsoft.Windows.Server.Reports.mp into 3 different OpsMgr environments, and the only management group that's throwing out the same error as what you're receiving also has SQL 2005 for a DW and SSRS. There's a chance that the reports weren't written for SQL 2005 and / or tested with SQL 2005.

  55. Hi Kevin,

    I'm also using SQL 2005, and I've got the same error message than Sven and Moter.

    Thank you

    Regards

    Christopher

  56. corwin says:

    The – Microsoft.Windows.Server.Reports.mp importing without errors. But I can't find new repots in Reporting Panel :(

    In what may be the reason ?

  57. Chrizz06 says:

    Hi Kevin,

    Same issue here, we are running SQL2005 v 9.0.3042 (SP2 version)

    Kind regards

  58. Robb Dilallo says:

    The new Windows Server Reports that was just released doesn’t seem to work with SQL 2005 Reporting Services. In the header of the report definition in each report, it shows the xmlns of schemas.microsoft.com/…/reportdefinition. It looks as if they were written for SQL 2008 Reporting Services.

  59. TiLeCa says:

    I have the same issue when importing the Microsoft.Windows.Server.Reports.mp

    what kind of further investigantions mght help to solve this?

    Report Server is running on SQL 2005 EE build 9.0.5057

  60. Robb Dilallo says:

    @TiLeCa – No further investigation is needed. It doesn't work with SQL 2005 Reporting Services. My recommendation is to post in the OpsMgr Management Pack forum to get some attention on this matter.

    social.technet.microsoft.com/…/threads

  61. Sylvain says:

    I have the same problem for the reporting.  My datawarehouse is running on SQL2005 but my Reporting Services is running on another machine running 2008 R2 RTM. (no cumulative update). Still not working.

    Event Type: Error

    Event Source: Health Service Modules

    Event Category: Data Warehouse

    Event ID: 31565

    Date: 10/3/2011

    Time: 11:15:34 AM

    User: N/A

    Computer: SCOM01

    Description:

    Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'f652ee20-fdfd-1cb2-5491-c2cc5fb8daa6'; Target: Database, Server name: 'server', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near ','.

    Incorrect syntax near the keyword 'ELSE'.

  62. worldzfree says:

    kevin,

    the mispelling work around fixed my  the re-import.  i am now having the same issue as everyone else with 31565.  was there like one person doing the QA on this MP before it was released?

  63. Robb Dilallo says:

    @worldzfree, the product support folks are looking into the issues identified and discussed above. More to follow…

  64. Robert says:

    @ Kevin-

    I've found that it's a knowned issue not corrected by Microsoft.

    support.microsoft.com/…/2028818

    Thanks

  65. worldzfree says:

    it looks like this MP has also changed what the default alert looks like for "Logical Disk Free Space" monitor.  In the previous MP the alert notification looked like:

    "Alert description: The disk S: on computer FAKE.world.local is running out of disk space. The values that exceeded the threshold are 0% free space and 344 free Mbytes.

    Now it just shows the first sentence.  

    "Alert description: The disk S: on computer FAKE.world.local is running out of disk space."

    Any ideas how to easily fix this?

  66. worldzfree says:

    After further investigation it looks like the Windows Server 2000 Logical Disk alert has stayed in the original alert format

    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.

    The Windows Server 2003/2008 Logical Disk alerts are now shortened without the valuable data.  

    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.

    Any way to get this fixed?

  67. David Biot says:

    The problems are even worse: at a customer's site I got the following event every 15 minutes after importing the management pack:

    Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "C:" with id:"{02344336-14B7-98A5-88B6-4EED59743528}" cannot be initialized and will not be loaded. Management group "MGNAME"

    Effectively making the free disk space monitor not working anymore! Allthough it does show up as healthy.

    I do not understand how this got past testing. This is a major issue. Thanks to this guide I can change the overrides to re-enable monitoring.

  68. Mehmet Ali Buyukkarakas says:

    This is insane ! We cant monitor the disk space almost on every server. I dont undertstand how kind of quality control was applied to this MP…

  69. Moe says:

    I imported this MP into my environment and noticed that my CPU utilization on mer 2008 r2 Core servers are spiking. The process causing this is WmiPrvSE.exe. Any ideas ?

  70. Moe says:

    Hi Kev,

    The server is a virtual host but isnt over subscribed. It is constantly high with spikes above 50% every few minutes. I also notice it happening on a domain controller running server core. Full featured installations dont seem to have any issues.

    I need to roll back to the old mp's but there are 2 many dependencies to the base os management packs. Any help would be appreciated.

    I tried changing the old mp versions to supersede the new 1 but had no luck.

    MD

  71. Sad says:

    I'm bummed this MP has so many issues, mispellings, bugs.

    Was 2 years not enough time to develop, test and debug?

  72. tom says:

    Hello!

    My biggest Problem with this mmp is – that freespace-Alerts are sent without the values e.g. " The values that exceeded the threshold are 1% free space and 516 free Mbytes".

    Everytime SCOM send a Freespace Alert my Boss asks me about the value…

    How can I fix this??

  73. tom says:

    sorry Kevin just found your answer to my question an page 1

  74. Mike says:

    Found a bug,

    I found a problem, they added a new counter to 2008R2 for the new cores.  I have a server that has 4 10 core systems and 20 logical processors.  The normal Processor Monitor utilizes the object Processor and the counters only go up to 40, it is also showing incorrect processor utilization in opsmgr.  They have a new object called “Processor Information” ant it shows all 80 CPU’s correctly in performance monitor as well.  The Monitors in OpsMgr do not use the correct new counters for 2008R2.

  75. Scott M. says:

    Found another bug and have opened a case with PSS. There is a workflow called "Microsoft.Windows.Server.2003.NetworkAdapter.PercentBandwidthUsedTotal" that tries to run a VBS – unfortunately the VBS that is being called is misspelled: "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs". Notice the "r" is missing in "NetworkAdapter"? First "theshold" and now this LOL – if MS is hiring for proofreaders, let me know and I'll apply. Should be able to pay around $85k/yr, right? I won't even take up a cube, this is easily a work-from-home job 😉

  76. Sören says:

    Threshold for the monitor "Available Megabytes of Memory" has been changed from 2,5 to 100MBytes. Can´t see anything about this in the documentation…

  77. Brad says:

    Hi Kevin, I was pretty happy to get my hands on these reports and run them as they look a lot better and are divided more logically!

    I just have an issue as to what the reports are actually showing…

    The data in the bar graphs doesn't line up with what the table reads.  Have you noticed the same thing?  I am not sure what the issue actually is but I'll be doing some investigating on my end…

  78. Adam says:

    When running either of the reports I get a

    An error has occurred during Report Processing.

    Query execution failed for dataset ‘PerfDS’.  ((or 'PerformanceData' for the perf by system)

    Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation

  79. Gary Jukes says:

    I have noticed one other query about this on the System Center Central forums, but they're down for maintenance at the moment so figured I might as well add a comment here to see if anyone else has experienced it.

    Since installing this MP, we have seen three instances of what appears to be WMI failing. We have netman.dll faulting, which is causing quite a few critical services to fault. The only way to bring them back online is restarting the affected server. At the same time that netman.dll faults, we get the Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs script unable to output property bag data. I don't know if this is a coincidence, but we've only just started getting this after we updated this MP.

  80. Gary Jukes says:

    Hi Kevin, I'm not sure who Eric or Ryan are. They're definitely not part of the organisation that I'm in so am assuming that it is separate.

    The servers we've had experience this issue so far are 2003 R2 SP2, both x86 and x64. They have different roles installed as well so not all have the same functions. I haven't had a chance to check for any leaks. I have applied an override for the Percentage Bandwidth Used Total rule and monitor to all Server 2003 Network Adapters as this seemed to be the one that was always mentioned when the services faulted. Could just be a coincidence that this was the one that was running at the time and it's the one that tipped it over. The other person that I've seen mention this issue was also on a 2003 R2 server with this particular rule. I can enable it again though for a few less critical servers if I'm not seeing any leaks.

    We haven't seen this in our test environment, however the servers we're monitoring in there are all virtual. The ones this issue has occured on are all DL380 G5's. We haven't had it occur on any other physical devices.

  81. Peter Gamharter says:

    Hey Kevin!

    Is there any timeline for fixing the problems with SQL2005? How should i handle this? Just delete the Microsoft.Windows.Server.Reports.mp :-( ?

    Best regards,

    Peter

  82. Joseph says:

    Hi Kevin,

    I have imported only Microsoft.Windows.Server.Reports.mp from the MSI(from the link mentioned above). But even after 4 hrs it didnt report in Reporting tab. MP import was successful and no related errors in RMS eventlog. Please help me out here. Do importing only Report MP will give the expected result or Do I need to import other MP's present in MSI?

    Thanks,

    Joseph

  83. Joseph says:

    Kevin,

    I have imported only reports MP from the MSI but it didnt appear in console even after 4 hrs. Dimporting only reports.mp will give expected result or Do i need to import all Updated Base OS MP's mentioned in MSI.

  84. Vijay H says:

    Hello Kevin,

    I followed the same and everything works fine. I just have one query that "Performance by Utilization" report is capable of giving reports for maximum 50 servers, i have 1300 servers are in SCOM monitoring. Is there any way to get reports for all the systems?

  85. Vijay says:

    Thanks Kevin. I have another issue with my availability Reports. My agents are showing healthy in SCOM console but when i generate availability reports it is showing 100% but monitor disabled or unmonitored(full white in colour no green). What should i check for this?

  86. @Kevin says:

    My agents are showing healthy in SCOM console but when i generate availability reports it is showing 100% but monitor disabled or unmonitored(full white in colour no green). What should i check for this?

    Any help would be highly appreciated. even i created linked report and ran the report against agent watcher group. but no luck

    Regards,

    Vijay

  87. Vijayh says:

    Hello Kevin,

    I am using this new version of base OS MP in my environment and for Memory the alerts are triggering for even 45%, 50% which should not be right? Is there anything i need to check? Please advice

    Regards,

    Vijay

  88. vijayh says:

    Hello Kevin,

    I've received alerts from windows 2003 and windows 2008. Alert name is Available megabytes of memory is too low and the description is "The threshold for the MemoryAvailable MBytes performance counter has been exceeded. The value that exceeded the threshold is: 59.666666666666664." This is an example.

    59% is well below value and even i'm getting alert for 47%, 45% etc.

  89. vijayh says:

    Kevin,

    Any help would be more useful to me!! today i received alert with value 45% when i checked that server it has 1GB memory so as per threshold if 100MB free the value would be 90% but alert triggered as 45%..did anything missed here?

    Regards,

    Vijay

  90. GeorgeQ says:

    I have this problem with the logical disk for 2003. Can someone please help?

    : Verification failed with [1] errors:

    ——————————————————-

    Error 1:

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskc23ecc07960d4e979dcb0487954031bf].

    Cannot find OverridableParameter with name [TimeoutSeconds] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    ——————————————————-

    Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskc23ecc07960d4e979dcb0487954031bf].Cannot find OverridableParameter with name [TimeoutSeconds] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Failed to verify Override [OverrideForMonitorMicrosoftWindowsServer2003LogicalDiskFreeSpaceForContextMicrosoftWindowsServer2003LogicalDiskc23ecc07960d4e979dcb0487954031bf].

    Cannot find OverridableParameter with name [TimeoutSeconds] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

    : Cannot find OverridableParameter with name [TimeoutSeconds] defined on [Microsoft.Windows.Server.2003.FreeSpace.Monitortype]

  91. GeorgeQ says:

    I kept on deleting the overrides but to no avail, the error message kept on popping out. Please help?

  92. GeorgeQ says:

    @Kevin, that did the trick, i was not sure how to delete the entries, and your last post really helped me a lot. Thank you.

  93. Vijayh says:

    I would require disk space report like total space free space and % free space in report. Is it possible to do that? My management is eating my head to get this from SCOM. Please help me here.

    Any help would be really appreciated.

  94. Thomas Bredvig says:

    Another issue on this management pack is that the Processor object for server 2008 R2 is wrong.

    The 2008 R2 servers use a new object named Processor information which unlike the old Processor object "registers" more than 64 cores.

    This is an issue on both performance reporting and alerting on Server 2008 R2 servers.

    We have sent the issue to our TAM who is looking into the case right now.

  95. Mas says:

    Hi there.

    I've installed the MP, but when I try to do the reports, they're empty. I get no errors, but the report is empty, no data.

    Anyone knows ?

    Regards,

  96. Anonymous says:

    Pingback from Logical Disk free space alerts don???t show percent and MB free values in the alert description in OpsMgr 2007 – Information Store – ExchangeBlog – TechNetKlub

  97. Anonymous says:

    Microsoft’s very own Kevin Holman just posted a great article over on his blog talking about an issue

  98. Anonymous says:

    Pingback from Logical Disk free space alerts don???t show percent and MB free values in the alert description in OpsMgr 2007 – System Center Mindenkinek – TechNetKlub

  99. Anonymous says:

    NOTE: This article has been updated – please see the latest version at: http://blogs.technet.com/b/kevinholman

  100. Samir FARHAT says:

    Hi,
    Please, how can we generate a report of the cluster shared volumes usage ? Is this report exists ?
    Thanks

  101. Siva says:

    how can i increase the number of systems in the "Performance by utilization" report it shows the maximum as only 50

  102. Hussain says:

    Hi ,
    Kevin , I ran the the report it show blank so kindly advise .

  103. ErHussain says:

    Hi ,
    Kevin I followed you steps but when run the report it show blank so kindly advise.