Need to separate drive alerts with Logical Disk Free Space monitoring in SCOM 2012

I have an interesting need here to separate our SCOM alerts for Logical Disk Free space so that one alert is for OSSystem drives ONLY (C:/D:) and the other monitor alerts on all APP drives only (E:, etc). So far we have had great success using Kevin Holman's
blog post.
http://blogs.technet.com/b/kevinholman/archive/2009/11/24/writing-monitors-to-target-logical-or-physical-disks.aspx
We have overrides set so that the monitors report ONLY the percentage of free space left and ignores any MB threshold. So far so good, the alert comes in that host A reports low disk space on D: at 2.345...% free or host B reports low disk space on F: at
4.567...% free space etc. Now that we have our monitors working within the Windows Server classes Logical Disk, we need to set these monitors so that one is just for C or D drives with the alert named system Logical Disk Free Space OS Disk Warn and the other
monitor just reports on E - Z drives (excluding C or D) with the alert named Logical Disk Free Space APP Disk Warn.
We are very new to SCOM so I made the rookie mistake of creating a dynamic group for all Windows Server 2003 Logical Disk class that only includes Device Name = C or D. But found out too late you cant point a monitor to a group, it has to target a class.
And using the current monitors we set up with the above blog uses the correct logical disk class, but it doesnt care what instance (device Id = value), it will report low disk space on ANY logical drive. How in the world can we separate and exclude these monitors
so that one alerts only on OS disks (C and D) and the other only alerts on app disks (E through Z)?

