Microsoft-Windows-DHCP-Server
Event ID 70: [DHCPv4.ScopeConfigured] Scope: %1 for IPv4 is Configured by %2.
#Description
Scope: for IPv4 is Configured by .
References #
Event ID 70: Scope: IP_ScopeName for IPv4 is Configured by ClientName.
#Event ID 71: [DHCPv4.ScopeModified] Scope: %1 for IPv4 is Modified by %2.
#Description
Scope: for IPv4 is Modified by .
References #
Event ID 71: Scope: IP_ScopeName for IPv4 is Modified by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 71,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:20.3312105+00:00",
"event_record_id": 6,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is Modified by ludus\\domainadmin."
}
References #
Event ID 72: [DHCPv4.ScopeDeleted] Scope: %1 for IPv4 is Deleted by %2.
#Description
Scope: for IPv4 is Deleted by .
References #
Event ID 72: Scope: IP_ScopeName for IPv4 is Deleted by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 72,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-06-13T15:13:20.2120411+00:00",
"event_record_id": 18,
"correlation": {},
"execution": {
"process_id": 1168,
"thread_id": 2660
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "telemetry-DC-d.cell-d.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.99.0]evtgen-scope]",
"ClientName": "cell-d\\domainadmin"
},
"message": "Scope: [[10.99.99.0]evtgen-scope] for IPv4 is Deleted by cell-d\\domainadmin."
}
References #
Event ID 73: [DHCPv4.ScopeActivated] Scope: %1 for IPv4 is Activated by %2.
#Description
Scope: for IPv4 is Activated by .
References #
Event ID 73: Scope: IP_ScopeName for IPv4 is Activated by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 73,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.5138375+00:00",
"event_record_id": 42,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.88.1.0]det-tiny]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.88.1.0]det-tiny] for IPv4 is Activated by ludus\\domainadmin."
}
References #
Event ID 74: [DHCPv4.ScopeDeActivated] Scope: %1 for IPv4 is Deactivated by %2.
#Description
Scope: for IPv4 is DeActivated by .
References #
Event ID 74: Scope: IP_ScopeName for IPv4 is DeActivated by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 74,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:20.2902875+00:00",
"event_record_id": 4,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is DeActivated by ludus\\domainadmin."
}
References #
Event ID 75: [DHCPv4.ScopeLeaseUpdate] Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds.
#Description
Scope: for IPv4 is Updated with Lease Duration: seconds by . The previous configured Lease Duration was: seconds.
References #
Event ID 75: Scope: IP_ScopeName for IPv4 is Updated with Lease Duration: ModifiedDuration seconds by ClientName.
#Description
Scope: IP_ScopeName for IPv4 is Updated with Lease Duration: ModifiedDuration seconds by ClientName. The previous configured Lease Duration was: OriginalDuration seconds.
Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ModifiedDuration UnicodeString | |
ClientName UnicodeString | |
OriginalDuration UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 75,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.5090954+00:00",
"event_record_id": 41,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.88.1.0]det-tiny]",
"ModifiedDuration": "691200",
"ClientName": "ludus\\domainadmin",
"OriginalDuration": "0"
},
"message": "Scope: [[10.88.1.0]det-tiny] for IPv4 is Updated with Lease Duration: 691200 seconds by ludus\\domainadmin. The previous configured Lease Duration was: 0 seconds."
}
References #
Event ID 76: [DHCPv4.ScopeOptionUpdate] Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3
#Description
Scope: for IPv4 is Updated with Option Settings: by.
References #
Event ID 76: Scope: IP_ScopeName for IPv4 is Updated with Option Settings: OptionName by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
OptionName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 76,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:20.4113131+00:00",
"event_record_id": 9,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"OptionName": "[3 - Router]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is Updated with Option Settings: [3 - Router] by ludus\\domainadmin"
}
References #
Event ID 77: [DHCPv4.ScopeDNSEnable] Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.
#Description
Scope: for IPv4 is Enabled for DNS Dynamic updates by .
References #
Event ID 77: Scope: IP_ScopeName for IPv4 is Enabled for DNS Dynamic updates by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 77,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.5383944+00:00",
"event_record_id": 10,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is Enabled for DNS Dynamic updates by ludus\\domainadmin."
}
References #
Event ID 78: [DHCPv4.ScopeDNSDisable] Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.
#Description
Scope: for IPv4 is Disabled for DNS Dynamic updates by .
References #
Event ID 78: Scope: IP_ScopeName for IPv4 is Disabled for DNS Dynamic updates by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 78,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.7037131+00:00",
"event_record_id": 12,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is Disabled for DNS Dynamic updates by ludus\\domainadmin."
}
References #
Event ID 79: [DHCPv4.ScopeDNSUpdate_Req_by_Client] Scope: %1 for IPv4 is Updated with DNS Settings by %2: to dynamically update DNS A and PTR records on request by the DHCP Clients.
#Description
Scope: for IPv4 is Updated with DNS Settings by : to dynamically update DNS A and PTR records on request by the DHCP Clients .
References #
Event ID 79: Scope: IP_ScopeName for IPv4 is Updated with DNS Settings by ClientName: to dynamically update DNS A and PTR records on request by the DHCP Clients .
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 79,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.6518415+00:00",
"event_record_id": 11,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.99.7.0]detwiki-v4] for IPv4 is Updated with DNS Settings by ludus\\domainadmin: to dynamically update DNS A and PTR records on request by the DHCP Clients ."
}
References #
Event ID 80: [DHCPv4.ScopeDNSUpdate_Always] Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records.
#Description
Scope: for IPv4 is Updated with DNS Settings by : to always dynamically update DNS A and PTR records.
References #
Event ID 80: Scope: IP_ScopeName for IPv4 is Updated with DNS Settings by ClientName: to always dynamically update DNS A and PTR records.
#Event ID 81: [DHCPv4.ScopeDNSEnable_Discard] Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.
#Description
Scope: for IPv4 is Enabled for DNS Settings by : to discard DNS A and PTR records when lease is deleted.
References #
Event ID 81: Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.
#Event ID 82: [DHCPv4.ScopeDNSDisable_Discard] Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.
#Description
Scope: for IPv4 is Disabled for DNS Settings by : to discard DNS A and PTR records when lease is deleted.
References #
Event ID 82: Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.
#Event ID 83: [DHCPv4.ScopeDNSEnable_Update_Client_NoReq] Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that don't request updates.
#Description
Scope: for IPv4 is Enabled for DNS Settings by : to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
References #
Event ID 83: Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
#Event ID 84: [DHCPv4.ScopeDNSDisable_Update_Client_NoReq] Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that don't request updates.
#Description
Scope: for IPv4 is Disabled for DNS Settings by : to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
References #
Event ID 84: Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
#Event ID 85: [DHCPv4.ScopePBA_DeActivated] Policy based assignment has been disabled for scope %1.
#Description
Policy based assignment has been disabled for scope .
References #
Event ID 85: Policy based assignment has been disabled for scope IP_ScopeName.
#Event ID 86: [DHCPv4.ScopePBA_Activated] Policy based assignment has been enabled for scope %1.
#Description
Policy based assignment has been enabled for scope .
References #
Event ID 86: Policy based assignment has been enabled for scope IP_ScopeName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 86,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.5066296+00:00",
"event_record_id": 40,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.88.1.0]det-tiny]"
},
"message": "Policy based assignment has been enabled for scope [[10.88.1.0]det-tiny]."
}
References #
Event ID 87: [DHCPv4.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.
#Description
Name Protection setting is Enabled on Scope: for IPv4 by .
References #
Event ID 87: Name Protection setting is Enabled on Scope: IP_Name for IPv4 by ClientName.
#Event ID 88: [DHCPv4.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.
#Description
Name Protection setting is Disabled on Scope: for IPv4 by .
References #
Event ID 88: Name Protection setting is Disabled on Scope: IP_Name for IPv4 by ClientName.
#Event ID 89: [DHCPv4.ScopeSupportType] Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.
#Description
Scope: for IPv4 is Updated with support type: by . The previous configured state was: .
References #
Event ID 89: Scope: IP_Name for IPv4 is Updated with support type: ModifiedSupportType by ClientName.
#Description
Scope: IP_Name for IPv4 is Updated with support type: ModifiedSupportType by ClientName. The previous configured state was: OriginalSupportType.
Message #
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
ModifiedSupportType UnicodeString | |
ClientName UnicodeString | |
OriginalSupportType UnicodeString |
References #
Event ID 90: [DHCPv4.ScopeNAPEnabled] NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.
#Description
NAP Enforcement is Enabled on Scope: for IPv4 by .
References #
Event ID 90: NAP Enforcement is Enabled on Scope: IP_ScopeName for IPv4 by ClientName.
#Event ID 91: [DHCPv4.ScopeNAPDisabled] NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.
#Description
NAP Enforcement is Disabled on Scope: for IPv4 by .
References #
Event ID 91: NAP Enforcement is Disabled on Scope: IP_ScopeName for IPv4 by ClientName.
#Event ID 92: [DHCPv4.ScopeNAPProfileConfigured] NAP Profile is configured on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3.
#Description
NAP Profile is configured on Scope: for IPv4 with the following NAP Profile: by .
References #
Event ID 92: NAP Profile is configured on Scope: IP_ScopeName for IPv4 with the following NAP Profile: NAP_ProfileName by ClientName.
#Event ID 93: [DHCPv4.ScopeNAPProfileModified] NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4.
#Description
NAP Profile is Updated on Scope: for IPv4 with the following NAP Profile: by . The previous configured NAP Profile was: .
References #
Event ID 93: NAP Profile is Updated on Scope: IP_ScopeName for IPv4 with the following NAP Profile: NAP_ModifiedProfileName by ClientName.
#Description
NAP Profile is Updated on Scope: IP_ScopeName for IPv4 with the following NAP Profile: NAP_ModifiedProfileName by ClientName. The previous configured NAP Profile was: NAP_OriginalProfileName.
Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
NAP_ModifiedProfileName UnicodeString | |
ClientName UnicodeString | |
NAP_OriginalProfileName UnicodeString |
References #
Event ID 94: [DHCPv4.ScopeNAPProfileDeleted] The following NAP Profile: %1 is deleted on Scope: %2 by %3.
#Description
The following NAP Profile: is deleted on Scope: by .
References #
Event ID 95: [DHCPv4.MulticastScopeConfigured] Scope: %1 for Multicast IPv4 is Configured by %2.
#Description
Scope: for Multicast IPv4 is Configured by .
References #
Event ID 95: Scope: IP_MulticastScopeName for Multicast IPv4 is Configured by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_MulticastScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 95,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.0969052+00:00",
"event_record_id": 24,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_MulticastScopeName": "[[224.0.1.10]det-mcast]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[224.0.1.10]det-mcast] for Multicast IPv4 is Configured by ludus\\domainadmin."
}
References #
Event ID 96: [DHCPv4.MulticastScopeDeleted] Scope: %1 for Multicast IPv4 is Deleted by %2.
#Description
Scope: for Multicast IPv4 is Deleted by .
References #
Event ID 96: Scope: IP_MulticastScopeName for Multicast IPv4 is Deleted by ClientName.
#Event ID 97
#Description
Scope: for IPv4 is Added in Superscope: by .
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
IP_SuperScopeName UnicodeString | |
ClientName UnicodeString |
Event ID 97: Scope: IP_ScopeName for IPv4 is Added in Superscope: IP_SuperScopeName by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
IP_SuperScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 97,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.1880185+00:00",
"event_record_id": 30,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[10.77.7.0]det-v4-b]",
"IP_SuperScopeName": "det-super",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[10.77.7.0]det-v4-b] for IPv4 is Added in Superscope: det-super by ludus\\domainadmin."
}
Event ID 98: [DHCPv4.SuperScopeConfigured] SuperScope: %1 for IPv4 is Configured by %2.
#Description
SuperScope: for IPv4 is Configured by .
References #
Event ID 98: SuperScope: IP_MulticastScopeName for IPv4 is Configured by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_MulticastScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 98,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.1793453+00:00",
"event_record_id": 28,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_MulticastScopeName": "det-super",
"ClientName": "ludus\\domainadmin"
},
"message": "SuperScope: det-super for IPv4 is Configured by ludus\\domainadmin."
}
References #
Event ID 99: [DHCPv4.SuperScopeDeleted] SuperScope: %1 for IPv4 is Deleted by %2.
#Description
SuperScope: for IPv4 is Deleted by .
References #
Event ID 99: SuperScope: IP_MulticastScopeName for IPv4 is Deleted by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_MulticastScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 99,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.2090162+00:00",
"event_record_id": 31,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_MulticastScopeName": "det-super",
"ClientName": "ludus\\domainadmin"
},
"message": "SuperScope: det-super for IPv4 is Deleted by ludus\\domainadmin."
}
References #
Event ID 100: [DHCPv4.SuperScopeActivated] Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.
#Description
Scope: within SuperScope: for IPv4 is Activated by .
References #
Event ID 100: Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is Activated by ClientName.
#Event ID 101: [DHCPv4.SuperScopeDeActivated] Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.
#Description
Scope: within SuperScope: for IPv4 is DeActivated by .
References #
Event ID 101: Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is DeActivated by ClientName.
#Event ID 102: [DHCPv4.SuperScopeDeleteTemp] Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.
#Description
Scope: for IPv4 is Removed in Superscope: by . However, the Scope exists outside the Superscope.
References #
Event ID 102: Scope: IP_ScopeName for IPv4 is Removed in Superscope: IP_SuperScopeName by ClientName.
#Event ID 103: [DHCPv4.SuperScopeDeletePerm] Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.
#Description
Scope: for IPv4 is Deleted in Superscope: as well as Deleted permanently by .
References #
Event ID 103: Scope: IP_ScopeName for IPv4 is Deleted in Superscope: IP_SuperScopeName as well as Deleted permanently by ClientName.
#Event ID 104
#Description
Delay Time: milliseconds for the OFFER message sent by Secondary Servers is Updated on Scope: for IPv4 by . The previous configured Delay Time was: milliseconds.
Fields #
| Name | Description |
|---|---|
UpdatedVal UnicodeString | |
IP_Name UnicodeString | |
OriginalVal UnicodeString | |
ClientName UnicodeString |
Event ID 104: Delay Time: UpdatedVal milliseconds for the OFFER message sent by Secondary Servers is Updated on Scope: IP_Name for IPv4 by ClientName.
#Description
Delay Time: UpdatedVal milliseconds for the OFFER message sent by Secondary Servers is Updated on Scope: IP_Name for IPv4 by ClientName. The previous configured Delay Time was: OriginalVal milliseconds.
Message #
Fields #
| Name | Description |
|---|---|
UpdatedVal UnicodeString | |
IP_Name UnicodeString | |
OriginalVal UnicodeString | |
ClientName UnicodeString |
Event ID 105: [DHCPv4.ServerOptionUpdate] Server level option %1 for IPv4 has been updated by %2.
#Description
Server level option for IPv4 has been updated by .
References #
Event ID 105: Server level option OptionName for IPv4 has been updated by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
OptionName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 105,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:20.3960118+00:00",
"event_record_id": 8,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"OptionName": "[15 - DNS Domain Name]",
"ClientName": "ludus\\domainadmin"
},
"message": "Server level option [15 - DNS Domain Name] for IPv4 has been updated by ludus\\domainadmin."
}
References #
Event ID 106: [DHCPv4.ReservationConfigured] Reservation: %1 for IPv4 is Configured under Scope %2 by %3.
#Description
Reservation: for IPv4 is Configured under Scope by .
References #
Event ID 106: Reservation: ReservationName for IPv4 is Configured under Scope IP_Name by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 106,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.7655930+00:00",
"event_record_id": 15,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ReservationName": "[[10.99.7.50]]",
"IP_Name": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Reservation: [[10.99.7.50]] for IPv4 is Configured under Scope [[10.99.7.0]detwiki-v4] by ludus\\domainadmin."
}
References #
Event ID 107: [DHCPv4.ReservationDeleted] Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.
#Description
Reservation: for IPv4 is Deleted under Scope by .
References #
Event ID 107: Reservation: ReservationName for IPv4 is Deleted under Scope IP_Name by ClientName.
#Event ID 108: [DHCPv4.ReservationDNSEnable] Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.
#Description
Reservation: for IPv4 under Scope: is Enabled for DNS Dynamic updates by .
References #
Event ID 108: Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS Dynamic updates by ClientName.
#Event ID 109: [DHCPv4.ReservationDNSDisable] Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.
#Description
Reservation: for IPv4 under Scope: is Disabled for DNS Dynamic updates by .
References #
Event ID 109: Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS Dynamic updates by ClientName.
#Event ID 110: [DHCPv4.ReservationDNSUpdate_Req_by_Client] Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to dynamically update DNS A and PTR records on request by the DHCP Clients.
#Description
Reservation: for IPv4 under Scope: is Updated with DNS Settings by : to dynamically update DNS A and PTR records on request by the DHCP Clients.
References #
Event ID 110: Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS Settings by ClientName: to dynamically update DNS A and PTR records on request by the DHCP Cli...
#Description
Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS Settings by ClientName: to dynamically update DNS A and PTR records on request by the DHCP Clients.
Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
References #
Event ID 111: [DHCPv4.ReservationDNSUpdate_Always] Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records.
#Description
Reservation: for IPv4 under Scope: is Updated with DNS Settings by : to always dynamically update DNS A and PTR records.
References #
Event ID 111: Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS Settings by ClientName: to always dynamically update DNS A and PTR records.
#Event ID 112: [DHCPv4.ReservationDNSEnable_Discard] Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Settings by %3: to discard DNS A and PTR records when lease is deleted.
#Description
Reservation: for IPv4 under Scope: is Enabled for DNS Settings by : to discard DNS A and PTR records when lease is deleted.
References #
Event ID 112: Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.
#Event ID 113: [DHCPv4.ReservationDNSDisable_Discard] Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Settings by %3: to discard DNS A and PTR records when lease is deleted.
#Description
Reservation: for IPv4 under Scope: is Disabled for DNS Settings by : to discard DNS A and PTR records when lease is deleted.
References #
Event ID 113: Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.
#Event ID 114: [DHCPv4.ReservationDNSEnableUpdate_No_Req_by_Client] Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Settings by %3: to dynamically update DNS A and PTR records for DHCP Clients that do...
#Description
Reservation: for IPv4 under Scope: is Enabled for DNS Settings by : to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
References #
Event ID 114: Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do no...
#Description
Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
References #
Event ID 115: [DHCPv4.ReservationDNSDisableUpdate_No_Req_by_Client] Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Settings by %3: to dynamically update DNS A and PTR records for DHCP Clients that ...
#Description
Reservation: for IPv4 under Scope: is Disabled for DNS Settings by : to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
References #
Event ID 115: Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do n...
#Description
Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS Settings by ClientName: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.
Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
References #
Event ID 116: [DHCPv4.ReservationOptionUpdate] Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4.
#Description
Reservation: for IPv4 under Scope: is Updated with Option Setting: by .
References #
Event ID 116: Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with Option Setting: OptionName by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
OptionName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 116,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.7872810+00:00",
"event_record_id": 16,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ReservationName": "[[10.99.7.50]]",
"IP_Name": "[[10.99.7.0]detwiki-v4]",
"OptionName": "[12 - Host Name]",
"ClientName": "ludus\\domainadmin"
},
"message": "Reservation: [[10.99.7.50]] for IPv4 under Scope: [[10.99.7.0]detwiki-v4] is Updated with Option Setting: [12 - Host Name] by ludus\\domainadmin."
}
References #
Event ID 117: [DHCPv4.ServerPBA_DeActivated] Policy based assignment has been disabled at server level.
#Description
Policy based assignment has been disabled at server level.
References #
Event ID 118: [DHCPv4.ServerPBA_Activated] Policy based assignment has been enabled at server level.
#Description
Policy based assignment has been enabled at server level.
References #
Event ID 119: [DHCPv4.ScopeExclusionAdded] Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.
#Description
Added exclusion IP Address range in the Address Pool for IPv4 under Scope: by .
References #
Event ID 119: Added exclusion IP Address range ExclusionRange in the Address Pool for IPv4 under Scope: IP_Name by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ExclusionRange UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 119,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.5276558+00:00",
"event_record_id": 43,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ExclusionRange": "[10.88.1.10 to 10.88.1.11]",
"IP_Name": "[[10.88.1.0]det-tiny]",
"ClientName": "ludus\\domainadmin"
},
"message": "Added exclusion IP Address range [10.88.1.10 to 10.88.1.11] in the Address Pool for IPv4 under Scope: [[10.88.1.0]det-tiny] by ludus\\domainadmin."
}
References #
Event ID 120: [DHCPv4.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.
#Description
Deleted exclusion IP Address range in the Address Pool for IPv4 under Scope: by .
References #
Event ID 120: Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv4 under Scope: IP_Name by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ExclusionRange UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 120,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.7385382+00:00",
"event_record_id": 14,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ExclusionRange": "[10.99.7.190 to 10.99.7.200]",
"IP_Name": "[[10.99.7.0]detwiki-v4]",
"ClientName": "ludus\\domainadmin"
},
"message": "Deleted exclusion IP Address range [10.99.7.190 to 10.99.7.200] in the Address Pool for IPv4 under Scope: [[10.99.7.0]detwiki-v4] by ludus\\domainadmin."
}
References #
Event ID 121: [DHCPv4.ScopeEnableAllow] Link Layer based filtering is Enabled in the allowlist of the IPv4 by %1
#Description
Link Layer based filtering is Enabled in the Allow List of the IPv4 by.
References #
Event ID 121: Link Layer based filtering is Enabled in the Allow List of the IPv4 by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 121,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8202748+00:00",
"event_record_id": 17,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ClientName": "ludus\\domainadmin"
},
"message": "Link Layer based filtering is Enabled in the Allow List of the IPv4 by ludus\\domainadmin "
}
References #
Event ID 122: [DHCPv4.ScopeDisableAllow] Link Layer based filtering is Disabled in the allowlist of the IPv4 by %1
#Description
Link Layer based filtering is Disabled in the Allow List of the IPv4 by.
References #
Event ID 122: Link Layer based filtering is Disabled in the Allow List of the IPv4 by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 122,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8814080+00:00",
"event_record_id": 23,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ClientName": "ludus\\domainadmin"
},
"message": "Link Layer based filtering is Disabled in the Allow List of the IPv4 by ludus\\domainadmin "
}
References #
Event ID 123: [DHCPv4.ScopeAllow_AddFilter] Filter for physical address: %1, hardware type: %3 added to the IPv4 allowlist by %2.
#Description
Filter for physical address: , hardware type: added to the IPv4 Allow List by .
References #
Event ID 123: Filter for physical address: PhysicalAddress, hardware type: HWType added to the IPv4 Allow List by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
PhysicalAddress UnicodeString | |
ClientName UnicodeString | |
HWType UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 123,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8369013+00:00",
"event_record_id": 19,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"PhysicalAddress": "AA-BB-CC-DD-EE-01",
"ClientName": "ludus\\domainadmin",
"HWType": "1"
},
"message": "Filter for physical address: AA-BB-CC-DD-EE-01, hardware type: 1 added to the IPv4 Allow List by ludus\\domainadmin. "
}
References #
Event ID 124: [DHCPv4.ScopeAllow_DeleteFilter] Filter for physical address: %1, hardware type: %3 removed from the IPv4 allowlist by %2.
#Description
Filter for physical address: , hardware type: removed from the IPv4 Allow List by .
References #
Event ID 124: Filter for physical address: PhysicalAddress, hardware type: HWType removed from the IPv4 Allow List by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
PhysicalAddress UnicodeString | |
ClientName UnicodeString | |
HWType UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 124,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8610101+00:00",
"event_record_id": 21,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"PhysicalAddress": "AA-BB-CC-DD-EE-01",
"ClientName": "ludus\\domainadmin",
"HWType": "1"
},
"message": "Filter for physical address: AA-BB-CC-DD-EE-01, hardware type: 1 removed from the IPv4 Allow List by ludus\\domainadmin. "
}
References #
Event ID 125: [DHCPv4.ScopeEnableDeny] Link Layer based filtering is Enabled in the blocklist of the IPv4 by %1
#Description
Link Layer based filtering is Enabled in the Deny List of the IPv4 by.
References #
Event ID 125: Link Layer based filtering is Enabled in the Deny List of the IPv4 by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 125,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8202806+00:00",
"event_record_id": 18,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ClientName": "ludus\\domainadmin"
},
"message": "Link Layer based filtering is Enabled in the Deny List of the IPv4 by ludus\\domainadmin "
}
References #
Event ID 126: [DHCPv4.ScopeDisableDeny] Link Layer based filtering is Disabled in the blocklist of the IPv4 by %1
#Description
Link Layer based filtering is Disabled in the Deny List of the IPv4 by.
References #
Event ID 126: Link Layer based filtering is Disabled in the Deny List of the IPv4 by ClientName.
#Event ID 127: [DHCPv4.ScopeDeny_AddFilter] Filter for physical address: %1, hardware type: %3 added to the IPv4 blocklist by %2.
#Description
Filter for physical address: , hardware type: added to the IPv4 Deny List by .
References #
Event ID 127: Filter for physical address: PhysicalAddress, hardware type: HWType added to the IPv4 Deny List by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
PhysicalAddress UnicodeString | |
ClientName UnicodeString | |
HWType UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 127,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8483932+00:00",
"event_record_id": 20,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"PhysicalAddress": "AA-BB-CC-DD-EE-99",
"ClientName": "ludus\\domainadmin",
"HWType": "1"
},
"message": "Filter for physical address: AA-BB-CC-DD-EE-99, hardware type: 1 added to the IPv4 Deny List by ludus\\domainadmin. "
}
References #
Event ID 128: [DHCPv4.ScopeDeny_DeleteFilter] Filter for physical address: %1, hardware type: %3 removed from the IPv4 blocklist by %2.
#Description
Filter for physical address: , hardware type: removed from the IPv4 Deny List by .
References #
Event ID 128: Filter for physical address: PhysicalAddress, hardware type: HWType removed from the IPv4 Deny List by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
PhysicalAddress UnicodeString | |
ClientName UnicodeString | |
HWType UInt32 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 128,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:32.8709903+00:00",
"event_record_id": 22,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"PhysicalAddress": "AA-BB-CC-DD-EE-99",
"ClientName": "ludus\\domainadmin",
"HWType": "1"
},
"message": "Filter for physical address: AA-BB-CC-DD-EE-99, hardware type: 1 removed from the IPv4 Deny List by ludus\\domainadmin. "
}
References #
Event ID 129
#Description
Scope: for IPv6 is Configured by .
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Event ID 129: Scope: IP_ScopeName for IPv6 is Configured by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 129,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.2452955+00:00",
"event_record_id": 32,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is Configured by ludus\\domainadmin."
}
Event ID 130: [DHCPv6.ScopeDeleted] Scope: %1 for IPv6 is Deleted by %2.
#Description
Scope: for IPv6 is Deleted by .
References #
Event ID 130: Scope: IP_ScopeName for IPv6 is Deleted by ClientName.
#Event ID 131: [DHCPv6.ScopeActivated] Scope: %1 for IPv6 is Activated by %2.
#Description
Scope: for IPv6 is Activated by .
References #
Event ID 131: Scope: IP_ScopeName for IPv6 is Activated by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 131,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.2905320+00:00",
"event_record_id": 35,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is Activated by ludus\\domainadmin."
}
References #
Event ID 132: [DHCPv6.ScopeDeActivated] Scope: %1 for IPv6 is DeActivated by %2.
#Description
Scope: for IPv6 is DeActivated by .
References #
Event ID 132: Scope: IP_ScopeName for IPv6 is DeActivated by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 132,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.2794302+00:00",
"event_record_id": 34,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is DeActivated by ludus\\domainadmin."
}
References #
Event ID 133: [DHCPv6.ScopeLeasePreferredUpdate] Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime: %2 by %3. The previous configured Lease Preferred Lifetime was: %4.
#Description
Scope: for IPv6 is Updated with Lease Preferred Lifetime: by . The previous configured Lease Preferred Lifetime was: .
References #
Event ID 133: Scope: IP_ScopeName for IPv6 is Updated with Lease Preferred Lifetime: ModifiedDuration by ClientName.
#Description
Scope: IP_ScopeName for IPv6 is Updated with Lease Preferred Lifetime: ModifiedDuration by ClientName. The previous configured Lease Preferred Lifetime was: OriginalDuration.
Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ModifiedDuration UnicodeString | |
ClientName UnicodeString | |
OriginalDuration UnicodeString |
References #
Event ID 134: [DHCPv6.ScopeLeaseValidUpdate] Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4.
#Description
Scope: for IPv6 is Updated with Lease Valid Lifetime: by . The previous configured Lease Valid Lifetime was: .
References #
Event ID 134: Scope: IP_ScopeName for IPv6 is Updated with Lease Valid Lifetime: ModifiedDuration by ClientName.
#Description
Scope: IP_ScopeName for IPv6 is Updated with Lease Valid Lifetime: ModifiedDuration by ClientName. The previous configured Lease Valid Lifetime was: OriginalDuration.
Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ModifiedDuration UnicodeString | |
ClientName UnicodeString | |
OriginalDuration UnicodeString |
References #
Event ID 135: [DHCPv6.ScopeOptionUpdate] Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3.
#Description
Scope: for IPv6 is Updated with Option Setting: by .
References #
Event ID 135: Scope: IP_ScopeName for IPv6 is Updated with Option Setting: OptionName by ClientName.
#Event ID 136: [DHCPv6.ScopeDNSEnable] Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.
#Description
Scope: for IPv6 is Enabled for DNS Dynamic updates by .
References #
Event ID 136: Scope: IP_ScopeName for IPv6 is Enabled for DNS Dynamic updates by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 136,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.3810623+00:00",
"event_record_id": 36,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is Enabled for DNS Dynamic updates by ludus\\domainadmin."
}
References #
Event ID 137: [DHCPv6.ScopeDNSDisable] Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.
#Description
Scope: for IPv6 is Disabled for DNS Dynamic updates by .
References #
Event ID 137: Scope: IP_ScopeName for IPv6 is Disabled for DNS Dynamic updates by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 137,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.3918235+00:00",
"event_record_id": 37,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is Disabled for DNS Dynamic updates by ludus\\domainadmin."
}
References #
Event ID 138: [DHCPv6.ScopeDNSUpdate_Req_by_Client] Scope: %1 for IPv6 is Updated with DNS Settings by %2: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
#Description
Scope: for IPv6 is Updated with DNS Settings by : to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
References #
Event ID 138: Scope: IP_ScopeName for IPv6 is Updated with DNS Settings by ClientName: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
#Event ID 139: [DHCPv6.ScopeDNSUpdate_Always] Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records.
#Description
Scope: for IPv6 is Updated with DNS Settings by : to always dynamically update DNS AAAA and PTR records.
References #
Event ID 139: Scope: IP_ScopeName for IPv6 is Updated with DNS Settings by ClientName: to always dynamically update DNS AAAA and PTR records.
#Event ID 140: [DHCPv6.ScopeDNSEnable_Discard] Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.
#Description
Scope: for IPv6 is Enabled for DNS Settings by : to discard DNS AAAA and PTR records when lease is deleted.
References #
Event ID 140: Scope: IP_ScopeName for IPv6 is Enabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.
#Event ID 141: [DHCPv6.ScopeDNSDisable_Discard] Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.
#Description
Scope: for IPv6 is Disabled for DNS Settings by : to discard DNS AAAA and PTR records when lease is deleted.
References #
Event ID 141: Scope: IP_ScopeName for IPv6 is Disabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.
#Event ID 142: [DHCPv6.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.
#Description
Name Protection setting is Enabled on Scope: for IPv6 by .
References #
Event ID 142: Name Protection setting is Enabled on Scope: IP_Name for IPv6 by ClientName.
#Event ID 143: [DHCPv6.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.
#Description
Name Protection setting is Disabled on Scope: for IPv6 by .
References #
Event ID 143: Name Protection setting is Disabled on Scope: IP_Name for IPv6 by ClientName.
#Event ID 145: [DHCPv6.ReservationConfigured] Reservation: %1 for IPv6 is Configured under Scope %2 by %3.
#Description
Reservation: for IPv6 is Configured under Scope by .
References #
Event ID 145: Reservation: ReservationName for IPv6 is Configured under Scope IP_Name by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 145,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.4221240+00:00",
"event_record_id": 39,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ReservationName": "[[2001:db8:dec0:de01::100]]",
"IP_Name": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Reservation: [[2001:db8:dec0:de01::100]] for IPv6 is Configured under Scope [[2001:db8:dec0:de01::]det-v6] by ludus\\domainadmin."
}
References #
Event ID 147: [DHCPv6.ReservationDeleted] Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.
#Description
Reservation: for IPv6 is Deleted under Scope by .
References #
Event ID 147: Reservation: ReservationName for IPv6 is Deleted under Scope IP_Name by ClientName.
#Event ID 148: [DHCPv6.ReservationDNSEnable] Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.
#Description
Reservation: for IPv6 under Scope: is Enabled for DNS Dynamic updates by .
References #
Event ID 148: Reservation: ReservationName for IPv6 under Scope: IP_Name is Enabled for DNS Dynamic updates by ClientName.
#Event ID 149: [DHCPv6.ReservationDNSDisable] Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.
#Description
Reservation: for IPv6 under Scope: is Disabled for DNS Dynamic updates by .
References #
Event ID 149: Reservation: ReservationName for IPv6 under Scope: IP_Name is Disabled for DNS Dynamic updates by ClientName.
#Event ID 150: [DHCPv6.ReservationDNSUpdate_Req_by_Client] Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
#Description
Reservation: for IPv6 under Scope: is Updated with DNS Settings by : to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
References #
Event ID 150: Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS Settings by ClientName: to dynamically update DNS AAAA and PTR records on request by the DHCP ...
#Description
Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS Settings by ClientName: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients.
Message #
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
References #
Event ID 151: [DHCPv6.ReservationDNSUpdate_Always] Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records.
#Description
Reservation: for IPv6 under Scope: is Updated with DNS Settings by : to always dynamically update DNS AAAA and PTR records.
References #
Event ID 151: Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS Settings by ClientName: to always dynamically update DNS AAAA and PTR records.
#Event ID 152: [DHCPv6.ReservationDNSEnable_Discard] Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Settings by %3: to discard DNS AAAA and PTR records when lease is deleted.
#Description
Reservation: for IPv6 under Scope: is Enabled for DNS Settings by : to discard DNS AAAA and PTR records when lease is deleted.
References #
Event ID 152: Reservation: ReservationName for IPv6 under Scope: IP_Name is Enabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.
#Event ID 153: [DHCPv6.ReservationDNSDisable_Discard] Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Settings by %3: to discard DNS AAAA and PTR records when lease is deleted.
#Description
Reservation: for IPv6 under Scope: is Disabled for DNS Settings by : to discard DNS AAAA and PTR records when lease is deleted.
References #
Event ID 153: Reservation: ReservationName for IPv6 under Scope: IP_Name is Disabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.
#Event ID 154: [DHCPv6.ReservationOptionUpdate] Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.
#Description
Reservation: for IPv6 under Scope: is Updated with Option Setting: by .
References #
Event ID 154: Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with Option Setting: OptionName by ClientName.
#Event ID 155: [DHCPv6.ScopeExclusionAdded] Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.
#Description
Added exclusion IP Address range in the Address Pool for IPv6 under Scope: by .
References #
Event ID 155: Added exclusion IP Address range ExclusionRange in the Address Pool for IPv6 under Scope: IP_Name by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
ExclusionRange UnicodeString | |
IP_Name UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 155,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.4061817+00:00",
"event_record_id": 38,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"ExclusionRange": "[2001:db8:dec0:de01::1 to 2001:db8:dec0:de01::5]",
"IP_Name": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Added exclusion IP Address range [2001:db8:dec0:de01::1 to 2001:db8:dec0:de01::5] in the Address Pool for IPv6 under Scope: [[2001:db8:dec0:de01::]det-v6] by ludus\\domainadmin."
}
References #
Event ID 156: [DHCPv6.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.
#Description
Deleted exclusion IP Address range in the Address Pool for IPv6 under Scope: by .
References #
Event ID 156: Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv6 under Scope: IP_Name by ClientName.
#Event ID 157: [DHCPv6.ScopeModified] Scope: %1 for IPv6 is Modified by %2.
#Description
Scope: for IPv6 is Modified by .
References #
Event ID 157: Scope: IP_ScopeName for IPv6 is Modified by ClientName.
#Message #
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 157,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": -9223372036854775808,
"time_created": "2026-05-30T01:43:33.2650708+00:00",
"event_record_id": 33,
"correlation": {},
"execution": {
"process_id": 8848,
"thread_id": 1516
},
"channel": "Microsoft-Windows-Dhcp-Server/Operational",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
}
},
"event_data": {
"IP_ScopeName": "[[2001:db8:dec0:de01::]det-v6]",
"ClientName": "ludus\\domainadmin"
},
"message": "Scope: [[2001:db8:dec0:de01::]det-v6] for IPv6 is Modified by ludus\\domainadmin."
}
References #
Event ID 158: [DHCPv6.ScopeStatelessEnabled] DHCPv6 Stateless client inventory has been enabled for the scope %1.
#Description
DHCPv6 Stateless client inventory has been enabled for the scope .
References #
Event ID 158: DHCPv6 Stateless client inventory has been enabled for the scope IP_ScopeName.
#Event ID 159: [DHCPv6.ScopeStatelessDisabled] DHCPv6 Stateless client inventory has been disabled for the scope %1.
#Description
DHCPv6 Stateless client inventory has been disabled for the scope .
References #
Event ID 159: DHCPv6 Stateless client inventory has been disabled for the scope IP_ScopeName.
#Event ID 160: [DHCPv6.ServerStatelessEnabled] DHCPv6 Stateless client inventory has been enabled for the server.
#Description
DHCPv6 Stateless client inventory has been enabled for the server.
References #
Event ID 161: [DHCPv6.ServerStatelessDisabled] DHCPv6 Stateless client inventory has been disabled for the server.
#Description
DHCPv6 Stateless client inventory has been disabled for the server.
References #
Event ID 162: [DHCPv6.ScopeStatelessPurgeInterval] Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours.
#Description
Purge time interval for DHCPv6 stateless client inventory for scope has been set to hours.
References #
Event ID 162: Purge time interval for DHCPv6 stateless client inventory for scope IP_ScopeName has been set to PurgeInterval hours.
#Event ID 163: [DHCPv6.ServerStatelessPurgeInterval] Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.
#Description
Purge time interval for DHCPv6 stateless client inventory for server has been set to hours.
References #
Event ID 163: Purge time interval for DHCPv6 stateless client inventory for server has been set to PurgeInterval hours.
#Event ID 164
#Description
Scope: for IPv4 is Enabled for DNS Settings by : to disable dynamic updates for DNS PTR records.
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
ClientName UnicodeString |
Event ID 164: Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to disable dynamic updates for DNS PTR records.
#Event ID 165: [DHCPv4.ScopeDNSDisable_DisablePtrUpdates] Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.
#Description
Scope: for IPv4 is Disabled for DNS Settings by : to disable dynamic updates for DNS PTR records.
References #
Event ID 165: Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to disable dynamic updates for DNS PTR records.
#Event ID 166: [DHCPv6.ServerOptionUpdate] Server level option %1 for IPv6 has been updated by %2.
#Description
Server level option for IPv6 has been updated by .
References #
Event ID 166: Server level option OptionName for IPv6 has been updated by ClientName.
#Event ID 167
#Description
Server level option for IPv4 has been removed by .
Fields #
| Name | Description |
|---|---|
OptionName UnicodeString | |
ClientName UnicodeString |
Event ID 167: Server level option OptionName for IPv4 has been removed by ClientName.
#Event ID 168
#Description
Option setting: has been removed from IPv4 scope: by .
Fields #
| Name | Description |
|---|---|
IP_ScopeName UnicodeString | |
OptionName UnicodeString | |
ClientName UnicodeString |
Event ID 168: Option setting: OptionName has been removed from IPv4 scope: IP_ScopeName by ClientName.
#Event ID 169
#Description
Option setting: has been removed from the reservation: in IPv4 scope: by .
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
OptionName UnicodeString | |
ClientName UnicodeString |
Event ID 169: Option setting: OptionName has been removed from the reservation: ReservationName in IPv4 scope: IP_Name by ClientName.
#Event ID 170
#Description
Server level option for IPv6 has been removed by .
Fields #
| Name | Description |
|---|---|
OptionName UnicodeString | |
ClientName UnicodeString |
Event ID 170: Server level option OptionName for IPv6 has been removed by ClientName.
#Event ID 172
#Description
Option setting: has been removed from the reservation: in IPv6 scope: by .
Fields #
| Name | Description |
|---|---|
ReservationName UnicodeString | |
IP_Name UnicodeString | |
OptionName UnicodeString | |
ClientName UnicodeString |
Event ID 172: Option setting: OptionName has been removed from the reservation: ReservationName in IPv6 scope: IP_Name by ClientName.
#Event ID 1000: [EVENT_SERVER_UNKNOWN_OPTION] The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below.
#Event ID 1001: [EVENT_SERVER_FAILED_REGISTER_SC] The DHCP service failed to register with Service Controller.
#Event ID 1002: [EVENT_SERVER_INIT_DATA_FAILED] The DHCP service failed to initialize its global parameters.
#Event ID 1003: [EVENT_SERVER_INIT_REGISTRY_FAILED] The DHCP service failed to initialize its registry parameters.
#Event ID 1004: [EVENT_SERVER_INIT_DATABASE_FAILED] The DHCP service failed to initialize the database.
#Event ID 1005: [EVENT_SERVER_INIT_WINSOCK_FAILED] The DHCP service failed to initialize Winsock startup.
#Event ID 1006: [EVENT_SERVER_INIT_RPC_FAILED] The DHCP service failed to start as an RPC server.
#Event ID 1007: [EVENT_SERVER_INIT_SOCK_FAILED] The DHCP service failed to initialize Winsock data.
#Event ID 1008: [EVENT_SERVER_SHUTDOWN] The DHCP service is shutting down due to the following error: %1
#Event ID 1009: [EVENT_SERVER_CLIENT_CLEANUP] The DHCP service encountered the following error while cleaning up the pending client records: %1
#Event ID 1010: [EVENT_SERVER_DATABASE_CLEANUP] The DHCP service encountered the following error while cleaning up the database: %1
#Event ID 1011: [EVENT_SERVER_LEASE_NACK] The DHCP service issued a NACK to the client, %2, for the address, %1.
#Event ID 1012: [EVENT_SERVER_LEASE_DECLINED] The DHCP client, %2, declined the address %1.
#Event ID 1013: [EVENT_SERVER_LEASE_RELEASE] The DHCP Client, %2, released the address %1.
#Event ID 1016: [EVENT_SERVER_DATABASE_BACKUP] The DHCP service encountered the following error when backing up the database: %1
#Event ID 1017: [EVENT_SERVER_CONFIG_BACKUP] The DHCP service encountered the following error when backing up the registry configuration: %1
#Event ID 1018: [EVENT_SERVER_DATABASE_RESTORE_FAILED] The DHCP service failed to restore the database.
#Event ID 1019: [EVENT_SERVER_CONFIG_RESTORE_FAILED] The DHCP service failed to restore the DHCP registry configuration.
#Event ID 1020: [EVENT_SERVER_LOW_ADDRESS_WARNING] Scope, %1, is %2 percent full with only %3 IP addresses remaining.
#Event ID 1021: [EVENT_SERVER_LOAD_JET_FAILED] The DHCP service couldn't load the JET database library successfully.
#Event ID 1022: [EVENT_SERVER_JET_CONV_REQUIRED] The DHCP service couldn't use the database.
#Event ID 1023: [EVENT_SERVER_JET_CONV_IN_PROGRESS] The DHCP service will now terminate because the existing database needs conversion to Windows 2000 format.
#Event ID 1024: [EVENT_SERVER_INIT_AND_READY] The DHCP service has initialized and is ready.
#Event ID 1025: [EVENT_SERVER_BOOT_FILE_TABLE] The DHCP service was unable to read the BOOTP file table from the registry.
#Event ID 1026: [EVENT_SERVER_BOOT_FILE_NAME] The DHCP service was unable to read the global BOOTP file name from the registry.
#Event ID 1027: [EVENT_SERVER_AUDIT_LOG_APPEND_FAILED] The audit log file can't be appended.
#Event ID 1028: [EVENT_SERVER_INIT_AUDIT_LOG_FAILED] The DHCP service failed to initialize the audit log.
#Event ID 1029: [EVENT_SERVER_PING_FAILED] The DHCP service was unable to ping for a new IP address. The address was leased to the client.
#Event ID 1030: [EVENT_SERVER_MOVE_AUDIT_LOG_FAILED] The audit log file couldn't be backed up.
#Event ID 1031: [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception.
#Description
The installed server callout .dll file has caused an exception. The exception was.
Message #
Detection Patterns #
Stealth: DLL
DHCP-Server Event ID 1031: [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception.OREvent ID 1032: [EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has caused an exception. The .dll file couldn't be loaded.OREvent ID 1034: [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs.
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | microsoft-windows-dhcp-server | 1 rule | sigma |
References #
Event ID 1032: [EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has caused an exception. The .dll file couldn't be loaded.
#Description
The installed server callout .dll file has caused an exception. The exception was.
Message #
Detection Patterns #
Stealth: DLL
DHCP-Server Event ID 1031: [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception.OREvent ID 1032: [EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has caused an exception. The .dll file couldn't be loaded.OREvent ID 1034: [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs.
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | microsoft-windows-dhcp-server | 1 rule | sigma |
References #
Event ID 1033: [EVENT_SERVER_CALLOUT_LOAD_SUCCESS] The DHCP service has successfully loaded one or more callout DLLs.
#Description
The DHCP service has successfully loaded one or more callout DLLs.
Message #
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | microsoft-windows-dhcp-server | 1 rule | sigma |
Detection Rules #
Full rule details for this event, including ATT&CK technique mappings and native queries →Sigma # view in coverage
T1574, T1574.001
References #
Event ID 1034: [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs.
#Description
The DHCP service has failed to load one or more callout DLLs. The following error occured.
Message #
Fields #
| Name | Description |
|---|---|
Data_0 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 1034,
"version": 0,
"level": 3,
"task": 0,
"opcode": 0,
"keywords": 36028797018963968,
"time_created": "2026-05-30T14:11:40.6693564+00:00",
"event_record_id": 40872,
"correlation": {},
"execution": {
"process_id": 0,
"thread_id": 0
},
"channel": "System",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": ""
}
},
"event_data": {
"Data_0": "The specified module could not be found.\n"
},
"message": "The DHCP service has failed to load one or more callout DLLs. The following error occured: \r\nThe specified module could not be found.\r\n"
}
Detection Patterns #
Stealth: DLL
DHCP-Server Event ID 1031: [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception.OREvent ID 1032: [EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has caused an exception. The .dll file couldn't be loaded.OREvent ID 1034: [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs.
Common Indicators #
Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.
| Field | Kind | Value | Rules | Vendors |
|---|---|---|---|---|
Provider_Name | eq | microsoft-windows-dhcp-server | 1 rule | sigma |
References #
Event ID 1035: [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service was unable to create or look up the DHCP Users local group on this computer.
#Event ID 1036: [EVENT_SERVER_ADMIN_GROUP_ERROR] The DHCP server was unable to create or look up the DHCP Administrators local group on this computer.
#Event ID 1037: [EVENT_SERVER_CLEANUP_STARTED] The DHCP service has started to clean up the database.
#Event ID 1038: [EVENT_SERVER_IPCLEANUP_FINISHED] The DHCP service has cleaned up the database for unicast IP addresses.
#Event ID 1039: [EVENT_SERVER_MCASTCLEANUP_FINISHED] The DHCP service has cleaned up the database for multicast IP addresses.
#Event ID 1040: [EVENT_SERVER_DATABASE_RESTORE_SUCCEEDED] The DHCP service successfully restored the database.
#Event ID 1041: [DHCP_ROGUE_EVENT_NO_NETWORK] The DHCP service isn't servicing any DHCPv4 clients because none of the active network interfaces have statically configured IPv4 addresses.
#Event ID 1042: [DHCP_ROGUE_EVENT_UNAUTHORIZED_INFO] The DHCP/BINL service running on this machine has detected a server on the network.
#Event ID 1043: [DHCP_ROGUE_EVENT_STARTED] The DHCP/BINL service on the local machine has determined that it's authorized to start.
#Event ID 1044: [DHCP_ROGUE_EVENT_STARTED_DOMAIN] The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain Data_1, has determined that it's authorized to start.
#Description
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain , has determined that it is authorized to start. It is servicing clients now.
Message #
Fields #
| Name | Description |
|---|---|
Data_0 | |
Data_1 | |
Data_2 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 1044,
"version": 0,
"level": 4,
"task": 0,
"opcode": 0,
"keywords": 36028797018963968,
"time_created": "2026-05-30T01:43:40.8401733+00:00",
"event_record_id": 35173,
"correlation": {},
"execution": {
"process_id": 0,
"thread_id": 0
},
"channel": "System",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": ""
}
},
"event_data": {
"Data_0": "",
"Data_1": "ludus.domain",
"Data_2": "0"
},
"message": "The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain ludus.domain, has determined that it is authorized to start. It is servicing clients now."
}
References #
Event ID 1045: [DHCP_ROGUE_EVENT_STOPPED] The DHCP/BINL service on the local machine has determined that it isn't authorized to start. It has stopped servicing clients.
#Event ID 1046: [DHCP_ROGUE_EVENT_STOPPED_DOMAIN] The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, has determined that it isn't authorized to start.
#Event ID 1047: [DHCP_ROGUE_EVENT_JUST_UPGRADED] The DHCP/BINL service on the local machine has determined that it's authorized to start. The machine was recently upgraded.
#Event ID 1048: [DHCP_ROGUE_EVENT_JUST_UPGRADED_DOMAIN] The DHCP/BINL Service on the local machine, belonging to Windows Domain %2, has determined that it's authorized to start. The computer was recently upgraded.
#Event ID 1049: [DHCP_ROGUE_EVENT_CANT_FIND_DOMAIN] The DHCP/BINL service on the local machine encountered an error while trying to find the domain of the local machine.
#Event ID 1050: [DHCP_ROGUE_EVENT_NETWORK_FAILURE] The DHCP/BINL service on the local machine encountered a network error.
#Event ID 1051: [DHCP_ROGUE_EVENT_UNAUTHORIZED] The DHCP/BINL service has determined that it isn't authorized to service clients on this network.
#Event ID 1052: [DHCP_ROGUE_EVENT_OTHER_SERVER] The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2.
#Event ID 1053: [DHCP_ROGUE_EVENT_SAM_OTHER_SERVER] The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2.
#Event ID 1054: [DHCP_ROGUE_EVENT_SHUTDOWN] The DHCP/BINL service on this computer is shutting down.
#Event ID 1055: [DHCP_EVENT_DNS_REGPARAMS_FAILURE] The DHCP service was unable to impersonate the credentials necessary for DNS registrations.
#Event ID 1056: [DHCP_EVENT_NO_DNSCREDENTIALS_ON_DC] The DHCP service has detected that it's running on a DC and has no credentials configured for use with Dynamic DNS registrations.
#Message #
Fields #
| Name | Description |
|---|---|
Data_0 |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 1056,
"version": 0,
"level": 3,
"task": 0,
"opcode": 0,
"keywords": 36028797018963968,
"time_created": "2026-05-30T01:43:36.7839250+00:00",
"event_record_id": 35171,
"correlation": {},
"execution": {
"process_id": 0,
"thread_id": 0
},
"channel": "System",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": ""
}
},
"event_data": {
"Data_0": "The operation completed successfully.\n"
},
"message": "The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line \"netsh dhcp server set dnscredentials\" or via the DHCP Administrative tool."
}
References #
Event ID 1057: [EVENT_SERVER_DATABASE_CONVERSION] The DHCP service was unable to convert the temporary database to ESE format.
#Event ID 1058: [EVENT_SERVER_INIT_CONFIG_FAILED] The DHCP service failed to initialize its configuration parameters.
#Event ID 1059: [VENT_SERVER_COULDNT_SEE_DS] The DHCP service failed to see a directory server for authorization.
#Event ID 1060: [EVENT_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the audit log.
#Event ID 1061: [EVENT_SERVER_BACKUP_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the database backups.
#Event ID 1062: [EVENT_SERVER_DB_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the database.
#Event ID 1063: [EVENT_SERVER_SCOPE_FULL] There are no IP addresses available for lease in the scope or superscope %1.
#Event ID 1064: [EVENT_SERVER_BOOTP_FULL] There are no IP addresses available for BOOTP clients in the scope or superscope %1.
#Event ID 1065: [EVENT_SERVER_ORPHONED_ENTRIES_DELETED] There were some orphaned entries deleted in the configuration due to the deletion of a class or an option definition.
#Event ID 1144: [EVENT_SERVER_NEED_STATIC_IP] This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.
#Event ID 1338: [EVENT_SERVER_OFFER_QUEUE_FULL] The number of pending DHCPOFFER messages for delayed transmission to the client has exceeded the server's capacity of 1,000 pending messages.
#Event ID 1339: [EVENT_SERVER_OFFER_QUEUE_FUNCTIONAL] The number pending DHCPOFFER messages for delayed transmission to the client are now below the server's capacity of 1,000.
#Event ID 1340: [EVENT_SERVER_DNSDHCID_FAIL] The DNS registration for DHCPv4 Client IP address %1, FQDN %2, and DHCID %3 has been denied.
#Event ID 1341: [EVENT_SERVER_POLICY_RANGES_FULL] There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2.
#Event ID 1342: [EVENT_SERVER_RESIDUAL_RANGES_FULL] IP address range of scope %1 is out of IP addresses.
#Event ID 1343: [EVENT_SERVER_POLICY_RANGES_LOW_ADDRESS_WARNING] IP address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available.
#Event ID 1344: [EVENT_SERVER_DNS_VALIDATION_FAILED] The DNS IP Address %1 isn't a valid DNS Server Address.
#Event ID 1376: [EVENT_SERVER_RESIDUAL_RANGES_LOW_ADDRESS_WARNING] IP address range of scope %1 is %2 percent full with only %3 IP addresses available.
#Event ID 1377: [EVENT_SERVER_SUPERSCOPE_LOW_ADDRESS_WARNING] SuperScope, %1, is %2 percent full with only %3 IP addresses remaining.
#Event ID 10000: [EVENT_DHCPV6_ADDERESS_NACKED] DHCPv6 confirmation has been declined because the address wasn't appropriate to the link.
#Event ID 10001: [EVENT_DHCPV6_REQUEST_RECEIVED_FOR_ADDRESSES_NOT_LEASED] Renew, rebind, or confirm received for IPv6 addresses %1 for which there are no active lease available.
#Event ID 10002: [EVENT_DHCPV6_SERVER_UNKNOWN_OPTION] DHCPv6 service received the unknown option %1, with a length of %2.
#Event ID 10003: [EVENT_DHCPV6_SERVER_SCOPE_FULL] There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1.
#Event ID 10004: [EVENT_DHCPV6_SERVER_LEASE_DECLINED] The DHCPv6 client, %2, declined the address %1.
#Event ID 10005: [EVENT_DHCPV6_SERVER_LOW_ADDRESS_WARNING] DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining.
#Event ID 10006: [EVENT_DHCPV6_CLIENT_DELETE] A DHCPv6 client %1 has been deleted from DHCPv6 database.
#Event ID 10007: [EVENT_DHCPV6_DROP_TIMEOUT] A DHCPv6 message that was in the queue for more than 30 seconds has been dropped because it's too old to process.
#Event ID 10008: [EVENT_DHCPV6_DROP_INVALID] An invalid DHCPv6 message has been dropped.
#Event ID 10009: [EVENT_DHCPV6_DROP_WRONG_SERVER] A DHCPv6 message that wasn't meant for this server has been dropped.
#Event ID 10010: [EVENT_DHCPV6_DROP_UNICAST] DHCPv6 message has been dropped because it was received on a Unicast address and unicast support is disabled on the server.
#Event ID 10011: [EVENT_DHCPV6_SERVER_AUDIT_LOG_APPEND_FAILED] DHCPv6 audit log file can't be appended, Error Code returned %1.
#Event ID 10012: [EVENT_DHCPV6_DROP_UNAUTH] A DHCPv6 message has been dropped because the server isn't authorized to process the message.
#Event ID 10013: [EVENT_DHCPv6_SERVER_INIT_AUDIT_LOG_FAILED] The DHCPv6 service failed to initialize the audit log.
#Event ID 10014: [EVENT_DHCPV6_SERVER_MOVE_AUDIT_LOG_FAILED] DHCPv6 audit log file couldn't be backed up.
#Event ID 10015: [EVENT_DHCPV6_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCPv6 service was unable to access path specified for the audit log.
#Event ID 10016: [EVENT_DHCPV6_SERVER_INIT_WINSOCK_FAILED] The DHCPv6 service failed to initialize Winsock startup.
#Event ID 10017: [EVENT_DHCPV6_NO_DNSCREDENTIALS_ON_DC] The DHCPv6 service has detected that it's running on a DC and has no credentials configured for use with Dynamic DNS registrations.
#Event ID 10018: [EVENT_DHCPV6_SERVER_INTERFACE_NOTIFICATION] The DHCPv6 Server failed to receive a notification of interface list changes.
#Event ID 10019: [EVENT_DHCPV6_SERVER_INIT_CONFIG_FAILED] The DHCPv6 service failed to initialize its configuration parameters.
#Event ID 10020: [EVENT_DHCPV6_SERVER_NEED_STATIC_IP] This computer has at least one dynamically assigned IPv6 address. For reliable DHCPv6 server operation, you should use only static IPv6 addresses.
#Description
This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.
Message #
Example Event #
{
"system": {
"provider": "Microsoft-Windows-DHCP-Server",
"guid": "{6D64F02C-A125-4DAC-9A01-F0555B41CA84}",
"event_source_name": "",
"event_id": 10020,
"version": 0,
"level": 3,
"task": 0,
"opcode": 0,
"keywords": 36028797018963968,
"time_created": "2026-05-30T01:43:40.8088599+00:00",
"event_record_id": 35172,
"correlation": {},
"execution": {
"process_id": 0,
"thread_id": 0
},
"channel": "System",
"computer": "JD-DC01-2022.ludus.domain",
"security": {
"user_id": ""
}
},
"event_data": {},
"message": "This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses."
}
References #
Event ID 10021: [EVENT_DHCPV6_SERVER_INIT_DATABASE_FAILED] DHCPv6 service failed to initialize the database.
#Event ID 10022: [EVENT_DHCPV6_SERVER_INIT_AND_READY] The DHCPv6 service has initialized and is ready to serve.
#Event ID 10023: [EVENT_DHCPV6_PORT_UNAVAILABLE] DHCPv6 Server is unable to bind to UDP port number %1 as it's used by another application.
#Event ID 10024: [ERROR_LAST_DHCPV6_SERVER_ERROR] ERROR_LAST_DHCPV6_SERVER_ERROR
#Event ID 10025: [EVENT_DHCPV6_DNSDHCID_FAIL] The DNS registration for DHCPv6 Client IPv6 address %1, FQDN %2 and DHCID %3 have been denied.
#Event ID 20035: [EVENT_SERVER_INTERFACE_NOTIFICATION] %1 %3
#Event ID 20058: [DHCPv4HA.BndUpd] RelationshipName PktContents
#Event ID 20059: [DHCPv4HA.BndAck] RelationshipName PktContents
#Event ID 20060: [DHCPv4HA.Connect] RelationshipName PktContents
#Event ID 20061: [DHCPv4HA.ConnectAck] RelationshipName PktContents
#Event ID 20062: [DHCPv4HA.UpdReqAll] RelationshipName PktContents
#Event ID 20063: [DHCPv4HA.UpdDone] RelationshipName PktContents
#Event ID 20064: [DHCPv4HA.UpdReq] RelationshipName PktContents
#Event ID 20065: [DHCPv4HA.State] RelationshipName PktContents
#Event ID 20066: [DHCPv4HA.Contact] RelationshipName PktContents
#Event ID 20067: [DHCPv4HA.Disconnect] RelationshipName PktContents
#Event ID 20068: [DHCPv4HA.ScavengerStart] Scavenger started.
#Description
Scavenger started.
References #
Event ID 20090: [EVENT_DHCP_PORT_UNAVAILABLE] DHCP Server is unable to bind to UDP port number %1 as it's used by another application.
#Event ID 20096: [EVENT_FILTER_DENIED_IN_DENY_LIST] DHCP Services denied to machine with hardware address %1, hardware type %4, and FQDN/Hostname %2 because it matched entry %3 in the blocklist.
#Description
DHCP Services were denied to machine with hardware address , hardware type and FQDN/Hostname because it matched entry in the Deny List.
References #
Event ID 20096: DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and FQDN/Hostname HostName because it matched entry DenyFilter in the Deny List.
#Event ID 20097: [EVENT_FILTER_DENIED_NOT_IN_ALLOW_LIST] DHCP Services denied to machine with hardware address %1, hardware type %3, and FQDN/Hostname %2 because it didn't match any entry in the allowlist.
#Description
DHCP Services were denied to machine with hardware address , hardware type and FQDN/Hostname because it did not match any entry in the Allow List.
References #
Event ID 20097: DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and FQDN/Hostname HostName because it did not match any entry in the Allo...
#Event ID 20098: [EVENT_FILTER_EMPTY_ALLOW_LIST] No DHCP clients are being served, as the allowlist is empty and the server was configured to provide DHCP services to clients in the allowlist.
#Event ID 20099: [EVENT_FILTER_DENIED_IN_DENY_LIST_UNSPECIFIED] DHCP Services denied to machine with hardware address %1, hardware type %4, and unspecified FQDN/Hostname because it matched entry %3 in the blocklist.
#Description
DHCP Services were denied to machine with hardware address , hardware type and unspecified FQDN/Hostname because it matched entry in the Deny List.
References #
Event ID 20099: DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and unspecified FQDN/HostnameHostName because it matched entry DenyFilter in the ...
#Description
DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and unspecified FQDN/HostnameHostName because it matched entry DenyFilter in the Deny List.
Message #
Fields #
| Name | Description |
|---|---|
MACAddress UnicodeString | |
HostName UnicodeString | |
DenyFilter UnicodeString | |
HWType UInt32 |
References #
Event ID 20100: [EVENT_FILTER_DENIED_NOT_IN_ALLOW_LIST_UNSPECIFIED] DHCP Services denied to machine with hardware address %1, hardware type %3, and unspecified FQDN/Hostname because it didn't match any entry in th...
#Description
DHCP Services were denied to machine with hardware address , hardware type and unspecified FQDN/Hostname because it did not match any entry in the Allow List.
References #
Event ID 20100: DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and unspecified FQDN/HostnameHostName because it did not match any entry ...
#Event ID 20161: [DHCPv4HA.AddrAllocationTriggered] Address allocation triggered for the failover relationship %1.
#Description
Address allocation triggered for the failover relationship .
References #
Event ID 20161: Address allocation triggered for the failover relationship RelationshipName.
#Event ID 20162
#Description
Scavenger started purging stateless entries.
Event ID 20162: Scavenger started purging stateless entries.
#Event ID 20163: [DHCPv4Stateless.ScavengerEnd] Scavenger finished purging stateless entries.
#Description
Scavenger finished purging stateless entries.
References #
Event ID 20164: [DHCPv4HA.TotalLeasesDeleted] The total leases deleted in scavenger are %1
#Description
The total leases deleted in scavenger are.
References #
Event ID 20164: The total leases deleted in scavenger are number.
#Event ID 20165: [DHCPv4HA.FailoverScopeDeleted] Scope %1 which was part of failover relationship %2 wasn't found in DHCP server database.
#Description
Scope which was part of failover relationship was not found in DHCP server database. Please restore the DHCP server database.
References #
Event ID 20165: Scope Server which was part of failover relationship RelationName was not found in DHCP server database.
#Event ID 20220: [DHCPv4.UpdateServerPolicyState] Policy %2 for server is %1.
#Description
Policy for server is .
References #
Event ID 20220: Policy PolicyName for server is String1.
#Event ID 20221: Policy PolicyName for scope IP_ScopeName is String1.
#Event ID 20222: [DHCPv4.UpdateServerPolicyExpr] The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.
#Description
The conditions for server policy have been set to . The conditions are grouped by logical operator .
References #
Event ID 20222: The conditions for server policy PolicyName have been set to String1.
#Event ID 20223: [DHCPv4.UpdateScopePolicyExpr] The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2.
#Description
The conditions for scope policy have been set to . The conditions are grouped by logical operator .
References #
Event ID 20223: The conditions for scope IP_ScopeName policy PolicyName have been set to String1.
#Event ID 20224
#Description
A new server wide IPv4 policy was created. The processing order of the policy is .
Fields #
| Name | Description |
|---|---|
PolicyName UnicodeString | |
ProcessingOrder UInt32 |
Event ID 20224: A new server wide IPv4 policy PolicyName was created.
#Event ID 20225
#Description
A new scope policy was created in scope . The processing order of the policy is .
Fields #
| Name | Description |
|---|---|
PolicyName UnicodeString | |
ProcessingOrder UInt32 | |
IP_ScopeName UnicodeString |
Event ID 20225: A new scope policy PolicyName was created in scope IP_ScopeName.
#Event ID 20226: [DHCPv4.DeleteServerPolicy] Policy %1 was deleted from server.
#Description
Policy was deleted from server.
References #
Event ID 20226: Policy PolicyName was deleted from server.
#Event ID 20227: [DHCPv4.DeleteScopePolicy] Policy %1 was deleted from scope %2.
#Description
Policy was deleted from scope .
References #
Event ID 20227: Policy PolicyName was deleted from scope IP_ScopeName.
#Event ID 20228: [DHCPv4.SetScopePolicyRange] The IP address range from %1 was set for the scope %3 policy %2.
#Description
The IP address range from was set for the scope policy .
References #
Event ID 20228: The IP address range from String1 was set for the scope IP_ScopeName policy PolicyName.
#Event ID 20229: [DHCPv4.RemoveScopePolicyRange] The IP address range from %1 was removed from the scope %3 policy %2.
#Description
The IP address range from was removed from the scope policy .
References #
Event ID 20229: The IP address range from String1 was removed from the scope IP_ScopeName policy PolicyName.
#Event ID 20230: [DHCPv4.SetServerPolicyOption] The value %2 was set for the option %1 for the server policy %3.
#Description
The value was set for the option for the server policy .
References #
Event ID 20230: The value OptionValue was set for the option OptionName for the server policy PolicyName.
#Event ID 20231: [DHCPv4.SetScopePolicyOption] The value %2 was set for the option %1 for the scope %4 policy %3.
#Description
The value was set for the option for the scope policy .
References #
Event ID 20231: The value OptionValue was set for the option OptionName for the scope IP_ScopeName policy PolicyName.
#Event ID 20232: [DHCPv4.UnsetServerPolicyOption] The value %2 was removed from the option %1 for the server policy %3.
#Description
The value was removed from the option for the server policy .
References #
Event ID 20232: The value OptionValue was removed from the option OptionName for the server policy PolicyName.
#Event ID 20233: [DHCPv4.UnsetScopePolicyOption] The value %2 was removed from the option %1 for the scope %4 policy %3.
#Description
The value was removed from the option for the scope policy .
References #
Event ID 20233: The value OptionValue was removed from the option OptionName for the scope IP_ScopeName policy PolicyName.
#Event ID 20234: [DHCPv4.UpdateServerPolicyName] Server policy %2 has been renamed to %1.
#Description
Server policy has been renamed to .
References #
Event ID 20234: Server policy PolicyName has been renamed to String1.
#Event ID 20235: [DHCPv4.UpdateScopePolicyName] Scope %3 policy %2 has been renamed to %1.
#Description
Scope policy has been renamed to .
References #
Event ID 20235: Scope IP_ScopeName policy PolicyName has been renamed to String1.
#Event ID 20236: [DHCPv4.UpdateServerPolicyDescription] Description of server policy %2 was set to %1.
#Description
Description of server policy was set to .
References #
Event ID 20236: Description of server policy PolicyName was set to String1.
#Event ID 20237: [DHCPv4.UpdateScopePolicyDescription] Description of scope %3 policy %2 was set to %1.
#Description
Description of scope policy was set to .
References #
Event ID 20237: Description of scope IP_ScopeName policy PolicyName was set to String1.
#Event ID 20238: [DHCPv4.UpdateServerPolicyProcOrder] Processing order of server policy %3 was changed to %1 from %2.
#Description
Processing order of server policy was changed to from .
References #
Event ID 20238: Processing order of server policy PolicyName was changed to Integer1 from Integer2.
#Event ID 20239: [DHCPv4.UpdateScopePolicyProcOrder] Processing order of scope %4 policy %3 was changed to %1 from %2.
#Description
Processing order of scope policy was changed to from .
References #
Event ID 20239: Processing order of scope IP_ScopeName policy PolicyName was changed to Integer1 from Integer2.
#Event ID 20240
#Fields #
| Name | Description |
|---|---|
Server1Name UnicodeString | |
Server2Name UnicodeString | |
RelationshipName UnicodeString | |
Mclt UInt32 | |
Percentage UInt32 | |
AutoSwitchoverInterval UInt32 |
Event ID 20240: A failover relationship has been created between servers Server1Name and Server2Name with the following configuration parameters: name: RelationshipName, mode: load balance, maxim...
#Event ID 20241: [DHCPv4.CreateFailoverRelationshipHotStandby] A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, mode: hot standby, maximum cl...
#References #
Event ID 20241: A failover relationship has been created between servers Server1Name and Server2Name with the following configuration parameters: name: RelationshipName, mode: hot standby, maximu...
#Event ID 20242: [DHCPv4.DeleteFailoverRelationship] Failover relationship %1 between %2 and %3 has been deleted.
#Description
Failover relationship between and has been deleted.
References #
Event ID 20242: Failover relationship RelationshipName between Server1Name and Server2Name has been deleted.
#Event ID 20243: [DHCPv4.AddScopeRelationship] Scope %1 has been added to the failover relationship %2 with server %3.
#Description
Scope has been added to the failover relationship with server .
References #
Event ID 20243: Scope ScopeAddress has been added to the failover relationship RelationshipName with server Server2Name.
#Event ID 20244: [DHCPv4.DeleteScopeRelationship] Scope %1 has been removed from the failover relationship %2 with server %3.
#Description
Scope has been removed from the failover relationship with server .
References #
Event ID 20244: Scope ScopeAddress has been removed from the failover relationship RelationshipName with server Server2Name.
#Event ID 20245: [DHCPv4.UpdateRelationshipParamMclt] The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.
#Description
The failover configuration parameter MCLT for failover relationship with server has been changed from seconds to seconds.
References #
Event ID 20245: The failover configuration parameter MCLT for failover relationship RelationshipName with server Server2Name has been changed from OldValue seconds to NewValue seconds.
#Event ID 20246: [DHCPv4.UpdateRelationshipParamAutoSwitchOverInterval] The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to...
#Description
The failover configuration parameter auto switch over interval for failover relationship with server has been changed from seconds to seconds.
References #
Event ID 20246: The failover configuration parameter auto switch over interval for failover relationship RelationshipName with server Server2Name has been changed from OldValue seconds to NewValue s...
#Description
The failover configuration parameter auto switch over interval for failover relationship RelationshipName with server Server2Name has been changed from OldValue seconds to NewValue seconds.
Message #
Fields #
| Name | Description |
|---|---|
RelationshipName UnicodeString | |
Server2Name UnicodeString | |
OldValue UInt32 | |
NewValue UInt32 |
References #
Event ID 20247: [DHCPv4.UpdateRelationshipParamPercentageHS] The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4.
#Description
The failover configuration parameter reserve address percentage for failover relationship with server has been changed from to .
References #
Event ID 20247: The failover configuration parameter reserve address percentage for failover relationship RelationshipName with server Server2Name has been changed from OldValue to NewValue.
#Event ID 20248: [DHCPv4.UpdateRelationshipParamPercentageLB] The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server.
#Description
The failover configuration parameter load balance percentage for failover relationship with server has been changed from to on this server.
References #
Event ID 20248: The failover configuration parameter load balance percentage for failover relationship RelationshipName with server Server2Name has been changed from OldValue to NewValue on this ser...
#Description
The failover configuration parameter load balance percentage for failover relationship RelationshipName with server Server2Name has been changed from OldValue to NewValue on this server.
Message #
Fields #
| Name | Description |
|---|---|
RelationshipName UnicodeString | |
Server2Name UnicodeString | |
OldValue UInt32 | |
NewValue UInt32 |
References #
Event ID 20249: [DHCPv4.UpdateRelationshipParamModeHStoLB] The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance.
#Description
The failover configuration parameter mode for failover relationship with server has been changed from hot standby to load balance.
References #
Event ID 20249: The failover configuration parameter mode for failover relationship RelationshipName with server Server2Name has been changed from hot standby to load balance.
#Event ID 20250: [DHCPv4.UpdateRelationshipParamModeLBtoHS] The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby.
#Description
The failover configuration parameter mode for failover relationship with server has been changed from load balance to hot standby.
References #
Event ID 20250: The failover configuration parameter mode for failover relationship RelationshipName with server Server2Name has been changed from load balance to hot standby.
#Event ID 20251: The failover state of server: Server for failover relationship: RelationName changed from: OldState to NewState.
#Event ID 20251: [DHCPv4.ChangeFailoverRelationState] The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.
#Description
The failover state of server: for failover relationship: changed from: to .
References #
Event ID 20252: The failover state of server: Server for failover relationship: RelationName changed from: OldState to NewState.
#Event ID 20252: [DHCPv4.ChangeFailoverRelationStateError] The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.
#Description
The failover state of server: for failover relationship: changed from: to .
References #
Event ID 20253: The server detected that it is out of time synchronization with partner server: Server for failover relationship: RelationName.
#Event ID 20253: [DHCPv4.FailoverServerTimeSync] The server detected that it's out of time synchronization with partner server: %1 for failover relationship: %2.
#Description
The server detected that it is out of time synchronization with partner server: for failover relationship: . The time is out of sync by: seconds .
References #
Event ID 20254: Server has established contact with failover partner server Server for relationship RelationName .
#Event ID 20254: [DHCPv4.FailoverCommUp] Server has established contact with failover partner server %1 for relationship %2.
#Description
Server has established contact with failover partner server for relationship .
References #
Event ID 20255: Server has lost contact with failover partner server Server for relationship RelationName .
#Event ID 20255: [DHCPv4.FailoverCommDown] Server has lost contact with failover partner server %1 for relationship %2.
#Description
Server has lost contact with failover partner server for relationship .
References #
Event ID 20256: Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20256: [DHCPv4.AuthFailedBndUpdMsgDigestFailedToCompare] Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message BINDING-UPDATE from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20257: Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20257: [DHCPv4.AuthFailedBndUpdMsgDigestNotConfigured] Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message BINDING-UPDATE from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20258: Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20258: [DHCPv4.AuthFailedBndUpdMsgDigestNotPresent] Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message BINDING-UPDATE from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20259: The failover state of server: Server for failover relationship: RelationName changed to : NewState.
#Event ID 20259: [DHCPv4.ChangeFailoverRelationStateNoPrevState] The failover state of server: %1 for failover relationship: %2 changed to: %3.
#Description
The failover state of server: for failover relationship: changed to : .
References #
Event ID 20260: The failover state of server: Server for failover relationship: RelationName changed to: NewState.
#Event ID 20260: [DHCPv4.ChangeFailoverRelationStateErrorNoPrevState] The failover state of server: %1 for failover relationship: %2 changed to: %3.
#Description
The failover state of server: for failover relationship: changed to: .
References #
Event ID 20261: Failover protocol message BINDING-ACK from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20261: [DHCPv4.AuthFailedBndAckMsgDigestFailedToCompare] Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message BINDING-ACK from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20262: Failover protocol message BINDING-ACK from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20262: [DHCPv4.AuthFailedBndAckMsgDigestNotConfigured] Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message BINDING-ACK from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20263: Failover protocol message BINDING-ACK from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20263: [DHCPv4.AuthFailedBndAckMsgDigestNotPresent] Failover protocol message BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message BINDING-ACK from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20264: Failover protocol message CONNECT from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20264: [DHCPv4.AuthFailedConnectMsgDigestFailedToCompare] Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message CONNECT from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20265: Failover protocol message CONNECT from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20265: [DHCPv4.AuthFailedConnectMsgDigestNotConfigured] Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message CONNECT from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20266: Failover protocol message CONNECT from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20266: [DHCPv4.AuthFailedConnectMsgDigestNotPresent] Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message CONNECT from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20267: Failover protocol message CONNECTACK from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20267: [DHCPv4.AuthFailedConnectAckMsgDigestFailedToCompare] Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message CONNECTACK from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20268: Failover protocol message CONNECTACK from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20268: [DHCPv4.AuthFailedConnectAckMsgDigestNotConfigured] Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message CONNECTACK from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20269: Failover protocol message CONNECTACK from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20269: [DHCPv4.AuthFailedConnectAckMsgDigestNotPresent] Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message CONNECTACK from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20270: Failover protocol message UPDREQALL from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20270: [DHCPv4.AuthFailedUpdReqAllMsgDigestFailedToCompare] Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message UPDREQALL from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20271: [DHCPv4.AuthFailedUpdReqAllMsgDigestNotConfigured] Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message UPDREQALL from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20272: Failover protocol message UPDREQALL from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20272: [DHCPv4.AuthFailedUpdReqAllMsgDigestNotPresent] Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message UPDREQALL from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20273: Failover protocol message UPDDONE from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20273: [DHCPv4.AuthFailedUpdDoneMsgDigestFailedToCompare] Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message UPDDONE from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20274: Failover protocol message UPDDONE from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20274: [DHCPv4.AuthFailedUpdDoneMsgDigestNotConfigured] Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message UPDDONE from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20275: Failover protocol message UPDDONE from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20275: [DHCPv4.AuthFailedUpdDoneMsgDigestNotPresent] Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message UPDDONE from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20276: Failover protocol message UPDREQ from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20276: [DHCPv4.AuthFailedUpdReqMsgDigestFailedToCompare] Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message UPDREQ from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20277: Failover protocol message UPDREQ from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20277: [DHCPv4.AuthFailedUpdReqMsgDigestNotConfigured] Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message UPDREQ from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20278: Failover protocol message UPDREQ from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20278: [DHCPv4.AuthFailedUpdReqMsgDigestNotPresent] Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message UPDREQ from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20279: Failover protocol message STATE from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20279: [DHCPv4.AuthFailedStateMsgDigestFailedToCompare] Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message STATE from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20280: Failover protocol message STATE from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20280: [DHCPv4.AuthFailedStateMsgDigestNotConfigured] Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message STATE from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20281: Failover protocol message STATE from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20281: [DHCPv4.AuthFailedStateMsgDigestNotPresent] Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message STATE from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20282: Failover protocol message CONTACT from server Server for failover relationship RelationName was rejected because message digest failed to compare.
#Event ID 20282: [DHCPv4.AuthFailedContactMsgDigestFailedToCompare] Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.
#Description
Failover protocol message CONTACT from server for failover relationship was rejected because message digest failed to compare.
References #
Event ID 20283: Failover protocol message CONTACT from server Server for failover relationship RelationName was rejected because message digest was not configured.
#Event ID 20283: [DHCPv4.AuthFailedContactMsgDigestNotConfigured] Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest wasn't configured.
#Description
Failover protocol message CONTACT from server for failover relationship was rejected because message digest was not configured.
References #
Event ID 20284: Failover protocol message CONTACT from server Server for failover relationship RelationName is rejected because message digest was not present.
#Event ID 20284: [DHCPv4.AuthFailedContactMsgDigestNotPresent] Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest wasn't present.
#Description
Failover protocol message CONTACT from server for failover relationship is rejected because message digest was not present.
References #
Event ID 20285: An invalid cryptographic algorithm Message was specified for failover message authentication in FailoverCryptoAlgorithm under registry key HKEY_LOCAL_MA...
#Event ID 20285: [DHCPv4.InvalidAlgorithmProvider] An invalid cryptographic algorithm %1 was specified for failover message authentication.
#References #
Event ID 20286: BINDING UPDATE message for IP address IpAddress could not be replicated to the partner server ServerName of failover relation RelationName as the internal BINDING UPDATE qu...
#Description
BINDING UPDATE message for IP address IpAddress could not be replicated to the partner server ServerName of failover relation RelationName as the internal BINDING UPDATE queue is full.
Message #
Fields #
| Name | Description |
|---|---|
IpAddress UInt32 | |
ServerName UnicodeString | |
RelationName UnicodeString |
References #
Event ID 20286: [DHCPv4.FailoverClientLeaseDropped] BINDING UPDATE message for IP address %1 couldn't be replicated to the partner server %2 of failover relation %3 as the internal BINDING UPDATE queue is full.
#Description
BINDING UPDATE message for IP address could not be replicated to the partner server of failover relation as the internal BINDING UPDATE queue is full.
References #
Event ID 20287: DHCP client request from ClientID was dropped since the applicable IP address ranges in scope/superscope ScopeName are out of available IP addresses.
#Event ID 20287: [DHCPv4.ClientRequestDropped] DHCP client request from %1 was dropped since the applicable IP address ranges in scope/superscope %2 are out of available IP addresses.
#References #
Event ID 20288: This DHCP server LocalServer has transitioned to a PARTNER DOWN state for the failover relationship RelationName and the MCLT period of Mclt seconds has expired.
#Event ID 20288
#Fields #
| Name | Description |
|---|---|
LocalServer UnicodeString | |
RelationName UnicodeString | |
Mclt UInt32 | |
PartnerServer UnicodeString |
Event ID 20289: [DHCPv4.SendBndUpdMessage] A BINDING-UPDATE message with transaction ID: %1 was sent for IP address: %2 with binding status: %3 to partner server: %4 for failover relationship: %5.
#Description
A BINDING-UPDATE message with transaction id: was sent for IP address: with binding status: to partner server: for failover relationship: .
References #
Event ID 20289: A BINDING-UPDATE message with transaction id: TransactionId was sent for IP address: IPAddress with binding status: BndStatus to partner server: PartnerServer for failover relationshi...
#Description
A BINDING-UPDATE message with transaction id: TransactionId was sent for IP address: IPAddress with binding status: BndStatus to partner server: PartnerServer for failover relationship: RelationName.
Message #
Fields #
| Name | Description |
|---|---|
TransactionId UInt32 | |
IPAddress UInt32 | |
BndStatus UnicodeString | |
PartnerServer UnicodeString | |
RelationName UnicodeString |
References #
Event ID 20290: [DHCPv4.RecvBndUpdMessage] A BINDING-UPDATE message with transaction ID: %1 was received for IP address: %2 with binding status: %3 from partner server: %4 for failover relationship: %5.
#Description
A BINDING-UPDATE message with transaction id: was received for IP address: with binding status: from partner server: for failover relationship: .
References #
Event ID 20290: A BINDING-UPDATE message with transaction id: TransactionId was received for IP address: IPAddress with binding status: BndStatus from partner server: PartnerServer for failover relat...
#Description
A BINDING-UPDATE message with transaction id: TransactionId was received for IP address: IPAddress with binding status: BndStatus from partner server: PartnerServer for failover relationship: RelationName.
Message #
Fields #
| Name | Description |
|---|---|
TransactionId UInt32 | |
IPAddress UInt32 | |
BndStatus UnicodeString | |
PartnerServer UnicodeString | |
RelationName UnicodeString |
References #
Event ID 20291: A BINDING-ACK message with transaction id: TransactionId was sent for IP address: IPAddress with reject reason: (BndStatus) to partner server: PartnerServer for failover relationship:...
#Description
A BINDING-ACK message with transaction id: TransactionId was sent for IP address: IPAddress with reject reason: (BndStatus) to partner server: PartnerServer for failover relationship: RelationName.
Message #
Fields #
| Name | Description |
|---|---|
TransactionId UInt32 | |
IPAddress UInt32 | |
BndStatus UnicodeString | |
PartnerServer UnicodeString | |
RelationName UnicodeString |
References #
Event ID 20291: [DHCPv4.SendBndAckMessageRejectReason] A BINDING-ACK message with transaction ID: %1 was sent for IP address: %2 with reject reason: (%3) to partner server: %4 for failover relationship: %5.
#Description
A BINDING-ACK message with transaction id: was sent for IP address: with reject reason: () to partner server: for failover relationship: .
References #
Event ID 20292: A BINDING-ACK message with transaction id: TransactionId was received for IP address: IPAddress with reject reason: (BndStatus ) from partner server: PartnerServer for failover relati...
#Description
A BINDING-ACK message with transaction id: TransactionId was received for IP address: IPAddress with reject reason: (BndStatus ) from partner server: PartnerServer for failover relationship: RelationName.
Message #
Fields #
| Name | Description |
|---|---|
TransactionId UInt32 | |
IPAddress UInt32 | |
BndStatus UnicodeString | |
PartnerServer UnicodeString | |
RelationName UnicodeString |
References #
Event ID 20292: [DHCPv4.RecvBndAckMessageRejectReason] A BINDING-ACK message with transaction ID: %1 was received for IP address: %2 with reject reason: (%3) from partner server: %4 for failover relationship: %5.
#Description
A BINDING-ACK message with transaction id: was received for IP address: with reject reason: ( ) from partner server: for failover relationship: .
References #
Event ID 20293: [DHCPv4.SendUpdReqMessage] A UPDREQ message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A UPDREQ message with transaction id: was sent to partner server: for failover relationship: .
References #
Event ID 20293: A UPDREQ message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20294: [DHCPv4.RecvUpdReqMessage] A UPDREQ message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.
#Description
A UPDREQ message with transaction id: was received from partner server: for failover relationship.
References #
Event ID 20294: A UPDREQ message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20295: [DHCPv4.SendUpdDoneMessage] A UPDDONE message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A UPDDONE message with transaction id: was sent to partner server: for failover relationship: .
References #
Event ID 20295: A UPDDONE message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20296: A UPDDONE message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20297: [DHCPv4.SendUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A UPDREQALL message with transaction id: was sent to partner server: for failover relationship.
References #
Event ID 20297: A UPDREQALL message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20298: [DHCPv4.RecvUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.
#Description
A UPDREQALL message with transaction id: was received from partner server: for failover relationship.
References #
Event ID 20298: A UPDREQALL message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20299: [DHCPv4.SendContactMessage] A CONTACT message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A CONTACT message with transaction id: was sent to partner server: for failover relationship: .
References #
Event ID 20299: A CONTACT message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20300: [DHCPv4.RecvContactMessage] A CONTACT message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.
#Description
A CONTACT message with transaction id: was received from partner server: for failover relationship: .
References #
Event ID 20300: A CONTACT message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20301: [DHCPv4.SendConnectMessage] A CONNECT message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A CONNECT message with transaction id: was sent to partner server: for failover relationship: .
References #
Event ID 20301: A CONNECT message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20302: [DHCPv4.RecvConnectMessage] A CONNECT message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.
#Description
A CONNECT message with transaction id: was received from partner server: for failover relationship: .
References #
Event ID 20302: A CONNECT message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20303: [DHCPv4.SendStateMessage] A STATE message with transaction ID: %1 was sent to partner server: %2 for failover relationship %3 with state: %4 and start time of state: %5.
#Description
A STATE message with transaction id: was sent to partner server : for failover relationship with state: and start time of state: .
References #
Event ID 20303: A STATE message with transaction id: TransactionId was sent to partner server : PartnerServer for failover relationship RelationName with state: state and start time of state: startTimeOfState.
#Event ID 20304: [DHCPv4.RecvStateMessage] A STATE message with transaction ID: %1 was received from partner server: %2 for failover relationship %3 with state: %4 and start time of state %5.
#Description
A STATE message with transaction id: was received from partner server : for failover relationship with state: and start time of state .
References #
Event ID 20304: A STATE message with transaction id: TransactionId was received from partner server : PartnerServer for failover relationship RelationName with state: state and start time of state startTimeOfState.
#Event ID 20305: [DHCPv4.SendConnectAckMessage] A CONNECTACK message with transaction ID %1 was sent to partner server: %2 for failover relationship: %3.
#Description
A CONNECTACK message with transaction id was sent to partner server : for failover relationship: .
References #
Event ID 20305: A CONNECTACK message with transaction id TransactionId was sent to partner server : PartnerServer for failover relationship: RelationName.
#Event ID 20306: [DHCPv4.RecvConnectAckMessage] A CONNECTACK message with transaction ID %1 was received from partner server: %2 for failover relationship: %3.
#Description
A CONNECTACK message with transaction id was received from partner server : for failover relationship: .
References #
Event ID 20306: A CONNECTACK message with transaction id TransactionId was received from partner server : PartnerServer for failover relationship: RelationName.
#Event ID 20307: [DHCPv4.SendBndAckMessageNoRejectReason] A BINDING-ACK message with transaction ID: %1 was sent for IP address: %2 to partner server: %3 for failover relationship: %4.
#Description
A BINDING-ACK message with transaction id: was sent for IP address: to partner server: for failover relationship: .
References #
Event ID 20307: A BINDING-ACK message with transaction id: TransactionId was sent for IP address: IPAddress to partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20308: [DHCPv4.RecvBndAckMessageNoRejectReason] A BINDING-ACK message with transaction ID: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4.
#Description
A BINDING-ACK message with transaction id: was received for IP address: from partner server: for failover relationship: .
References #
Event ID 20308: A BINDING-ACK message with transaction id: TransactionId was received for IP address: IPAddress from partner server: PartnerServer for failover relationship: RelationName.
#Event ID 20309: [DHCPv4.SendConnectAckMessageRejectReason] A CONNECTACK message with transaction ID %1 was sent to partner server: %2 for failover relationship: %3 with reject reason: %4.
#Description
A CONNECTACK message with transaction id was sent to partner server : for failover relationship: with reject reason: .
References #
Event ID 20309: A CONNECTACK message with transaction id TransactionId was sent to partner server : PartnerServer for failover relationship: RelationName with reject reason: state.
#Event ID 20310: [DHCPv4.RecvConnectAckMessageRejectReason] A CONNECTACK message with transaction ID %1 was received from partner server: %2 for failover relationship: %3 with reject reason: %4.
#Description
A CONNECTACK message with transaction id was received from partner server : for failover relationship: with reject reason: .
References #
Event ID 20310: A CONNECTACK message with transaction id TransactionId was received from partner server : PartnerServer for failover relationship: RelationName with reject reason: state.
#Event ID 20311: [DHCPv4.UpdateSharedSecret] The shared secret for failover relationship %2 with server %1 has been changed.
#Description
The shared secret for failover relationship with server has been changed.
References #
Event ID 20311: The shared secret for failover relationship Server2Name with server RelationshipName has been changed.
#Event ID 20312: [DHCPv4.EnabledSharedSecret] Message authentication for failover relationship %2 with server %1 has been enabled.
#Description
Message authentication for failover relationship with server has been enabled.
References #
Event ID 20312: Message authentication for failover relationship Server2Name with server RelationshipName has been enabled.
#Event ID 20313: [DHCPv4.DisabledSharedSecret] Message authentication for failover relationship %2 with server %1 has been disabled.
#Description
Message authentication for failover relationship with server has been disabled.
References #
Event ID 20313: Message authentication for failover relationship Server2Name with server RelationshipName has been disabled.
#Event ID 20315: [DHCPv4.UpdateScopePolicyDNSSuffix] DNSSuffix of scope %3 policy %2 was set to %1.
#Description
DNSSuffix of scope policy was set to .
References #
Event ID 20315: DNSSuffix of scope IP_ScopeName policy PolicyName was set to String1.
#Event ID 20316: [DHCPv4.UpdateServerPolicyDNSSuffix] DNSSuffix of server policy %2 was set to %1.
#Description
DNSSuffix of server policy was set to .
References #
Event ID 20316: DNSSuffix of server policy PolicyName was set to String1.
#Event ID 20317: Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Description
Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType. This is likely to be because the forward lookup zone for this record does not exist on the DNS server.
Message #
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20317
#Description
Forward record registration for IPv4 address and FQDN failed with error . This is likely to be because the forward lookup zone for this record does not exist on the DNS server.
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20318: Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Event ID 20318
#Description
Forward record registration for IPv4 address and FQDN failed with error .
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20319: Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).
#Event ID 20319
#Description
Forward record registration for IPv4 address and FQDN failed with error ().
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
Errorvalue UInt32 | |
operation UnicodeString |
Event ID 20320: PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Description
PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.
Message #
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20320
#Description
PTR record registration for IPv4 address and FQDN failed with error . This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20321
#Description
PTR record registration for IPv4 address and FQDN failed with error .
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20322: PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).
#Event ID 20322
#Description
PTR record registration for IPv4 address and FQDN failed with error ().
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
Errorvalue UInt32 | |
operation UnicodeString |
Event ID 20323: Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Description
Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType. This is likely to be because the forward lookup zone for this record does not exist on the DNS server.
Message #
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20323
#Description
Forward record registration for IPv6 address and FQDN failed with error . This is likely to be because the forward lookup zone for this record does not exist on the DNS server.
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20324: Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Event ID 20324
#Description
Forward record registration for IPv6 address and FQDN failed with error .
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20325: Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).
#Event ID 20325
#Description
Forward record registration for IPv6 address and FQDN failed with error ().
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
Errorvalue UInt32 | |
operation UnicodeString |
Event ID 20326: PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Description
PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.
Message #
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20326
#Description
PTR record registration for IPv6 address and FQDN failed with error . This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20327: PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.
#Event ID 20327
#Description
PTR record registration for IPv6 address and FQDN failed with error .
Fields #
| Name | Description |
|---|---|
IP_Name UnicodeString | |
FQDNName UnicodeString | |
ErrorType UnicodeString | |
operation UnicodeString |
Event ID 20328: PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).
#Provenance
ETW provider GUID 6d64f02c-a125-4dac-9a01-f0555b41ca84
Defined in dhcpssvc.dll, which carries the event manifest.
- WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02 — Manifest XML pack, 1.9 MB