A lot of people who are monitoring their Windows Servers with OpsMgr has probably read in the blog of Kevin Holman, that in the latest version of the Windows Server OS MP changes are made to the Logical Disk free space monitors both for Windows Server 2003 and 2008 disks. The changes that are made is that in the alert description of the Logical Disk Free space monitors no values are shown of percentage free space and MB free space anymore.

As Kevin describes in his blog a lot of customers would like to have these values back in the alert description. Kevin also describes another approach on how to fix this issue with the help of the blog of Daniele Grandini. Personally I prefer the fix of Daniele by adding diagnostics to the existing sealed Logical Disk Free space monitors, which will add the actual disk free space in MB and % to the Health explorer.

Unfortunate by testing the sample MP of Daniele Grandini, I ran into a problem. In the Health Explorer the output of the diagnostic task was displaying a WMI error: "Unable to open WMI Namespace 'winmgmts:\\\root\cimv2'. Check to see if the WMI service is enabled and running, and ensure this WMI namespace exists.."

I found out that in the sample MP of Daniele a visual basic script was added to collect the values of percentage free space and MB free space. In this visual basic script there are two lines that are not correct. To fix this you have to do the following or download the New Sample MP.

1. Open the XML file "QND.Windows.Server.2008.LDisk.xml" in notepad.
2. Search for the line: " TargetComputer = oArgs(0)"
3. Replace the line with: "TargetComputer = WScript.Arguments.Item(0)"
4. Search for the line: "P_DiskLabel = oArgs(1)"
5. Replace the line with: "P_DiskLabel  = WScript.Arguments.Item(1)"
6. Save the XML file
7. Import the new Sample MP in Operations Manager. (Note: if you already imported the original Sample MP, you have to increase the version of the MP to 6.0.6278.6)

If you test it again the diagnostic task will run correctly with the correct values of percentage free space and MB free space as shown in the screenshot.

Thanks to Kevin and Daniele for their research.
Best Regards
Tom

Working at a customer this week I had to implement a service map within SCSM based on a Distibuted Application created with SCOM 2007. This did not work at first! For some reason the objects would not sync. I checked the allow list in SCSM and added all the DA classes that are not in the list by default. Still no succes, the Service map remained empty after sync.

So after some time trying to figure out what was going wrong I discovered that when you configure the connector you first need to deselect all management packs and press OK. So you actually configure it back to not synchronize anytime. Then go back into the connector, hit the refresh button and now select all management packs and press OK again. For some reason, after this procedure the connector started syncing, This step has to be done everytime you add new managment packs to the connector!

Synchronizing started working for me now and my service map was filled with the correct objects. I tested this behaviour in my demo environment and the problem was the same. I checked this with SCSM 2010 SP1 and CU 3 installed. I cannot tell if this problem also exists in other versions of the product.