Hi Kevsharp,
Quite confusing after reading your question.
So based on your requirement, What i understand is you need separate alerts for all the drives of the disk is running at low or out of space right ?
For the above just create a simple performance counter monitor and use the same counters as kevin has used in his blog.
Now Target: Use Windows server operating system (This will target all the Windows operating system agents in your SCOM. If the specified discovery MP's are installed).
Set a threshold Below 10% is critical or what ever. You will get the alerts in your console.
Gautam.75801

Similar Messages

Logical Disk Free Space Monitor - Slow to detect low free space

We are using the built in two trigger (MB and %) logical disk free space monitor in SCOM 2012 R2. We have setup overrides for MB warning and critical for both system and non-system drives and for a group containing disks we do not want monitored. The monitor
actually works fine, triggering an alert when both the MB and % free criteria are met. The problem is that it takes almost an hour for the initial alert to fire. After the initial alert, if I further fill the disk to push it from warning to critical, the alert
changes within the specifiec interval, which we have left at 15 minutes. The alert also clears using the 15 minute interval.
Has anyone else seen this behavior with this monitor? A disk monitor that takes an hour to fire is not going to be very useful.

I wanted to see for myself if there was anything else that I might be missing, so I opened up the Windows 2008 Logical Disk Free Space monitor XML and noticed that there is a NumSamples configuration that is set to 4. So, if the interval is 15 minutes, the
disk would have to exceed both threshold types for 4 consecutive intervals in order to change state and generate alert. This would be a minimum of 1 hour before an alert is raised with the default 15 minutes interval.
Unfortunately, NumSamples is not overrideable in the monitor type, which is too bad... The only way to get an alert sooner than one hour is to override interval. For example, if you want an alert within 20 minutes, override interval to 300 seconds (5 minutes).
Here is the code - see for yourself:
<UnitMonitor ID="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace" Accessibility="Public" Enabled="true" Target="Server2008!Microsoft.Windows.Server.2008.LogicalDisk" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.Server.2008.FreeSpace.Monitortype" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</AlertParameter1>
<AlertParameter2>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UnderWarningThresholds" MonitorTypeStateID="UnderWarningThresholds" HealthState="Success" />
<OperationalState ID="OverWarningUnderErrorThresholds" MonitorTypeStateID="OverWarningUnderErrorThresholds" HealthState="Warning" />
<OperationalState ID="OverErrorThresholds" MonitorTypeStateID="OverErrorThresholds" HealthState="Error" />
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<DiskLabel>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</DiskLabel>
<IntervalSeconds>900</IntervalSeconds>
<SystemDriveWarningMBytesThreshold>500</SystemDriveWarningMBytesThreshold>
<SystemDriveWarningPercentThreshold>10</SystemDriveWarningPercentThreshold>
<SystemDriveErrorMBytesThreshold>300</SystemDriveErrorMBytesThreshold>
<SystemDriveErrorPercentThreshold>5</SystemDriveErrorPercentThreshold>
<NonSystemDriveWarningMBytesThreshold>2000</NonSystemDriveWarningMBytesThreshold>
<NonSystemDriveWarningPercentThreshold>10</NonSystemDriveWarningPercentThreshold>
<NonSystemDriveErrorMBytesThreshold>1000</NonSystemDriveErrorMBytesThreshold>
<NonSystemDriveErrorPercentThreshold>5</NonSystemDriveErrorPercentThreshold>
<NumSamples>4</NumSamples>
</Configuration>
</UnitMonitor>
This proves 2 things:
1. Your testing proved that the monitor is working as designed - you got an alert in about an hour
2. This is a bad design at best, or a bug if you wish, as NumSamples should not be a hidden configuration - it should be exposed in override parameters in the console.
This should be fixed by Microsoft.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

Override Windows 2008 Logical Disk Free Space Monitor

HI all,
can I override this monitor on one concrete logical disk and concrete server ?
thanx
Falcon

find out the monitor
right click the monitor --> overrdies monitor --> speical object of logical disk
select the require hard disk e.g. c: and with path of your server name
Roger

Logical disk free space counters missing for server 2008 r2 and 2012 r2

I'm trying to get low disk space alerts for server 2008R2 and 2012 R2. While the monitors exist for 2008 and 2012 (Not-R2), they are missign for all R2 operating systems. Any idea how to either obtain these monitors, or create them so I can
get alerts for % disk free alerts?

What is your meaning of " monitors exist for 2008 and 2012 (Not-R2), they are missing for all R2 operating systems."? Does it means that the monitor is missing on all Windows 2008 R2 and Windows 2012 R2 machine or it just a blank circle ?
By default, Windows XXX Logical disk Free Space monitor is enable for all windows XXX. You may check whether an override to disable it. Moreover, Windows Server XXXX Logical Disk Free Space (%) Low and Windows Server 2008 Logical Disk Free Space (MB) Low
is disable by default and you should manually enable it.
Roger

SCOM 2007 R2 : Logical Disk Free Space : Did not Alert

Hello reader ,
I know this might be a repeated hearing for you. I have been sitting wit this issue for many hours now. I would like to understand where or what am I missing.
We have the default 'Logical Disk Space' Monitoring enabled for ALL servers in our environment. In one SQL server, non-system drive(E:) went beyond the warning(2000MB and 10%) and Critical (1000MB and 5%) Threshold.The total space allotted for the Drive
E: was 79GB. Now the total space left today morning was 698MB. But no alert was triggered.
I checked the following
If the health service watcher was available. - Yes it was.
If the Space really dropped to 698 - Yes it did. I verified from Performance Report.
I checked if there are any overrides - Nothing specific found.
In most of the blogs they said me to check if both criteria was successful - As shown above it is clearly matches.
Any idea why this alert was not fired ?
S.Arun Prasath HP ARDE TEAM

Thank you Agarwal ! To Answer your Question.
1) verify the monitor settings again.
=> I did this N number of times.
2) ensure there are no overrides
=> I did this too.
3) ensure that monitor properties are set for the correct Windows OS (same as that of the server).
=>What Do you mean here ?. I did not change any settings , it was there by default. No change was done at all.
4) also confirm that you do not have any other overrides on the two aggregate rollup monitors for "logical disk free space". These aggregate rollup monitors are just below the unit monitor in SCOM console.
=>Those Aggregate Rollup monitors are disabled. As we already have this unit monitor Enabled. There is no link to Aggregate monitor.
If all these settings are true, then can you try this. calculate the exact value in both % and MBytes according to your server, put the same values in your monitor through an override and repro the low disk space condition,. you should get an alert.
=> Not so easy to do this in prod. So will keep you posted when this is tested. Looks like this is the only way we can confirm if the alerts are sent.
S.Arun Prasath HP ARDE TEAM

How to make a proactive view of the Logical Disk Free Space

Hello,
I was wondering how I could make a view (preferably within a dashboard) that monitors the state of the Logical Disk Free Space values for one or more predefined groups. I can only get this to work with line diagrams but that is pretty hard to read.
I would like to make views like:
1) A simple state view that shows the state of the servers (or disks) in three state form (1. Healthy: 80% or lower; 2. Warning: Between 80% and 90%; 3. Alert: 90% or higher).
2) A view of actual percentages of the disk drives in a table form rather than the usual line diagram.
I prefer the first one the most and seems to be the easiest aswell but I can't seem to get this to work.
I hope that this is possible any like to know how to achieve this.
Thanks in advance,
Bram

