DHCP Scope(s) < 5 IP Addresses
Purpose
This solution automates the evaluation of a DHCP health check script’s output, determining whether any scope has fewer than 5 free IPs. When an issue is detected, it automatically triggers the creation of a support ticket with all relevant scope details to enable rapid remediation.
Associated Content
| Content | Type | Function |
|---|---|---|
| DHCP Scope(s) < 5 IP Addresses | Automation | Monitors DHCP scopes and triggers the workflow when any DHCP scope has fewer than 5 available IP addresses remaining. |
| DHCP Scopes IP Alerts | Ticket Template | Creates a ConnectWise Manage ticket when a DHCP scope is detected with fewer than 5 available IP addresses. |
| Compound Condition - DHCP Scope Alert | Compound Condition | Evaluates the task output and determines whether the automation should generate an alert based on the remaining available IP addresses in the DHCP scope. |
Implementation
- Create the automation DHCP Scope(s) < 5 IP Addresses.
- Create the Compound condition DHCP Scope Alert.
- Create the ticket template CW Manage - DHCP Scopes IP Alerts.
Dependencies
FAQ
Q1. What does this solution monitor?
This solution monitors DHCP scopes on Windows DHCP servers and generates an alert when any scope has fewer than 5 available IP addresses remaining.
Q2. What happens when a DHCP scope falls below the threshold?
The automation creates a ConnectWise Manage ticket to notify technicians that the DHCP scope is running low on available IP addresses.
Q3. Which devices should this automation be deployed to?
This automation should be deployed only to Windows servers hosting the DHCP Server role.
Q4. Can I change the threshold from 5 available IP addresses?
No. The threshold is set to 5 available IP addresses by default and is not intended to be modified in this implementation.
Q5. Does this solution make any changes to the DHCP configuration?
No. This solution is monitoring-only. It does not modify DHCP scopes or settings; it only detects low IP availability and generates an alert.
Changelog
2025-07-29
- Initial version of the document