This monitor checks if the free disk space on SQL Server server is sufficient.
The SQL Server database instance supporting a Configuration Manager site server may have database files across multiple drives or on a single drive. The data contained in the database includes things such as application and package metadata, configuration item definitions, compliance results, and hardware and software inventory results for all clients supported by that Configuration Manager Site server.
Configuration Manager monitors the amount of free drive space across all of the drives configured to support its SQL Server database instance for the site server. Configuration Manager expects that the database minimum free disk space as configured by the Configuration Manager administrator (default thresholds: 5GB – critical; 10GB - warning) available to a site server’s SQL Server database instance exceeds the minimum configured thresholds.
The site system database server has stored more data taking up more physical disk space reducing the amount of minimum free disk space required to exceed the monitored thresholds (default thresholds: 5GB – critical; 10GB – warning).
The SQL Server database administrator needs to free up additional disk space by eliminating data in the temp DB files, shrinking database files, or allocating additional storage to the SQL Server database instance for this site. The SQL Server database administrator should work with the Configuration Manager administrator to determine the best course of action. Check the hman.log in the [Configuration Manager Installation folder]\Logs for further information.
| Target | MECM.SiteServer | ||
| Parent Monitor | System.Health.ConfigurationState | ||
| Category | ConfigurationHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | MECM.StatusMessage3State.MT | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="MECM.SQLDBSpace.StatusMessage.Monitor" Accessibility="Public" Enabled="true" Target="MECM.SiteServer" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="MECM.StatusMessage3State.MT" ConfirmDelivery="true">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="MECM.SQLDBSpace.StatusMessage.Monitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateIdff252e7667e34f9e9a9c6c2ac0652a1e" MonitorTypeStateID="Good" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateId7ae1bf0a4fa04a67bb7855e09a0c6f49" MonitorTypeStateID="Warning" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateId4daaf19c706d4fb7b8aeb5b4bc996ef3" MonitorTypeStateID="Error" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>
<ComponentName>SMS_HIERARCHY_MANAGER</ComponentName>
<RuleId>6FD0B53A-35DA-4da1-84C9-A9E1B6C12828</RuleId>
<IntervalSeconds>360</IntervalSeconds>
<MatchCount>3</MatchCount>
</Configuration>
</UnitMonitor>