Hi Bram,
I think you need to create a new dashboard view for this.
Make a new management pack for this.
Once you create a new management pack.
Go to monitoring TAB
Locate the management pack there and right click and select new Dashboard.
Create a summary view dashboard and then once it is created on the right hand side you will see something like
Performance (Which i edited as LDS report for last 24 hrs as per the screenshot)
Above that you will have a configure option. Click on it and mention the Object, counter and instance and of the LDS performance counter and mention the report duration (Last 1hr or 24 hrs )once you do this dashboard will start collecting the report
for you.
Once you scroll down the report you will get the list of servers in which space is low and how old is that alert
Below is the screenshot for your reference.
Gautam.75801

Windows Server 2012 Logical Disk Free Space (%) Low

I enabled the monitor "Windows Server 2012 Logical Disk Free Space (%) Low" and configured a low threshold to test. I started to get a bunch of warnings from servers, for example:
The disk \\?\Volume{ee0222ed-16de-40a5-af89-f95db3fdf5a4} on computer PC is running out of disk space. The value that exceeded the threshold is 11% free space.
Now I checked on the server, and all the disks have more than 11% free space. Additionally, I don't see any disks with such a name/guid.
When looking at the additional knowledge of the monitor, I see that it is using the following information:
Object Name: Logical Disk
Counter Name: PercentFree
My question is where is this disk coming from, and how can I avoid these disks from creating false alarms? When looking in the Windows Server
From my analyzing the DB, I see that these are the partitions on the server without a volume letter. Any way to avoid getting these discovered and/or alerts, without overriding each one?

Hi,
These "strange" disks are called mount points.
They get discovered by the "Mount Point Discovery Rule".
Go to your authoring => rules => search for the rule above and disable it.
If you want to remove all the instances in your environment you need to use Remove-SCOMDisabledClassInstance
powershell cmdlet.
More info on the cmdlet can be found here: http://technet.microsoft.com/en-us/library/hh920257%28v=sc.20%29.aspx
If you have any more questions please do not hesitate to ask
It's doing common things uncommonly well that brings succes. Check out my SCOM link blog:
SCOM link blog

How to enable Logical Disk Free Space

Hi
I have installed SCOM 2012R2 and configured monitoring for Windows 2012 R2 HyperV cluster. i think i configured most of the part but i could not able to see my logical disk free space.
I treid to enable In Monitors --> Windows Server 2012 Logical Disk --> "Logical Disk Free Space" but its grayed out.
can anyone tell me how to monitor my Logical Disk Free space and Physical Disk Free Space.
Here i attached the screenshot of my SCOM - Montiors
Regards
Kris
Kris

Thanks Gautam,
even i go through one by Monitors, i don't see any option to enable monitor. looks like its grayed out.
Regards
Kris
Kris

Logical disk free space is low.

Hello,
I am getting this alert "The disk on computer abc.com is running out of disk space. The values that exceeded the threshold are x% free space and "y" free Mbytes. Can any one clearly explain the issue and what is the proper resolution.
Thank you.

Hi,
this parameter is configured on your site properties (Administration \ Site Configuration \ Site).
It means that free space is missing on your server.
Proper resolution would be to modify the alert threshold or add some disk space.

Is there a matrix showing the difference with features of agent vs. agentless in SCOM 2012?

Is there a matrix showing the difference with features of agent vs. agentless in SCOM 2012?

Agent monitoring requires an agent installation on the target machine
Agentless monitoring
An agentless-managed computer is a Windows-based computer that is discovered by using the Operations console. You assign an management server or agent-managed computer to provide remote (proxy) agent functionality for the computers.
Agentless-managed computers are managed as if there is an agent installed on them. Not all management packs work in agentless mode.
Agentless versus Agent-based server monitoring
http://thwack.solarwinds.com/community/solarwinds-community/geek-speak_tht/blog/2013/02/11/agentless-versus-agent-based-server-monitoring
Roger

SCOM does not generate alert for logical disk space

