| | DisplayName | Description | ID | Target | Parent Monitor | Category | Enabled | Instance Name | Counter Name | Frequency | Alert Generate | Alert Severity | Alert Priority | Alert Auto Resolve | Monitor Type | Remotable | Accessibility | RunAs |
|---|
 | Backup restoration failed | Maintaining a backup of the Dynamic Host Configuration Protocol (DHCP) database protects you from data loss in the event of data corruption or a hard disk failure. There are three backup methods supported by the DHCP Server service: - Synchronous backups that occur automatically. The default backup interval is 60 minutes. - Asynchronous (manual) backups, performed by using the Backup command in the DHCP snap-in. - Backups using Windows Backup (Ntbackup.exe) or other backup software. When a synchronous or asynchronous backup occurs, the entire DHCP database is saved. | Microsoft.Windows.2008R2.DHCP.Server.Database.Monitor.BackupRestore.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType | True | Public | |
| DHCP backup failed | Maintaining a backup of the Dynamic Host Configuration Protocol (DHCP) database protects you from data loss in the event of data corruption or a hard disk failure. There are three backup methods supported by the DHCP Server service: - Synchronous backups that occur automatically. The default backup interval is 60 minutes. - Asynchronous (manual) backups, performed by using the Backup command in the DHCP snap-in. - Backups using Windows Backup (Ntbackup.exe) or other backup software. When a synchronous or asynchronous backup occurs, the entire DHCP database is saved. | Microsoft.Windows.2008R2.DHCP.Server.Database.Monitor.BackupRestore.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Versioning mismatch of DHCP and its database | Database migration allows you to migrate or convert previous versions of the Dynamic Host Configuration Protocol (DHCP) database to the DHCP in current or latest version of Windows operating system. | Microsoft.Windows.2008R2.DHCP.Server.Database.Monitor.DatabaseCorrupt | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP database corrupted | Database integrity refers to the ability of the Dynamic Host Configuration Protocol (DHCP) database to function properly, maintaining an uncorrupted state. | Microsoft.Windows.2008R2.DHCP.Server.Database.Monitor.DBIntegrity | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | True | Public | |
| Mismatch of DHCP and its database | Database migration allows you to migrate or convert previous versions of the Dynamic Host Configuration Protocol (DHCP) database to the DHCP in current or latest version of Windows operating system. | Microsoft.Windows.2008R2.DHCP.Server.Database.Monitor.Migration.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Unable to establish AD authorization | For proper authorization and operation, the Dynamic Host Configuration Protocol (DHCP) server relies on a valid Active Directory Domain Services configuration. The DHCP server must find a valid directory services-enabled domain controller. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.AD | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Unable to access the audit log file path | Dynamic Host Configuration Protocol (DHCP) servers include several logging features and server parameters that provide enhanced auditing capabilities. You can specify the following features:
- The file path in which the DHCP server stores audit log files.
- A maximum size restriction (in megabytes) for the total amount of disk space available for all audit log files created and stored by the DHCP service.
- An interval for disk checking that is used to determine how many times the DHCP server writes audit log events to the log file before checking for available disk space on the server.
- A minimum size requirement (in megabytes) for server disk space that is used during disk checking to determine if sufficient space exists for the server to continue audit logging. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.Auditing.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Unable to access the audit log file path for DHCP | Dynamic Host Configuration Protocol (DHCP) servers include several logging features and server parameters that provide enhanced auditing capabilities. You can specify the following features:
- The file path in which the DHCP server stores audit log files.
- A maximum size restriction
- An interval for disk checking
- A minimum size requirement | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.Auditing.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Unable to access the audit log file | Dynamic Host Configuration Protocol (DHCP) servers include several logging features and server parameters that provide enhanced auditing capabilities. You can specify the following features:
- The file path in which the DHCP server stores audit log files.
- A maximum size restriction
- An interval for disk checking
- A minimum size requirement | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.Auditing.3 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP server is not authorized in AD | When configured correctly and authorized for use on a network, Dynamic Host Configuration Protocol (DHCP) servers provide a useful administrative service. However, a misconfigured or unauthorized DHCP server can cause problems. For example, if an unauthorized DHCP server starts, it might begin either leasing incorrect IP addresses to clients or negatively acknowledging DHCP clients that attempt to renew current IP address leases. To resolve these issues, DHCP servers are verified as authorized in Active Directory Domain Services before they can service clients. This prevents most of the accidental damage caused by either misconfigured DHCP servers or correctly configured DHCP servers running on the wrong network. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.AuthorizationAndConflicts | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | True | Public | |
| Unable to restore the registry | Maintaining a backup of the Dynamic Host Configuration Protocol (DHCP) database protects you from data loss in the event of data corruption or a hard disk failure. There are three backup methods supported by the DHCP Server service: - Synchronous backups that occur automatically. The default backup interval is 60 minutes. - Asynchronous (manual) backups, performed by using the Backup command in the DHCP snap-in. - Backups using Windows Backup (Ntbackup.exe) or other backup software. When a synchronous or asynchronous backup occurs, the entire DHCP database is saved. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.Backup | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType | True | Public | |
| Incorrect BOOTP configuration | The Bootstrap Protocol (BOOTP) is a host configuration protocol developed before Dynamic Host Configuration Protocol (DHCP). DHCP improves on BOOTP and resolves its limitations as a host configuration service. To configure your DHCP server to assign Internet Protocol (IP) address information to BOOTP clients, you must add a reservation for each BOOTP client. The reservation builds an association between the media access control (MAC) address and the IP address. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.BOOTPFileConfig | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Communication was interrupted between critical network infrastructure components | For proper network communication between the Dynamic Host Configuration Protocol (DHCP) server and other network services, such as Active Directory Domain Services and Winsock, the DHCP server must have a working network connection. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.Communications | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType | True | Public | |
| DHCP Server service does not have a static IP address | The DHCP server interface and bindings must be configured correctly. The correct configuration of a static interface is required. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.DHCPServiceBoundToStaticIP | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DNS Registration issues | You can configure the Dynamic Host Configuration Protocol (DHCP) Server service to impersonate an account to perform Domain Name service (DNS) registrations and secure dynamic updates. The Netsh.exe tool can be used to configure the impersonation credentials. You must create a dedicated user account in Active Directory Domain Services before you use the Netsh.exe tool to configure the use of impersonation credentials. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.DNSRegistration | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DLL exception has occurred | General availability of the Dynamic Host Configuration Protocol (DHCP) server refers to its ability to service clients. General availability depends on: - Proper authorization of the DHCP server - Presence of Active Directory Domain Services - Successful loading of the DHCP dynamic-link libraries (DLLs) | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.GeneralAvailability.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DLL exception occurred or the DHCP server is unable to access AD | General availability of the Dynamic Host Configuration Protocol (DHCP) server refers to its ability to service clients. General availability depends on: - Proper authorization of the DHCP server - Presence of Active Directory Domain Services - Successful loading of the DHCP dynamic-link libraries (DLLs) | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.GeneralAvailability.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DLL exception occurred or the DHCP server is unable to access AD | General availability of the Dynamic Host Configuration Protocol (DHCP) server refers to its ability to service clients. General availability depends on: - Proper authorization of the DHCP server - Presence of Active Directory Domain Services - Successful loading of the DHCP dynamic-link libraries (DLLs) | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.GeneralAvailability.3 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | True | Public | |
| Configuration issues of DHCP security groups | To function properly, the Dynamic Host Configuration Protocol (DHCP) service must be able to create or look up the DHCP Users and DHCP Administrators local groups. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.GroupConfig | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Interface change not recognized | When the network interfaces or Internet Protocol (IP) addresses with which the Dynamic Host Configuration Protocol (DHCP) server is configured are changed, the server might not recognize these changes, and the interfaces might not function correctly. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.InterfaceNotificationFailed | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | Custom | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Unable to ping client for lease issuance | Internet Protocol (IP) addresses are leased by the Dynamic Host Configuration Protocol (DHCP) server to its clients. Each lease has an expiration date, which the client must renew if it is going to continue to use that IP address. If conflict detection is enabled, the DHCP server pings the client before assigning the IP address to determine whether an IP address is already in use on the network. If the DHCP client cannot be pinged by the server, the server assumes no IP address conflict and assigns the IP address to the client. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.LeaseIssuance | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Rogue DHCP Server was detected on the network | When configured correctly and authorized for use on a network, Dynamic Host Configuration Protocol (DHCP) servers provide a useful administrative service. However, a misconfigured or unauthorized DHCP server can cause problems. For example, if an unauthorized DHCP server starts, it might begin either leasing incorrect IP addresses to clients or negatively acknowledging DHCP clients that attempt to renew current address leases. To resolve these issues, DHCP servers are verified as authorized in Active Directory Domain Services before they can service clients and unauthorized, or rogue, servers are detected. This prevents most of the accidental damage caused by either misconfigured DHCP servers or correctly configured DHCP servers running on the wrong network. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.RogueDetection.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | True | Public | |
| Network connectivity was interrupted by a rogue DHCP Server | When configured correctly and authorized for use on a network, Dynamic Host Configuration Protocol (DHCP) servers provide a useful administrative service. However, a misconfigured or unauthorized DHCP server can cause problems. For example, if an unauthorized DHCP server starts, it might begin either leasing incorrect IP addresses to clients or negatively acknowledging DHCP clients that attempt to renew current address leases. To resolve these issues, DHCP servers are verified as authorized in Active Directory Domain Services before they can service clients and unauthorized, or rogue, servers are detected. This prevents most of the accidental damage caused by either misconfigured DHCP servers or correctly configured DHCP servers running on the wrong network. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.RogueDetection.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DHCP Server service failed to initialize properly | When the Dynamic Host Configuration Protocol (DHCP) Server service initializes, it checks for proper configuration of Transmission Control Protocol/Internet Protocol (TCP/IP), including the presence of a static IP address. Successful initialization results when the DHCP server has established network communication by using TCP/IP. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.ServiceInitialization.1 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP Server service failed to initialize properly | When the Dynamic Host Configuration Protocol (DHCP) Server service initializes, it checks for proper configuration of Transmission Control Protocol/Internet Protocol (TCP/IP), including the presence of a static IP address. Successful initialization results when the DHCP server has established network communication by using TCP/IP. | Microsoft.Windows.2008R2.DHCP.Server.IPv4Runtime.Monitor.ServiceInitialization.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Unable to access the audit log file path for DHCPv6 | Dynamic Host Configuration Protocol version 6 (DHCPv6) servers include several logging features and server parameters that provide enhanced auditing capabilities. You might need to configure log settings to prevent the log from filling up or to give the server permissions to write to the log. You can configure the following properties to keep your DHCP server logs healthy:
- The audit log file path
- A maximum size restriction
- An interval for disk checking
- A minimum size requirement | Microsoft.Windows.2008R2.DHCP.Server.IPv6Runtime.Monitor.Auditing | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.SecurityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP server failed to initialize properly | The Dynamic Host Configuration Protocol version 6 (DHCPv6) Server service is a process that runs in the background on a computer running Windows Server and that provides Internet Protocol version 6 (IPv6) addresses to clients. Dynamic Host Configuration Protocol (DHCP) can lease both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) addresses. If IPv6 is not available, the DHCP service uses IPv4 only. | Microsoft.Windows.2008R2.DHCP.Server.IPv6Runtime.Monitor.DatabaseCorrupt | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCPv6 server failed to initialize properly | The DHCPv6 server failed its initialization. | Microsoft.Windows.2008R2.DHCP.Server.IPv6Runtime.Monitor.InitializationFailed | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| One or more DHCPv6 Server service components failed to initialize properly | The Dynamic Host Configuration Protocol version 6 (DHCPv6) Server service is a process that runs in the background on a computer running Windows Server and that provides Internet Protocol version 6 (IPv6) addresses to clients. Dynamic Host Configuration Protocol (DHCP) can lease both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) addresses. If IPv6 is not available, the DHCP service uses IPv4 only. | Microsoft.Windows.2008R2.DHCP.Server.IPv6Runtime.Monitor.StaticIPAssigned | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCPv6 scope has reached its capacity | Internet Protocol v6 (IPv6) addresses are leased by the Dynamic Host Configuration Protocol IPv6 (DHCPv6) server to its clients. Each lease has an expiration date, which the client must renew if it is going to continue to use that IPv6 address. The DHCPv6 server cannot issue leases to clients if the number of available IP addresses in the scope is insufficient. | Microsoft.Windows.2008R2.DHCP.Server.IPv6Scope.Monitor.ScopeFull | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType | True | Public | |
| DHCP Server configuration change monitoring - Activity Logging | DHCP activity logging allows Administrators to monitor DHCP Server configuration changes. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.ActivityLogging | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP Scope delay is not configured correctly | Split-scope configuration with delay employs a secondary DHCP server with a time delay that is configured in its scope properties. The time delay on the secondary DHCP server causes it to respond with a delay to DHCP DISCOVER requests from DHCP clients, enabling the primary DHCP server to respond to and accept the DHCPOFFER first. This feature is available only for IPv4 network and not for IPv6 network as in case of latter exhaustion of addresses is not an issue. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.DelayOffer | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP Service Running Monitor | The DHCP service is not servicing any clients because none of the active network interfaces have statically configured IP addresses, or there are no active interfaces. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.DHCPServiceRunning | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.CheckNTServiceStateMonitorType | True | Public | |
| Link Layer Based Filtering is not configured correctly | Link layer filtering provides network access control for the issuance or denial of DHCP leases of IP addresses based on a media access control (MAC) address. Link layer filtering can be configured at the IPv4 node for all clients across all IPv4 scopes. This feature is currently available only for IPv4 networks. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.LinkLayerFiltering | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Name Protection is not configured correctly | The use of name protection in Windows Server prevents name squatting by non-Windows-based computers in the network. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.NameProtection | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP Server is not configured correctly | An invalid alternate DNS server address or port binding is preventing the DHCP server from leasing to clients. | Microsoft.Windows.2008R2.DHCP.Server.Monitor.System | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | EventCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP server is unable to communicate with an NPS server | Network Access Protection (NAP) is a health policy creation, enforcement, and remediation technology that is included in Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2. With NAP, system administrators can enforce health requirements, which can include software requirements, security update requirements, required computer configurations, and other settings. Dynamic Host Configuration Protocol (DHCP) enforcement includes a DHCP NAP enforcement server component and a DHCP NAP enforcement client component. By using DHCP enforcement, DHCP servers can enforce health policy requirements any time a computer attempts to lease or renew an IP address configuration on the network. DHCP enforcement is the easiest enforcement to deploy because all DHCP client computers must lease IP addresses. DHCP NAP requires proper NPS/RADIUS configuration. | Microsoft.Windows.2008R2.DHCP.Server.NAP.Monitor.NPSConnectivity | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Dependent service failed to start correctly | The Dynamic Host Configuration Protocol (DHCP) Server service is a process that runs in the background on a computer running Windows Server and provides IP addresses to clients. The Dynamic Host Configuration Protocol (DHCP) Server service is dependent on these services: Service Controller Global parameters initialization Registry parameters initialization RPC server start Winsock data initialization The failure of any of these services to initialize or start can cause the DHCP Server service to fail. | Microsoft.Windows.2008R2.DHCP.Server.Role.Monitor.DependentServiceHealth | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | AvailabilityHealth | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | True | Public | |
| DHCPv6 Server service failed to initialize properly | The Dynamic Host Configuration Protocol version 6 (DHCPv6) Server service is a process that runs in the background on a computer running Windows Server and that provides Internet Protocol version 6 (IPv6) addresses to clients. Dynamic Host Configuration Protocol (DHCP) can lease both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) addresses. If IPv6 is not available, the DHCP service uses IPv4 only. | Microsoft.Windows.2008R2.DHCP.Server.Role.Monitor.ServiceInitialized | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| BOOTP scope has reached its capacity | The Bootstrap Protocol (BOOTP) is a host configuration protocol developed before Dynamic Host Configuration Protocol (DHCP). DHCP improves on BOOTP and resolves its limitations as a host configuration service. The BOOTP service can request Internet Protocol (IP) addresses for BOOTP clients from the DHCP server. If the DHCP server cannot provide IP addresses, the BOOTP service might not function correctly. | Microsoft.Windows.2008R2.DHCP.Server.Scope.Monitor.BOOTPScopeFull | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP scope for IPv4 addresses has reached its capacity | Internet Protocol (IP) addresses are leased by the Dynamic Host Configuration Protocol (DHCP) server to its clients. Each lease has an expiration date, which the client must renew if it is going to continue to use that IP address. The DHCP server cannot issue leases to clients if the number of available IP addresses in the scope is insufficient. | Microsoft.Windows.2008R2.DHCP.Server.Scope.Monitor.LeaseAvailability.2 | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.AvailabilityState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DHCP database contains orphaned entries | Before Dynamic Host Configuration Protocol (DHCP) clients can use a DHCP server for dynamic Transmission Control Protocol/Internet Protocol (TCP/IP) configuration, you must define and activate scopes for your DHCP clients. A scope is the full, consecutive range of possible Internet Protocol (IP) addresses for a subnet. The IP addresses in a scope defines a single subnet on which DHCP services are offered. DHCP servers use scopes to manage network IP address distribution and the configuration of DHCP options. | Microsoft.Windows.2008R2.DHCP.Server.Scope.Monitor.OrphanedEntry | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DHCP client used an unknown option | Dynamic Host Configuration Protocol (DHCP) uses options to pass additional Internet Protocol (IP) settings to DHCP clients on a network. Examples of DHCP options include:
- The default gateway IP address
- The Domain Name System (DNS) server IP address
- The DNS domain name
You can configure options for an entire server, a scope, or for a single reserved client. If the server does not recognize the options sent by the client, it ignores the options. | Microsoft.Windows.2008R2.DHCP.Server.Scope.Monitor.UnknownScopeOption | Microsoft.Windows.2008R2.DHCP.Server.Role | System.Health.ConfigurationState | StateCollection | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
Home