I like the Managed Availability and the “self healing” aspect of Exchange 2013.
But about SpaceMonitorLowSpaceThresholdInMB is nothing about to read.
If you check your serverhealt with:
get-serverhealth -identity servername -HealthSet Diskspace | ? AlertValue -ne unHealthy | ft -autosize
You can get lots of Databases which are in an unhealthy state because the LowLogVolumeSpaceMonitor is configured to check if you have 200 GB of free space. That would be an great idea, if you have a large organization and you have lots of disks whith a huge amount of free space. But in smaller company it would be great to change this value.
With Exchange 2013 SP1 you should now be able to configure this. Go to all of your Mailbox Servers and in regedit go to the following path:
HKLM\Software\Microsoft\ExchangeServer\v15\ActiveMonitoring\Parameters
If you have an DWORD called SpaceMonitorLowSpaceThresholdInMB then you’re lucky. If not, create a DWORD with the name and then you can change it to an Value which suits you more. But, as the dword is mentioning, its in MB not GB 😉
Updated 15-03-2015
No Reg Setting but Add-GlobalMonitoringOverride is better!!
SpaceMonitorLowSpaceThresholdInMB.ps1
write-host = “Default 175GB CU7”
$diskspace = Read-Host ‘What is the Minimum Free Disk Space in MB?’
Add-GlobalMonitoringOverride -Item Monitor –Identity MailboxSpace\StorageLogicalDriveSpaceMonitor -PropertyName MonitoringThreshold -PropertyValue $diskspace