Hi,
Today we noticed that one of agent in SCOM has drive space below 5% and 500 MB but SCOM did not generate any alert.
I have also verified that there is no override set for this agent's logical disks. I have also verified that discovery is able to discover all disks on server but monitoring is not working as expected.
I have flushed health service on agent but it didn't help.
When I gone through event logs on agent, I found below events:
Log Name:      Operations Manager
Source:        HealthService
Date:          5/26/2014 5:13:05 AM
Event ID:      1103
Description:
Summary: 6 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "XXXXXXXX".
This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).
Log Name:      Operations Manager
Source:        HealthService
Date:          5/26/2014 5:14:21 AM
Event ID:      1206
Task Category: Health Service
Description:
Rule/Monitor "Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace", running for instance "F:" with id:"{36ED7395-3798-A361-5017-327F6FA50030}" failed,
got unloaded and reached the failure limit that prevents automatic reload. Management group "XXXXXXXXX".
Please let me if what we need to do here.
Thanks.

Do this
Change startup type to Window Management Instrumentation (WMI) Service to disabled
Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
Open a CMD Prompt with elevated privileges
CD windows\system32\wbem
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
Set the WMI Service type back to Automatic and start WMI Service
cd /d c:\ ((go to the root of the c drive, this is important))
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s
Reboot the server
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway

Need help with the "Erase Free Space" disk utility

When I use Disk Utilities to Erase Free Space (I use the single zero mode) I get a message telling me,
"Your Startup Disk is almost Full,
you need to make more space available
on your startup disk by deleting files."
This occurs about 90% of the way through the process (based on where the blue bar is at the time) during the "Creating Temporary File" portion of the process. I know from past experience that I will remain in this portion of the process forever unless I press the "Skip" button to complete the process.
My questions,
1. What is the startup disk and why is it full?
2. What should I do about the Your Startup Disk is Almost Full warning?
3. Is my computer actually talking about "regular" disk space (I currently have about 9GB of 80GB free but have seen this warning with 30GB available as well).
4. When I press "Skip" and the blue bar continues to complete the process, have I actually erased free space?
PBG4 15" 80GB HD 1GB RAM Mac OS X (10.4)

The Disk Utility does the erase by creating large temporary files, writing to them, then deleting them. While doing this, OSX may notice the lack of free space on the disk. This is normal, but could cause problems if you are also running some applications that want some disk space. If you let if finish, it should delete the temporary files and free the disk space.
I prefer to run the Disk Utility from the Tiger install disk when doing a Verify, Repair, or Erase Free Space on my boot disk, so I know I won't be interfering with anything running.

Aperture: "Insufficient Disk Space" alert with 370 GB Free

Hello,
Since I use aperture on Mountain Lion, it's unpossible to import big folders anymore.
The folders named "2012" is on my network and has 7 400 files (560 GB). I import it with option "In Their Current Location", so, it's no copy nor move. After checking, computer says : Insufficient Disk Space. Need 100 GB more". But HD is 370 GB free and pictures aren't copied/moved to my HD !!!
With snow leopard, I don't have this prob, but Aperture update are no more available for SL.
I work on a IMac with 4GB RAM and HD 500 GB with a Mac Server of 15 TB.
Any suggestion ?
Etienne
Aperture 3.4.3 on Mountain Lion 10.8.2

Ernie,
1) Aperture library is on the internal HD with 370 GB Free. FS is Mac OS Extended (Journaled). The linked picture stays on a Mac Network fileserver with afolder per year. I make test with folder 2011 and folder 2012
2) With LR, I don't import library from aperture but I import picture from folder 2012. And it's fine. LR library stays on the same HD/same partition than Aperture one.
3) If I remove big TIFF file (273 MB) from 2012, it's OK.
4) If I try to import 100 big TIFF File it's NOK : "Insuffisant disk space..."
5) If I try to import 10 big TIFF File it's OK to import but zoom 1:1 gives a little picture.
Etienne

ProTool Digi 003 new driver issues with Logic

I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.

I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.

Logical disk availability monitor on SCOM 2012 r2

Hi Team,
Please let me know in which management pack has the rule or monitor for logical disk availability. We need to monitor HP physical disk ( c:\ or D:\ Logical disk) availability.

Hi,
System Center Management Pack for Windows Server Operating System
http://www.microsoft.com/en-us/download/details.aspx?id=9296
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Need to separate drive alerts with Logical Disk Free Space monitoring in SCOM 2012

Similar Messages

Maybe you are looking for