detection.wiki

Microsoft-Windows-DHCP-Server

565 events across 7 channels

Event IDTitleChannel
70[DHCPv4.ScopeConfigured] Scope: %1 for IPv4 is Configured by %2.Operational
70Scope: IP_ScopeName for IPv4 is Configured by ClientName.Operational
71[DHCPv4.ScopeModified] Scope: %1 for IPv4 is Modified by %2.Operational
71Scope: IP_ScopeName for IPv4 is Modified by ClientName.Operational
72[DHCPv4.ScopeDeleted] Scope: %1 for IPv4 is Deleted by %2.Operational
72Scope: IP_ScopeName for IPv4 is Deleted by ClientName.Operational
73[DHCPv4.ScopeActivated] Scope: %1 for IPv4 is Activated by %2.Operational
73Scope: IP_ScopeName for IPv4 is Activated by ClientName.Operational
74[DHCPv4.ScopeDeActivated] Scope: %1 for IPv4 is Deactivated by %2.Operational
74Scope: IP_ScopeName for IPv4 is DeActivated by ClientName.Operational
75[DHCPv4.ScopeLeaseUpdate] Scope: %1 for IPv4 is Updated with Lease Duration: %2 …Operational
75Scope: IP_ScopeName for IPv4 is Updated with Lease Duration: ModifiedDuration …Operational
76[DHCPv4.ScopeOptionUpdate] Scope: %1 for IPv4 is Updated with Option Settings: …Operational
76Scope: IP_ScopeName for IPv4 is Updated with Option Settings: OptionName by …Operational
77[DHCPv4.ScopeDNSEnable] Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by …Operational
77Scope: IP_ScopeName for IPv4 is Enabled for DNS Dynamic updates by ClientName.Operational
78[DHCPv4.ScopeDNSDisable] Scope: %1 for IPv4 is Disabled for DNS Dynamic updates …Operational
78Scope: IP_ScopeName for IPv4 is Disabled for DNS Dynamic updates by ClientName.Operational
79[DHCPv4.ScopeDNSUpdate_Req_by_Client] Scope: %1 for IPv4 is Updated with DNS …Operational
79Scope: IP_ScopeName for IPv4 is Updated with DNS Settings by ClientName: to …Operational
80[DHCPv4.ScopeDNSUpdate_Always] Scope: %1 for IPv4 is Updated with DNS Settings …Operational
80Scope: IP_ScopeName for IPv4 is Updated with DNS Settings by ClientName: to …Operational
81[DHCPv4.ScopeDNSEnable_Discard] Scope: %1 for IPv4 is Enabled for DNS Settings …Operational
81Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to …Operational
82[DHCPv4.ScopeDNSDisable_Discard] Scope: %1 for IPv4 is Disabled for DNS Settings …Operational
82Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to …Operational
83[DHCPv4.ScopeDNSEnable_Update_Client_NoReq] Scope: %1 for IPv4 is Enabled for …Operational
83Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to …Operational
84[DHCPv4.ScopeDNSDisable_Update_Client_NoReq] Scope: %1 for IPv4 is Disabled for …Operational
84Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to …Operational
85[DHCPv4.ScopePBA_DeActivated] Policy based assignment has been disabled for …Operational
85Policy based assignment has been disabled for scope IP_ScopeName.Operational
86[DHCPv4.ScopePBA_Activated] Policy based assignment has been enabled for scope …Operational
86Policy based assignment has been enabled for scope IP_ScopeName.Operational
87[DHCPv4.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for …Operational
87Name Protection setting is Enabled on Scope: IP_Name for IPv4 by ClientName.Operational
88[DHCPv4.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for …Operational
88Name Protection setting is Disabled on Scope: IP_Name for IPv4 by ClientName.Operational
89[DHCPv4.ScopeSupportType] Scope: %1 for IPv4 is Updated with support type: %2 by …Operational
89Scope: IP_Name for IPv4 is Updated with support type: ModifiedSupportType by …Operational
90[DHCPv4.ScopeNAPEnabled] NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.Operational
90NAP Enforcement is Enabled on Scope: IP_ScopeName for IPv4 by ClientName.Operational
91[DHCPv4.ScopeNAPDisabled] NAP Enforcement is Disabled on Scope: %1 for IPv4 by …Operational
91NAP Enforcement is Disabled on Scope: IP_ScopeName for IPv4 by ClientName.Operational
92[DHCPv4.ScopeNAPProfileConfigured] NAP Profile is configured on Scope: %1 for …Operational
92NAP Profile is configured on Scope: IP_ScopeName for IPv4 with the following NAP …Operational
93[DHCPv4.ScopeNAPProfileModified] NAP Profile is Updated on Scope: %1 for IPv4 …Operational
93NAP Profile is Updated on Scope: IP_ScopeName for IPv4 with the following NAP …Operational
94[DHCPv4.ScopeNAPProfileDeleted] The following NAP Profile: %1 is deleted on …Operational
94The following NAP Profile: IP_ScopeName is deleted on Scope: NAP_ProfileName by …Operational
95[DHCPv4.MulticastScopeConfigured] Scope: %1 for Multicast IPv4 is Configured by …Operational
95Scope: IP_MulticastScopeName for Multicast IPv4 is Configured by ClientName.Operational
96[DHCPv4.MulticastScopeDeleted] Scope: %1 for Multicast IPv4 is Deleted by %2.Operational
96Scope: IP_MulticastScopeName for Multicast IPv4 is Deleted by ClientName.Operational
97Operational
97Scope: IP_ScopeName for IPv4 is Added in Superscope: IP_SuperScopeName by …Operational
98[DHCPv4.SuperScopeConfigured] SuperScope: %1 for IPv4 is Configured by %2.Operational
98SuperScope: IP_MulticastScopeName for IPv4 is Configured by ClientName.Operational
99[DHCPv4.SuperScopeDeleted] SuperScope: %1 for IPv4 is Deleted by %2.Operational
99SuperScope: IP_MulticastScopeName for IPv4 is Deleted by ClientName.Operational
100[DHCPv4.SuperScopeActivated] Scope: %1 within SuperScope: %2 for IPv4 is …Operational
100Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is Activated …Operational
101[DHCPv4.SuperScopeDeActivated] Scope: %1 within SuperScope: %2 for IPv4 is …Operational
101Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is DeActivated …Operational
102[DHCPv4.SuperScopeDeleteTemp] Scope: %1 for IPv4 is Removed in Superscope: %2 by …Operational
102Scope: IP_ScopeName for IPv4 is Removed in Superscope: IP_SuperScopeName by …Operational
103[DHCPv4.SuperScopeDeletePerm] Scope: %1 for IPv4 is Deleted in Superscope: %2 as …Operational
103Scope: IP_ScopeName for IPv4 is Deleted in Superscope: IP_SuperScopeName as well …Operational
104Operational
104Delay Time: UpdatedVal milliseconds for the OFFER message sent by Secondary …Operational
105[DHCPv4.ServerOptionUpdate] Server level option %1 for IPv4 has been updated by …Operational
105Server level option OptionName for IPv4 has been updated by ClientName.Operational
106[DHCPv4.ReservationConfigured] Reservation: %1 for IPv4 is Configured under …Operational
106Reservation: ReservationName for IPv4 is Configured under Scope IP_Name by …Operational
107[DHCPv4.ReservationDeleted] Reservation: %1 for IPv4 is Deleted under Scope %2 …Operational
107Reservation: ReservationName for IPv4 is Deleted under Scope IP_Name by …Operational
108[DHCPv4.ReservationDNSEnable] Reservation: %1 for IPv4 under Scope: %2 is …Operational
108Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS …Operational
109[DHCPv4.ReservationDNSDisable] Reservation: %1 for IPv4 under Scope: %2 is …Operational
109Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS …Operational
110[DHCPv4.ReservationDNSUpdate_Req_by_Client] Reservation: %1 for IPv4 under …Operational
110Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS …Operational
111[DHCPv4.ReservationDNSUpdate_Always] Reservation: %1 for IPv4 under Scope: %2 is …Operational
111Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS …Operational
112[DHCPv4.ReservationDNSEnable_Discard] Reservation: %1 for IPv4 under Scope: %2 …Operational
112Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS …Operational
113[DHCPv4.ReservationDNSDisable_Discard] Reservation: %1 for IPv4 under Scope: %2 …Operational
113Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS …Operational
114[DHCPv4.ReservationDNSEnableUpdate_No_Req_by_Client] Reservation: %1 for IPv4 …Operational
114Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS …Operational
115[DHCPv4.ReservationDNSDisableUpdate_No_Req_by_Client] Reservation: %1 for IPv4 …Operational
115Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS …Operational
116[DHCPv4.ReservationOptionUpdate] Reservation: %1 for IPv4 under Scope: %2 is …Operational
116Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with …Operational
117[DHCPv4.ServerPBA_DeActivated] Policy based assignment has been disabled at …Operational
117Policy based assignment has been disabled at server level.Operational
118[DHCPv4.ServerPBA_Activated] Policy based assignment has been enabled at server …Operational
118Policy based assignment has been enabled at server level.Operational
119[DHCPv4.ScopeExclusionAdded] Added exclusion IP Address range %1 in the Address …Operational
119Added exclusion IP Address range ExclusionRange in the Address Pool for IPv4 …Operational
120[DHCPv4.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the …Operational
120Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv4 …Operational
121[DHCPv4.ScopeEnableAllow] Link Layer based filtering is Enabled in the allowlist …Operational
121Link Layer based filtering is Enabled in the Allow List of the IPv4 by …Operational
122[DHCPv4.ScopeDisableAllow] Link Layer based filtering is Disabled in the …Operational
122Link Layer based filtering is Disabled in the Allow List of the IPv4 by …Operational
123[DHCPv4.ScopeAllow_AddFilter] Filter for physical address: %1, hardware type: %3 …Operational
123Filter for physical address: PhysicalAddress, hardware type: HWType added to the …Operational
124[DHCPv4.ScopeAllow_DeleteFilter] Filter for physical address: %1, hardware type: …Operational
124Filter for physical address: PhysicalAddress, hardware type: HWType removed from …Operational
125[DHCPv4.ScopeEnableDeny] Link Layer based filtering is Enabled in the blocklist …Operational
125Link Layer based filtering is Enabled in the Deny List of the IPv4 by …Operational
126[DHCPv4.ScopeDisableDeny] Link Layer based filtering is Disabled in the …Operational
126Link Layer based filtering is Disabled in the Deny List of the IPv4 by …Operational
127[DHCPv4.ScopeDeny_AddFilter] Filter for physical address: %1, hardware type: %3 …Operational
127Filter for physical address: PhysicalAddress, hardware type: HWType added to the …Operational
128[DHCPv4.ScopeDeny_DeleteFilter] Filter for physical address: %1, hardware type: …Operational
128Filter for physical address: PhysicalAddress, hardware type: HWType removed from …Operational
129Operational
129Scope: IP_ScopeName for IPv6 is Configured by ClientName.Operational
130[DHCPv6.ScopeDeleted] Scope: %1 for IPv6 is Deleted by %2.Operational
130Scope: IP_ScopeName for IPv6 is Deleted by ClientName.Operational
131[DHCPv6.ScopeActivated] Scope: %1 for IPv6 is Activated by %2.Operational
131Scope: IP_ScopeName for IPv6 is Activated by ClientName.Operational
132[DHCPv6.ScopeDeActivated] Scope: %1 for IPv6 is DeActivated by %2.Operational
132Scope: IP_ScopeName for IPv6 is DeActivated by ClientName.Operational
133[DHCPv6.ScopeLeasePreferredUpdate] Scope: %1 for IPv6 is Updated with Lease …Operational
133Scope: IP_ScopeName for IPv6 is Updated with Lease Preferred Lifetime: …Operational
134[DHCPv6.ScopeLeaseValidUpdate] Scope: %1 for IPv6 is Updated with Lease Valid …Operational
134Scope: IP_ScopeName for IPv6 is Updated with Lease Valid Lifetime: …Operational
135[DHCPv6.ScopeOptionUpdate] Scope: %1 for IPv6 is Updated with Option Setting: %2 …Operational
135Scope: IP_ScopeName for IPv6 is Updated with Option Setting: OptionName by …Operational
136[DHCPv6.ScopeDNSEnable] Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by …Operational
136Scope: IP_ScopeName for IPv6 is Enabled for DNS Dynamic updates by ClientName.Operational
137[DHCPv6.ScopeDNSDisable] Scope: %1 for IPv6 is Disabled for DNS Dynamic updates …Operational
137Scope: IP_ScopeName for IPv6 is Disabled for DNS Dynamic updates by ClientName.Operational
138[DHCPv6.ScopeDNSUpdate_Req_by_Client] Scope: %1 for IPv6 is Updated with DNS …Operational
138Scope: IP_ScopeName for IPv6 is Updated with DNS Settings by ClientName: to …Operational
139[DHCPv6.ScopeDNSUpdate_Always] Scope: %1 for IPv6 is Updated with DNS Settings …Operational
139Scope: IP_ScopeName for IPv6 is Updated with DNS Settings by ClientName: to …Operational
140[DHCPv6.ScopeDNSEnable_Discard] Scope: %1 for IPv6 is Enabled for DNS Settings …Operational
140Scope: IP_ScopeName for IPv6 is Enabled for DNS Settings by ClientName: to …Operational
141[DHCPv6.ScopeDNSDisable_Discard] Scope: %1 for IPv6 is Disabled for DNS Settings …Operational
141Scope: IP_ScopeName for IPv6 is Disabled for DNS Settings by ClientName: to …Operational
142[DHCPv6.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for …Operational
142Name Protection setting is Enabled on Scope: IP_Name for IPv6 by ClientName.Operational
143[DHCPv6.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for …Operational
143Name Protection setting is Disabled on Scope: IP_Name for IPv6 by ClientName.Operational
145[DHCPv6.ReservationConfigured] Reservation: %1 for IPv6 is Configured under …Operational
145Reservation: ReservationName for IPv6 is Configured under Scope IP_Name by …Operational
147[DHCPv6.ReservationDeleted] Reservation: %1 for IPv6 is Deleted under Scope %2 …Operational
147Reservation: ReservationName for IPv6 is Deleted under Scope IP_Name by …Operational
148[DHCPv6.ReservationDNSEnable] Reservation: %1 for IPv6 under Scope: %2 is …Operational
148Reservation: ReservationName for IPv6 under Scope: IP_Name is Enabled for DNS …Operational
149[DHCPv6.ReservationDNSDisable] Reservation: %1 for IPv6 under Scope: %2 is …Operational
149Reservation: ReservationName for IPv6 under Scope: IP_Name is Disabled for DNS …Operational
150[DHCPv6.ReservationDNSUpdate_Req_by_Client] Reservation: %1 for IPv6 under …Operational
150Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS …Operational
151[DHCPv6.ReservationDNSUpdate_Always] Reservation: %1 for IPv6 under Scope: %2 is …Operational
151Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS …Operational
152[DHCPv6.ReservationDNSEnable_Discard] Reservation: %1 for IPv6 under Scope: %2 …Operational
152Reservation: ReservationName for IPv6 under Scope: IP_Name is Enabled for DNS …Operational
153[DHCPv6.ReservationDNSDisable_Discard] Reservation: %1 for IPv6 under Scope: %2 …Operational
153Reservation: ReservationName for IPv6 under Scope: IP_Name is Disabled for DNS …Operational
154[DHCPv6.ReservationOptionUpdate] Reservation: %1 for IPv6 under Scope: %2 is …Operational
154Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with …Operational
155[DHCPv6.ScopeExclusionAdded] Added exclusion IP Address range %1 in the Address …Operational
155Added exclusion IP Address range ExclusionRange in the Address Pool for IPv6 …Operational
156[DHCPv6.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the …Operational
156Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv6 …Operational
157[DHCPv6.ScopeModified] Scope: %1 for IPv6 is Modified by %2.Operational
157Scope: IP_ScopeName for IPv6 is Modified by ClientName.Operational
158[DHCPv6.ScopeStatelessEnabled] DHCPv6 Stateless client inventory has been …Operational
158DHCPv6 Stateless client inventory has been enabled for the scope IP_ScopeName.Operational
159[DHCPv6.ScopeStatelessDisabled] DHCPv6 Stateless client inventory has been …Operational
159DHCPv6 Stateless client inventory has been disabled for the scope IP_ScopeName.Operational
160[DHCPv6.ServerStatelessEnabled] DHCPv6 Stateless client inventory has been …Operational
160DHCPv6 Stateless client inventory has been enabled for the server.Operational
161[DHCPv6.ServerStatelessDisabled] DHCPv6 Stateless client inventory has been …Operational
161DHCPv6 Stateless client inventory has been disabled for the server.Operational
162[DHCPv6.ScopeStatelessPurgeInterval] Purge time interval for DHCPv6 stateless …Operational
162Purge time interval for DHCPv6 stateless client inventory for scope IP_ScopeName …Operational
163[DHCPv6.ServerStatelessPurgeInterval] Purge time interval for DHCPv6 stateless …Operational
163Purge time interval for DHCPv6 stateless client inventory for server has been …Operational
164Operational
164Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to …Operational
165[DHCPv4.ScopeDNSDisable_DisablePtrUpdates] Scope: %1 for IPv4 is Disabled for …Operational
165Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to …Operational
166[DHCPv6.ServerOptionUpdate] Server level option %1 for IPv6 has been updated by …Operational
166Server level option OptionName for IPv6 has been updated by ClientName.Operational
167Operational
167Server level option OptionName for IPv4 has been removed by ClientName.Operational
168Operational
168Option setting: OptionName has been removed from IPv4 scope: IP_ScopeName by …Operational
169Operational
169Option setting: OptionName has been removed from the reservation: …Operational
170Operational
170Server level option OptionName for IPv6 has been removed by ClientName.Operational
171Operational
171Option setting: OptionName has been removed from IPv6 scope: IP_ScopeName by …Operational
172Operational
172Option setting: OptionName has been removed from the reservation: …Operational
1000[EVENT_SERVER_UNKNOWN_OPTION] The DHCP service received the unknown option %1, …Operational
1001[EVENT_SERVER_FAILED_REGISTER_SC] The DHCP service failed to register with …Operational
1002[EVENT_SERVER_INIT_DATA_FAILED] The DHCP service failed to initialize its global …Operational
1003[EVENT_SERVER_INIT_REGISTRY_FAILED] The DHCP service failed to initialize its …Operational
1004[EVENT_SERVER_INIT_DATABASE_FAILED] The DHCP service failed to initialize the …Operational
1005[EVENT_SERVER_INIT_WINSOCK_FAILED] The DHCP service failed to initialize Winsock …Operational
1006[EVENT_SERVER_INIT_RPC_FAILED] The DHCP service failed to start as an RPC …Operational
1007[EVENT_SERVER_INIT_SOCK_FAILED] The DHCP service failed to initialize Winsock …Operational
1008[EVENT_SERVER_SHUTDOWN] The DHCP service is shutting down due to the following …Operational
1009[EVENT_SERVER_CLIENT_CLEANUP] The DHCP service encountered the following error …Operational
1010[EVENT_SERVER_DATABASE_CLEANUP] The DHCP service encountered the following error …Operational
1011[EVENT_SERVER_LEASE_NACK] The DHCP service issued a NACK to the client, %2, for …Operational
1012[EVENT_SERVER_LEASE_DECLINED] The DHCP client, %2, declined the address %1.Operational
1013[EVENT_SERVER_LEASE_RELEASE] The DHCP Client, %2, released the address %1.Operational
1016[EVENT_SERVER_DATABASE_BACKUP] The DHCP service encountered the following error …Operational
1017[EVENT_SERVER_CONFIG_BACKUP] The DHCP service encountered the following error …Operational
1018[EVENT_SERVER_DATABASE_RESTORE_FAILED] The DHCP service failed to restore the …Operational
1019[EVENT_SERVER_CONFIG_RESTORE_FAILED] The DHCP service failed to restore the DHCP …Operational
1020[EVENT_SERVER_LOW_ADDRESS_WARNING] Scope, %1, is %2 percent full with only %3 IP …Operational
1021[EVENT_SERVER_LOAD_JET_FAILED] The DHCP service couldn't load the JET database …Operational
1022[EVENT_SERVER_JET_CONV_REQUIRED] The DHCP service couldn't use the database.Operational
1023[EVENT_SERVER_JET_CONV_IN_PROGRESS] The DHCP service will now terminate because …Operational
1024[EVENT_SERVER_INIT_AND_READY] The DHCP service has initialized and is ready.Operational
1025[EVENT_SERVER_BOOT_FILE_TABLE] The DHCP service was unable to read the BOOTP …Operational
1026[EVENT_SERVER_BOOT_FILE_NAME] The DHCP service was unable to read the global …Operational
1027[EVENT_SERVER_AUDIT_LOG_APPEND_FAILED] The audit log file can't be appended.Operational
1028[EVENT_SERVER_INIT_AUDIT_LOG_FAILED] The DHCP service failed to initialize the …Operational
1029[EVENT_SERVER_PING_FAILED] The DHCP service was unable to ping for a new IP …Operational
1030[EVENT_SERVER_MOVE_AUDIT_LOG_FAILED] The audit log file couldn't be backed up.Operational
1031[EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll …Operational
1032[EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has …Operational
1033[EVENT_SERVER_CALLOUT_LOAD_SUCCESS] The DHCP service has successfully loaded one …Operational
1034[EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or …Operational
1035[EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service was unable to create or …Operational
1036[EVENT_SERVER_ADMIN_GROUP_ERROR] The DHCP server was unable to create or look up …Operational
1037[EVENT_SERVER_CLEANUP_STARTED] The DHCP service has started to clean up the …Operational
1038[EVENT_SERVER_IPCLEANUP_FINISHED] The DHCP service has cleaned up the database …Operational
1039[EVENT_SERVER_MCASTCLEANUP_FINISHED] The DHCP service has cleaned up the …Operational
1040[EVENT_SERVER_DATABASE_RESTORE_SUCCEEDED] The DHCP service successfully restored …Operational
1041[DHCP_ROGUE_EVENT_NO_NETWORK] The DHCP service isn't servicing any DHCPv4 …Operational
1042[DHCP_ROGUE_EVENT_UNAUTHORIZED_INFO] The DHCP/BINL service running on this …Operational
1043[DHCP_ROGUE_EVENT_STARTED] The DHCP/BINL service on the local machine has …Operational
1044[DHCP_ROGUE_EVENT_STARTED_DOMAIN] The DHCP/BINL service on the local machine, …Operational
1045[DHCP_ROGUE_EVENT_STOPPED] The DHCP/BINL service on the local machine has …Operational
1046[DHCP_ROGUE_EVENT_STOPPED_DOMAIN] The DHCP/BINL service on the local machine, …Operational
1047[DHCP_ROGUE_EVENT_JUST_UPGRADED] The DHCP/BINL service on the local machine has …Operational
1048[DHCP_ROGUE_EVENT_JUST_UPGRADED_DOMAIN] The DHCP/BINL Service on the local …Operational
1049[DHCP_ROGUE_EVENT_CANT_FIND_DOMAIN] The DHCP/BINL service on the local machine …Operational
1050[DHCP_ROGUE_EVENT_NETWORK_FAILURE] The DHCP/BINL service on the local machine …Operational
1051[DHCP_ROGUE_EVENT_UNAUTHORIZED] The DHCP/BINL service has determined that it …Operational
1052[DHCP_ROGUE_EVENT_OTHER_SERVER] The DHCP/BINL service on this workgroup server …Operational
1053[DHCP_ROGUE_EVENT_SAM_OTHER_SERVER] The DHCP/BINL service has encountered …Operational
1054[DHCP_ROGUE_EVENT_SHUTDOWN] The DHCP/BINL service on this computer is shutting …Operational
1055[DHCP_EVENT_DNS_REGPARAMS_FAILURE] The DHCP service was unable to impersonate …Operational
1056[DHCP_EVENT_NO_DNSCREDENTIALS_ON_DC] The DHCP service has detected that it's …Operational
1057[EVENT_SERVER_DATABASE_CONVERSION] The DHCP service was unable to convert the …Operational
1058[EVENT_SERVER_INIT_CONFIG_FAILED] The DHCP service failed to initialize its …Operational
1059[VENT_SERVER_COULDNT_SEE_DS] The DHCP service failed to see a directory server …Operational
1060[EVENT_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCP service was unable to …Operational
1061[EVENT_SERVER_BACKUP_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access …Operational
1062[EVENT_SERVER_DB_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path …Operational
1063[EVENT_SERVER_SCOPE_FULL] There are no IP addresses available for lease in the …Operational
1064[EVENT_SERVER_BOOTP_FULL] There are no IP addresses available for BOOTP clients …Operational
1065[EVENT_SERVER_ORPHONED_ENTRIES_DELETED] There were some orphaned entries deleted …Operational
1144[EVENT_SERVER_NEED_STATIC_IP] This computer has at least one dynamically …Operational
1338[EVENT_SERVER_OFFER_QUEUE_FULL] The number of pending DHCPOFFER messages for …Operational
1339[EVENT_SERVER_OFFER_QUEUE_FUNCTIONAL] The number pending DHCPOFFER messages for …Operational
1340[EVENT_SERVER_DNSDHCID_FAIL] The DNS registration for DHCPv4 Client IP address …Operational
1341[EVENT_SERVER_POLICY_RANGES_FULL] There are no IP addresses available for lease …Operational
1342[EVENT_SERVER_RESIDUAL_RANGES_FULL] IP address range of scope %1 is out of IP …Operational
1343[EVENT_SERVER_POLICY_RANGES_LOW_ADDRESS_WARNING] IP address range(s) for the …Operational
1344[EVENT_SERVER_DNS_VALIDATION_FAILED] The DNS IP Address %1 isn't a valid DNS …Operational
1376[EVENT_SERVER_RESIDUAL_RANGES_LOW_ADDRESS_WARNING] IP address range of scope %1 …Operational
1377[EVENT_SERVER_SUPERSCOPE_LOW_ADDRESS_WARNING] SuperScope, %1, is %2 percent full …Operational
10000[EVENT_DHCPV6_ADDERESS_NACKED] DHCPv6 confirmation has been declined because the …Operational
10001[EVENT_DHCPV6_REQUEST_RECEIVED_FOR_ADDRESSES_NOT_LEASED] Renew, rebind, or …Operational
10002[EVENT_DHCPV6_SERVER_UNKNOWN_OPTION] DHCPv6 service received the unknown option …Operational
10003[EVENT_DHCPV6_SERVER_SCOPE_FULL] There are no IPv6 addresses available to lease …Operational
10004[EVENT_DHCPV6_SERVER_LEASE_DECLINED] The DHCPv6 client, %2, declined the address …Operational
10005[EVENT_DHCPV6_SERVER_LOW_ADDRESS_WARNING] DHCPv6 Scope serving the network with …Operational
10006[EVENT_DHCPV6_CLIENT_DELETE] A DHCPv6 client %1 has been deleted from DHCPv6 …Operational
10007[EVENT_DHCPV6_DROP_TIMEOUT] A DHCPv6 message that was in the queue for more than …Operational
10008[EVENT_DHCPV6_DROP_INVALID] An invalid DHCPv6 message has been dropped.Operational
10009[EVENT_DHCPV6_DROP_WRONG_SERVER] A DHCPv6 message that wasn't meant for this …Operational
10010[EVENT_DHCPV6_DROP_UNICAST] DHCPv6 message has been dropped because it was …Operational
10011[EVENT_DHCPV6_SERVER_AUDIT_LOG_APPEND_FAILED] DHCPv6 audit log file can't be …Operational
10012[EVENT_DHCPV6_DROP_UNAUTH] A DHCPv6 message has been dropped because the server …Operational
10013[EVENT_DHCPv6_SERVER_INIT_AUDIT_LOG_FAILED] The DHCPv6 service failed to …Operational
10014[EVENT_DHCPV6_SERVER_MOVE_AUDIT_LOG_FAILED] DHCPv6 audit log file couldn't be …Operational
10015[EVENT_DHCPV6_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCPv6 service was unable …Operational
10016[EVENT_DHCPV6_SERVER_INIT_WINSOCK_FAILED] The DHCPv6 service failed to …Operational
10017[EVENT_DHCPV6_NO_DNSCREDENTIALS_ON_DC] The DHCPv6 service has detected that it's …Operational
10018[EVENT_DHCPV6_SERVER_INTERFACE_NOTIFICATION] The DHCPv6 Server failed to receive …Operational
10019[EVENT_DHCPV6_SERVER_INIT_CONFIG_FAILED] The DHCPv6 service failed to initialize …Operational
10020[EVENT_DHCPV6_SERVER_NEED_STATIC_IP] This computer has at least one dynamically …Operational
10021[EVENT_DHCPV6_SERVER_INIT_DATABASE_FAILED] DHCPv6 service failed to initialize …Operational
10022[EVENT_DHCPV6_SERVER_INIT_AND_READY] The DHCPv6 service has initialized and is …Operational
10023[EVENT_DHCPV6_PORT_UNAVAILABLE] DHCPv6 Server is unable to bind to UDP port …Operational
10024[ERROR_LAST_DHCPV6_SERVER_ERROR] ERROR_LAST_DHCPV6_SERVER_ERROROperational
10025[EVENT_DHCPV6_DNSDHCID_FAIL] The DNS registration for DHCPv6 Client IPv6 address …Operational
20035[EVENT_SERVER_INTERFACE_NOTIFICATION] %1 %3Operational
20058[DHCPv4HA.BndUpd] %1 %3Operational
20058[DHCPv4HA.BndUpd] RelationshipName PktContentsSystem
20059[DHCPv4HA.BndAck] %1 %3Operational
20059[DHCPv4HA.BndAck] RelationshipName PktContentsSystem
20060[DHCPv4HA.Connect] %1 %3Operational
20060[DHCPv4HA.Connect] RelationshipName PktContentsSystem
20061[DHCPv4HA.ConnectAck] %1 %3Operational
20061[DHCPv4HA.ConnectAck] RelationshipName PktContentsSystem
20062[DHCPv4HA.UpdReqAll] %1 %3Operational
20062[DHCPv4HA.UpdReqAll] RelationshipName PktContentsSystem
20063[DHCPv4HA.UpdDone] %1 %3Operational
20063[DHCPv4HA.UpdDone] RelationshipName PktContentsSystem
20064[DHCPv4HA.UpdReq] %1 %3Operational
20064[DHCPv4HA.UpdReq] RelationshipName PktContentsSystem
20065[DHCPv4HA.State] %1 %3Operational
20065[DHCPv4HA.State] RelationshipName PktContentsSystem
20066[DHCPv4HA.Contact] %1 %3Operational
20066[DHCPv4HA.Contact] RelationshipName PktContentsSystem
20067[DHCPv4HA.Disconnect] %1 %3Operational
20067[DHCPv4HA.Disconnect] RelationshipName PktContentsSystem
20068[DHCPv4HA.ScavengerStart] Scavenger started.Operational
20068Scavenger started.System
20069[DHCPv4HA.ScavengerEnd] Scavenger ended.Operational
20069Scavenger ended.System
20090[EVENT_DHCP_PORT_UNAVAILABLE] DHCP Server is unable to bind to UDP port number …Operational
20096[EVENT_FILTER_DENIED_IN_DENY_LIST] DHCP Services denied to machine with hardware …Operational
20096DHCP Services were denied to machine with hardware address MACAddress, hardware …FilterNotifications
20097[EVENT_FILTER_DENIED_NOT_IN_ALLOW_LIST] DHCP Services denied to machine with …Operational
20097DHCP Services were denied to machine with hardware address MACAddress, hardware …FilterNotifications
20098[EVENT_FILTER_EMPTY_ALLOW_LIST] No DHCP clients are being served, as the …Operational
20099[EVENT_FILTER_DENIED_IN_DENY_LIST_UNSPECIFIED] DHCP Services denied to machine …Operational
20099DHCP Services were denied to machine with hardware address MACAddress, hardware …FilterNotifications
20100[EVENT_FILTER_DENIED_NOT_IN_ALLOW_LIST_UNSPECIFIED] DHCP Services denied to …Operational
20100DHCP Services were denied to machine with hardware address MACAddress, hardware …FilterNotifications
20161[DHCPv4HA.AddrAllocationTriggered] Address allocation triggered for the failover …Operational
20161Address allocation triggered for the failover relationship RelationshipName.System
20162Operational
20162Scavenger started purging stateless entries.System
20163[DHCPv4Stateless.ScavengerEnd] Scavenger finished purging stateless entries.Operational
20163Scavenger finished purging stateless entries.System
20164[DHCPv4HA.TotalLeasesDeleted] The total leases deleted in scavenger are %1Operational
20164The total leases deleted in scavenger are number.System
20165[DHCPv4HA.FailoverScopeDeleted] Scope %1 which was part of failover relationship …Operational
20165Scope Server which was part of failover relationship RelationName was not found …System
20220[DHCPv4.UpdateServerPolicyState] Policy %2 for server is %1.Operational
20220Policy PolicyName for server is String1.Operational
20221[DHCPv4.UpdateScopePolicyState] Policy %2 for scope %3 is %1.Operational
20221Policy PolicyName for scope IP_ScopeName is String1.Operational
20222[DHCPv4.UpdateServerPolicyExpr] The conditions for server policy %3 have been …Operational
20222The conditions for server policy PolicyName have been set to String1.Operational
20223[DHCPv4.UpdateScopePolicyExpr] The conditions for scope %4 policy %3 have been …Operational
20223The conditions for scope IP_ScopeName policy PolicyName have been set to …Operational
20224Operational
20224A new server wide IPv4 policy PolicyName was created.Operational
20225Operational
20225A new scope policy PolicyName was created in scope IP_ScopeName.Operational
20226[DHCPv4.DeleteServerPolicy] Policy %1 was deleted from server.Operational
20226Policy PolicyName was deleted from server.Operational
20227[DHCPv4.DeleteScopePolicy] Policy %1 was deleted from scope %2.Operational
20227Policy PolicyName was deleted from scope IP_ScopeName.Operational
20228[DHCPv4.SetScopePolicyRange] The IP address range from %1 was set for the scope …Operational
20228The IP address range from String1 was set for the scope IP_ScopeName policy …Operational
20229[DHCPv4.RemoveScopePolicyRange] The IP address range from %1 was removed from …Operational
20229The IP address range from String1 was removed from the scope IP_ScopeName policy …Operational
20230[DHCPv4.SetServerPolicyOption] The value %2 was set for the option %1 for the …Operational
20230The value OptionValue was set for the option OptionName for the server policy …Operational
20231[DHCPv4.SetScopePolicyOption] The value %2 was set for the option %1 for the …Operational
20231The value OptionValue was set for the option OptionName for the scope …Operational
20232[DHCPv4.UnsetServerPolicyOption] The value %2 was removed from the option %1 for …Operational
20232The value OptionValue was removed from the option OptionName for the server …Operational
20233[DHCPv4.UnsetScopePolicyOption] The value %2 was removed from the option %1 for …Operational
20233The value OptionValue was removed from the option OptionName for the scope …Operational
20234[DHCPv4.UpdateServerPolicyName] Server policy %2 has been renamed to %1.Operational
20234Server policy PolicyName has been renamed to String1.Operational
20235[DHCPv4.UpdateScopePolicyName] Scope %3 policy %2 has been renamed to %1.Operational
20235Scope IP_ScopeName policy PolicyName has been renamed to String1.Operational
20236[DHCPv4.UpdateServerPolicyDescription] Description of server policy %2 was set …Operational
20236Description of server policy PolicyName was set to String1.Operational
20237[DHCPv4.UpdateScopePolicyDescription] Description of scope %3 policy %2 was set …Operational
20237Description of scope IP_ScopeName policy PolicyName was set to String1.Operational
20238[DHCPv4.UpdateServerPolicyProcOrder] Processing order of server policy %3 was …Operational
20238Processing order of server policy PolicyName was changed to Integer1 from …Operational
20239[DHCPv4.UpdateScopePolicyProcOrder] Processing order of scope %4 policy %3 was …Operational
20239Processing order of scope IP_ScopeName policy PolicyName was changed to Integer1 …Operational
20240Operational
20240A failover relationship has been created between servers Server1Name and …Operational
20241[DHCPv4.CreateFailoverRelationshipHotStandby] A failover relationship has been …Operational
20241A failover relationship has been created between servers Server1Name and …Operational
20242[DHCPv4.DeleteFailoverRelationship] Failover relationship %1 between %2 and %3 …Operational
20242Failover relationship RelationshipName between Server1Name and Server2Name has …Operational
20243[DHCPv4.AddScopeRelationship] Scope %1 has been added to the failover …Operational
20243Scope ScopeAddress has been added to the failover relationship RelationshipName …Operational
20244[DHCPv4.DeleteScopeRelationship] Scope %1 has been removed from the failover …Operational
20244Scope ScopeAddress has been removed from the failover relationship …Operational
20245[DHCPv4.UpdateRelationshipParamMclt] The failover configuration parameter MCLT …Operational
20245The failover configuration parameter MCLT for failover relationship …Operational
20246[DHCPv4.UpdateRelationshipParamAutoSwitchOverInterval] The failover …Operational
20246The failover configuration parameter auto switch over interval for failover …Operational
20247[DHCPv4.UpdateRelationshipParamPercentageHS] The failover configuration …Operational
20247The failover configuration parameter reserve address percentage for failover …Operational
20248[DHCPv4.UpdateRelationshipParamPercentageLB] The failover configuration …Operational
20248The failover configuration parameter load balance percentage for failover …Operational
20249[DHCPv4.UpdateRelationshipParamModeHStoLB] The failover configuration parameter …Operational
20249The failover configuration parameter mode for failover relationship …Operational
20250[DHCPv4.UpdateRelationshipParamModeLBtoHS] The failover configuration parameter …Operational
20250The failover configuration parameter mode for failover relationship …Operational
20251The failover state of server: Server for failover relationship: RelationName …DhcpAdminEvents
20251[DHCPv4.ChangeFailoverRelationState] The failover state of server: %1 for …Operational
20252The failover state of server: Server for failover relationship: RelationName …DhcpAdminEvents
20252[DHCPv4.ChangeFailoverRelationStateError] The failover state of server: %1 for …Operational
20253The server detected that it is out of time synchronization with partner server: …DhcpAdminEvents
20253[DHCPv4.FailoverServerTimeSync] The server detected that it's out of time …Operational
20254Server has established contact with failover partner server Server for …DhcpAdminEvents
20254[DHCPv4.FailoverCommUp] Server has established contact with failover partner …Operational
20255Server has lost contact with failover partner server Server for relationship …DhcpAdminEvents
20255[DHCPv4.FailoverCommDown] Server has lost contact with failover partner server …Operational
20256Failover protocol message BINDING-UPDATE from server Server for failover …DhcpAdminEvents
20256[DHCPv4.AuthFailedBndUpdMsgDigestFailedToCompare] Failover protocol message …Operational
20257Failover protocol message BINDING-UPDATE from server Server for failover …DhcpAdminEvents
20257[DHCPv4.AuthFailedBndUpdMsgDigestNotConfigured] Failover protocol message …Operational
20258Failover protocol message BINDING-UPDATE from server Server for failover …DhcpAdminEvents
20258[DHCPv4.AuthFailedBndUpdMsgDigestNotPresent] Failover protocol message …Operational
20259The failover state of server: Server for failover relationship: RelationName …DhcpAdminEvents
20259[DHCPv4.ChangeFailoverRelationStateNoPrevState] The failover state of server: %1 …Operational
20260The failover state of server: Server for failover relationship: RelationName …DhcpAdminEvents
20260[DHCPv4.ChangeFailoverRelationStateErrorNoPrevState] The failover state of …Operational
20261Failover protocol message BINDING-ACK from server Server for failover …DhcpAdminEvents
20261[DHCPv4.AuthFailedBndAckMsgDigestFailedToCompare] Failover protocol message …Operational
20262Failover protocol message BINDING-ACK from server Server for failover …DhcpAdminEvents
20262[DHCPv4.AuthFailedBndAckMsgDigestNotConfigured] Failover protocol message …Operational
20263Failover protocol message BINDING-ACK from server Server for failover …DhcpAdminEvents
20263[DHCPv4.AuthFailedBndAckMsgDigestNotPresent] Failover protocol message …Operational
20264Failover protocol message CONNECT from server Server for failover relationship …DhcpAdminEvents
20264[DHCPv4.AuthFailedConnectMsgDigestFailedToCompare] Failover protocol message …Operational
20265Failover protocol message CONNECT from server Server for failover relationship …DhcpAdminEvents
20265[DHCPv4.AuthFailedConnectMsgDigestNotConfigured] Failover protocol message …Operational
20266Failover protocol message CONNECT from server Server for failover relationship …DhcpAdminEvents
20266[DHCPv4.AuthFailedConnectMsgDigestNotPresent] Failover protocol message CONNECT …Operational
20267Failover protocol message CONNECTACK from server Server for failover …DhcpAdminEvents
20267[DHCPv4.AuthFailedConnectAckMsgDigestFailedToCompare] Failover protocol message …Operational
20268Failover protocol message CONNECTACK from server Server for failover …DhcpAdminEvents
20268[DHCPv4.AuthFailedConnectAckMsgDigestNotConfigured] Failover protocol message …Operational
20269Failover protocol message CONNECTACK from server Server for failover …DhcpAdminEvents
20269[DHCPv4.AuthFailedConnectAckMsgDigestNotPresent] Failover protocol message …Operational
20270Failover protocol message UPDREQALL from server Server for failover relationship …DhcpAdminEvents
20270[DHCPv4.AuthFailedUpdReqAllMsgDigestFailedToCompare] Failover protocol message …Operational
20271Failover protocol message UPDREQALL from server Server for failover relationship …DhcpAdminEvents
20271[DHCPv4.AuthFailedUpdReqAllMsgDigestNotConfigured] Failover protocol message …Operational
20272Failover protocol message UPDREQALL from server Server for failover relationship …DhcpAdminEvents
20272[DHCPv4.AuthFailedUpdReqAllMsgDigestNotPresent] Failover protocol message …Operational
20273Failover protocol message UPDDONE from server Server for failover relationship …DhcpAdminEvents
20273[DHCPv4.AuthFailedUpdDoneMsgDigestFailedToCompare] Failover protocol message …Operational
20274Failover protocol message UPDDONE from server Server for failover relationship …DhcpAdminEvents
20274[DHCPv4.AuthFailedUpdDoneMsgDigestNotConfigured] Failover protocol message …Operational
20275Failover protocol message UPDDONE from server Server for failover relationship …DhcpAdminEvents
20275[DHCPv4.AuthFailedUpdDoneMsgDigestNotPresent] Failover protocol message UPDDONE …Operational
20276Failover protocol message UPDREQ from server Server for failover relationship …DhcpAdminEvents
20276[DHCPv4.AuthFailedUpdReqMsgDigestFailedToCompare] Failover protocol message …Operational
20277Failover protocol message UPDREQ from server Server for failover relationship …DhcpAdminEvents
20277[DHCPv4.AuthFailedUpdReqMsgDigestNotConfigured] Failover protocol message UPDREQ …Operational
20278Failover protocol message UPDREQ from server Server for failover relationship …DhcpAdminEvents
20278[DHCPv4.AuthFailedUpdReqMsgDigestNotPresent] Failover protocol message UPDREQ …Operational
20279Failover protocol message STATE from server Server for failover relationship …DhcpAdminEvents
20279[DHCPv4.AuthFailedStateMsgDigestFailedToCompare] Failover protocol message STATE …Operational
20280Failover protocol message STATE from server Server for failover relationship …DhcpAdminEvents
20280[DHCPv4.AuthFailedStateMsgDigestNotConfigured] Failover protocol message STATE …Operational
20281Failover protocol message STATE from server Server for failover relationship …DhcpAdminEvents
20281[DHCPv4.AuthFailedStateMsgDigestNotPresent] Failover protocol message STATE from …Operational
20282Failover protocol message CONTACT from server Server for failover relationship …DhcpAdminEvents
20282[DHCPv4.AuthFailedContactMsgDigestFailedToCompare] Failover protocol message …Operational
20283Failover protocol message CONTACT from server Server for failover relationship …DhcpAdminEvents
20283[DHCPv4.AuthFailedContactMsgDigestNotConfigured] Failover protocol message …Operational
20284Failover protocol message CONTACT from server Server for failover relationship …DhcpAdminEvents
20284[DHCPv4.AuthFailedContactMsgDigestNotPresent] Failover protocol message CONTACT …Operational
20285An invalid cryptographic algorithm Message was specified for failover message …DhcpAdminEvents
20285[DHCPv4.InvalidAlgorithmProvider] An invalid cryptographic algorithm %1 was …Operational
20286BINDING UPDATE message for IP address IpAddress could not be replicated to the …DhcpAdminEvents
20286[DHCPv4.FailoverClientLeaseDropped] BINDING UPDATE message for IP address %1 …Operational
20287DHCP client request from ClientID was dropped since the applicable IP address …DhcpAdminEvents
20287[DHCPv4.ClientRequestDropped] DHCP client request from %1 was dropped since the …Operational
20288This DHCP server LocalServer has transitioned to a PARTNER DOWN state for the …DhcpAdminEvents
20288Operational
20289[DHCPv4.SendBndUpdMessage] A BINDING-UPDATE message with transaction ID: %1 was …Operational
20289A BINDING-UPDATE message with transaction id: TransactionId was sent for IP …AuditLog
20290[DHCPv4.RecvBndUpdMessage] A BINDING-UPDATE message with transaction ID: %1 was …Operational
20290A BINDING-UPDATE message with transaction id: TransactionId was received for IP …AuditLog
20291A BINDING-ACK message with transaction id: TransactionId was sent for IP …DhcpAdminEvents
20291[DHCPv4.SendBndAckMessageRejectReason] A BINDING-ACK message with transaction …Operational
20292A BINDING-ACK message with transaction id: TransactionId was received for IP …DhcpAdminEvents
20292[DHCPv4.RecvBndAckMessageRejectReason] A BINDING-ACK message with transaction …Operational
20293[DHCPv4.SendUpdReqMessage] A UPDREQ message with transaction ID: %1 was sent to …Operational
20293A UPDREQ message with transaction id: TransactionId was sent to partner server: …AuditLog
20294[DHCPv4.RecvUpdReqMessage] A UPDREQ message with transaction ID: %1 was received …Operational
20294A UPDREQ message with transaction id: TransactionId was received from partner …AuditLog
20295[DHCPv4.SendUpdDoneMessage] A UPDDONE message with transaction ID: %1 was sent …Operational
20295A UPDDONE message with transaction id: TransactionId was sent to partner server: …AuditLog
20296[DHCPv4.RecvUpdDoneMessage] A UPDDONE message with transaction ID: %1 was …Operational
20296A UPDDONE message with transaction id: TransactionId was received from partner …AuditLog
20297[DHCPv4.SendUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was …Operational
20297A UPDREQALL message with transaction id: TransactionId was sent to partner …AuditLog
20298[DHCPv4.RecvUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was …Operational
20298A UPDREQALL message with transaction id: TransactionId was received from partner …AuditLog
20299[DHCPv4.SendContactMessage] A CONTACT message with transaction ID: %1 was sent …Operational
20299A CONTACT message with transaction id: TransactionId was sent to partner server: …AuditLog
20300[DHCPv4.RecvContactMessage] A CONTACT message with transaction ID: %1 was …Operational
20300A CONTACT message with transaction id: TransactionId was received from partner …AuditLog
20301[DHCPv4.SendConnectMessage] A CONNECT message with transaction ID: %1 was sent …Operational
20301A CONNECT message with transaction id: TransactionId was sent to partner server: …AuditLog
20302[DHCPv4.RecvConnectMessage] A CONNECT message with transaction ID: %1 was …Operational
20302A CONNECT message with transaction id: TransactionId was received from partner …AuditLog
20303[DHCPv4.SendStateMessage] A STATE message with transaction ID: %1 was sent to …Operational
20303A STATE message with transaction id: TransactionId was sent to partner server : …AuditLog
20304[DHCPv4.RecvStateMessage] A STATE message with transaction ID: %1 was received …Operational
20304A STATE message with transaction id: TransactionId was received from partner …AuditLog
20305[DHCPv4.SendConnectAckMessage] A CONNECTACK message with transaction ID %1 was …Operational
20305A CONNECTACK message with transaction id TransactionId was sent to partner …AuditLog
20306[DHCPv4.RecvConnectAckMessage] A CONNECTACK message with transaction ID %1 was …Operational
20306A CONNECTACK message with transaction id TransactionId was received from partner …AuditLog
20307[DHCPv4.SendBndAckMessageNoRejectReason] A BINDING-ACK message with transaction …Operational
20307A BINDING-ACK message with transaction id: TransactionId was sent for IP …AuditLog
20308[DHCPv4.RecvBndAckMessageNoRejectReason] A BINDING-ACK message with transaction …Operational
20308A BINDING-ACK message with transaction id: TransactionId was received for IP …AuditLog
20309[DHCPv4.SendConnectAckMessageRejectReason] A CONNECTACK message with transaction …Operational
20309A CONNECTACK message with transaction id TransactionId was sent to partner …AuditLog
20310[DHCPv4.RecvConnectAckMessageRejectReason] A CONNECTACK message with transaction …Operational
20310A CONNECTACK message with transaction id TransactionId was received from partner …AuditLog
20311[DHCPv4.UpdateSharedSecret] The shared secret for failover relationship %2 with …Operational
20311The shared secret for failover relationship Server2Name with server …Operational
20312[DHCPv4.EnabledSharedSecret] Message authentication for failover relationship %2 …Operational
20312Message authentication for failover relationship Server2Name with server …Operational
20313[DHCPv4.DisabledSharedSecret] Message authentication for failover relationship …Operational
20313Message authentication for failover relationship Server2Name with server …Operational
20314Operational
20314DebugLogs
20315[DHCPv4.UpdateScopePolicyDNSSuffix] DNSSuffix of scope %3 policy %2 was set to …Operational
20315DNSSuffix of scope IP_ScopeName policy PolicyName was set to String1.Operational
20316[DHCPv4.UpdateServerPolicyDNSSuffix] DNSSuffix of server policy %2 was set to …Operational
20316DNSSuffix of server policy PolicyName was set to String1.Operational
20317Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20317Operational
20318Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20318Operational
20319Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20319Operational
20320PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20320Operational
20321PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20321Operational
20322PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20322Operational
20323Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20323Operational
20324Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20324Operational
20325Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed …DhcpAdminEvents
20325Operational
20326PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20326Operational
20327PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20327Operational
20328PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with …DhcpAdminEvents
20328Operational

Event ID 70 — [DHCPv4.ScopeConfigured] Scope: %1 for IPv4 is Configured by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Configured by .

References #

Event ID 70 — Scope: IP_ScopeName for IPv4 is Configured by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Configured by ClientName.

Message #

Scope: %1 for IPv4 is Configured by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 71 — [DHCPv4.ScopeModified] Scope: %1 for IPv4 is Modified by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Modified by .

References #

Event ID 71 — Scope: IP_ScopeName for IPv4 is Modified by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Modified by ClientName.

Message #

Scope: %1 for IPv4 is Modified by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 72 — [DHCPv4.ScopeDeleted] Scope: %1 for IPv4 is Deleted by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Deleted by .

References #

Event ID 72 — Scope: IP_ScopeName for IPv4 is Deleted by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Deleted by ClientName.

Message #

Scope: %1 for IPv4 is Deleted by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 73 — [DHCPv4.ScopeActivated] Scope: %1 for IPv4 is Activated by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Activated by .

References #

Event ID 73 — Scope: IP_ScopeName for IPv4 is Activated by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Activated by ClientName.

Message #

Scope: %1 for IPv4 is Activated by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 74 — [DHCPv4.ScopeDeActivated] Scope: %1 for IPv4 is Deactivated by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is DeActivated by .

References #

Event ID 74 — Scope: IP_ScopeName for IPv4 is DeActivated by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is DeActivated by ClientName.

Message #

Scope: %1 for IPv4 is DeActivated by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Updated with Lease Duration: ModifiedDuration seconds by ClientName. The previous configured Lease Duration was: OriginalDuration seconds.

Message #

Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ModifiedDuration UnicodeString—
ClientName UnicodeString—
OriginalDuration UnicodeString—

References #

Event ID 76 — [DHCPv4.ScopeOptionUpdate] Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Updated with Option Settings: OptionName by ClientName.

Message #

Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 77 — [DHCPv4.ScopeDNSEnable] Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Enabled for DNS Dynamic updates by ClientName.

Message #

Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 78 — [DHCPv4.ScopeDNSDisable] Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Disabled for DNS Dynamic updates by ClientName.

Message #

Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 .

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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 #

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 .

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Updated with DNS Settings by ClientName: to always dynamically update DNS A and PTR records.

Message #

Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.

Message #

Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to discard DNS A and PTR records when lease is deleted.

Message #

Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 85 — [DHCPv4.ScopePBA_DeActivated] Policy based assignment has been disabled for scope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been disabled for scope .

References #

Event ID 85 — Policy based assignment has been disabled for scope IP_ScopeName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been disabled for scope IP_ScopeName.

Message #

Policy based assignment has been disabled for scope %1.

Fields #

NameDescription
IP_ScopeName UnicodeString—

References #

Event ID 86 — [DHCPv4.ScopePBA_Activated] Policy based assignment has been enabled for scope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been enabled for scope .

References #

Event ID 86 — Policy based assignment has been enabled for scope IP_ScopeName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been enabled for scope IP_ScopeName.

Message #

Policy based assignment has been enabled for scope %1.

Fields #

NameDescription
IP_ScopeName UnicodeString—

References #

Event ID 87 — [DHCPv4.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Name Protection setting is Enabled on Scope: IP_Name for IPv4 by ClientName.

Message #

Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.

Fields #

NameDescription
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 88 — [DHCPv4.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Name Protection setting is Disabled on Scope: IP_Name for IPv4 by ClientName.

Message #

Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.

Fields #

NameDescription
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 89 — [DHCPv4.ScopeSupportType] Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_Name for IPv4 is Updated with support type: ModifiedSupportType by ClientName. The previous configured state was: OriginalSupportType.

Message #

Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

NAP Enforcement is Enabled on Scope: IP_ScopeName for IPv4 by ClientName.

Message #

NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 91 — [DHCPv4.ScopeNAPDisabled] NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

NAP Enforcement is Disabled on Scope: IP_ScopeName for IPv4 by ClientName.

Message #

NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 92 — [DHCPv4.ScopeNAPProfileConfigured] NAP Profile is configured on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

NAP Profile is configured on Scope: IP_ScopeName for IPv4 with the following NAP Profile: NAP_ProfileName by ClientName.

Message #

NAP Profile is configured on Scope: %1  for IPv4 with the following NAP Profile: %2 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
NAP_ProfileName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The following NAP Profile: is deleted on Scope: by .

References #

Event ID 94 — The following NAP Profile: IP_ScopeName is deleted on Scope: NAP_ProfileName by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The following NAP Profile: IP_ScopeName is deleted on Scope: NAP_ProfileName by ClientName.

Message #

The following NAP Profile: %1 is deleted on Scope: %2 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
NAP_ProfileName UnicodeString—
ClientName UnicodeString—

References #

Event ID 95 — [DHCPv4.MulticastScopeConfigured] Scope: %1 for Multicast IPv4 is Configured by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for Multicast IPv4 is Configured by .

References #

Event ID 95 — Scope: IP_MulticastScopeName for Multicast IPv4 is Configured by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_MulticastScopeName for Multicast IPv4 is Configured by ClientName.

Message #

Scope: %1 for Multicast IPv4 is Configured by %2.

Fields #

NameDescription
IP_MulticastScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 96 — [DHCPv4.MulticastScopeDeleted] Scope: %1 for Multicast IPv4 is Deleted by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for Multicast IPv4 is Deleted by .

References #

Event ID 96 — Scope: IP_MulticastScopeName for Multicast IPv4 is Deleted by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_MulticastScopeName for Multicast IPv4 is Deleted by ClientName.

Message #

Scope: %1 for Multicast IPv4 is Deleted by %2.

Fields #

NameDescription
IP_MulticastScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 97 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Added in Superscope: by .

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

Event ID 97 — Scope: IP_ScopeName for IPv4 is Added in Superscope: IP_SuperScopeName by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Added in Superscope: IP_SuperScopeName by ClientName.

Message #

Scope: %1 for IPv4 is Added in Superscope: %2 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

Event ID 98 — [DHCPv4.SuperScopeConfigured] SuperScope: %1 for IPv4 is Configured by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

SuperScope: for IPv4 is Configured by .

References #

Event ID 98 — SuperScope: IP_MulticastScopeName for IPv4 is Configured by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

SuperScope: IP_MulticastScopeName for IPv4 is Configured by ClientName.

Message #

SuperScope: %1 for IPv4 is Configured by %2.

Fields #

NameDescription
IP_MulticastScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 99 — [DHCPv4.SuperScopeDeleted] SuperScope: %1 for IPv4 is Deleted by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

SuperScope: for IPv4 is Deleted by .

References #

Event ID 99 — SuperScope: IP_MulticastScopeName for IPv4 is Deleted by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

SuperScope: IP_MulticastScopeName for IPv4 is Deleted by ClientName.

Message #

SuperScope: %1 for IPv4 is Deleted by %2.

Fields #

NameDescription
IP_MulticastScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 100 — [DHCPv4.SuperScopeActivated] Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is Activated by ClientName.

Message #

Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 101 — [DHCPv4.SuperScopeDeActivated] Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName within SuperScope: IP_SuperScopeName for IPv4 is DeActivated by ClientName.

Message #

Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 102 — [DHCPv4.SuperScopeDeleteTemp] Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Removed in Superscope: IP_SuperScopeName by ClientName. However, the Scope exists outside the Superscope.

Message #

Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 103 — [DHCPv4.SuperScopeDeletePerm] Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Deleted in Superscope: IP_SuperScopeName as well as Deleted permanently by ClientName.

Message #

Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
IP_SuperScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 104 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

Delay Time: %1 milliseconds for the OFFER message sent by Secondary Servers is Updated on Scope: %2 for IPv4 by %4. The previous configured Delay Time was: %3 milliseconds.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option OptionName for IPv4 has been updated by ClientName.

Message #

Server level option %1 for IPv4 has been updated by %2.

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 106 — [DHCPv4.ReservationConfigured] Reservation: %1 for IPv4 is Configured under Scope %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 is Configured under Scope IP_Name by ClientName.

Message #

Reservation: %1 for IPv4 is Configured under Scope %2 by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 107 — [DHCPv4.ReservationDeleted] Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 is Deleted under Scope IP_Name by ClientName.

Message #

Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 108 — [DHCPv4.ReservationDNSEnable] Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 under Scope: IP_Name is Enabled for DNS Dynamic updates by ClientName.

Message #

Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 109 — [DHCPv4.ReservationDNSDisable] Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 under Scope: IP_Name is Disabled for DNS Dynamic updates by ClientName.

Message #

Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

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.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with DNS Settings by ClientName: to always dynamically update DNS A and PTR records.

Message #

Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

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.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

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.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

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 not request updates.

Fields #

NameDescription
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 ...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

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 do not request updates.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv4 under Scope: IP_Name is Updated with Option Setting: OptionName by ClientName.

Message #

Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 117 — [DHCPv4.ServerPBA_DeActivated] Policy based assignment has been disabled at server level.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been disabled at server level.

References #

Event ID 117 — Policy based assignment has been disabled at server level.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been disabled at server level.

Message #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been enabled at server level.

References #

Event ID 118 — Policy based assignment has been enabled at server level.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Policy based assignment has been enabled at server level.

Message #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Added exclusion IP Address range ExclusionRange in the Address Pool for IPv4 under Scope: IP_Name by ClientName.

Message #

Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.

Fields #

NameDescription
ExclusionRange UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 120 — [DHCPv4.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv4 under Scope: IP_Name by ClientName.

Message #

Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.

Fields #

NameDescription
ExclusionRange UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 121 — [DHCPv4.ScopeEnableAllow] Link Layer based filtering is Enabled in the allowlist of the IPv4 by %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Link Layer based filtering is Enabled in the Allow List of the IPv4 by ClientName.

Message #

Link Layer based filtering is Enabled in the Allow List of the IPv4 by %1

Fields #

NameDescription
ClientName UnicodeString—

References #

Event ID 122 — [DHCPv4.ScopeDisableAllow] Link Layer based filtering is Disabled in the allowlist of the IPv4 by %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Link Layer based filtering is Disabled in the Allow List of the IPv4 by ClientName.

Message #

Link Layer based filtering is Disabled in the Allow List of the IPv4 by %1

Fields #

NameDescription
ClientName UnicodeString—

References #

Event ID 123 — [DHCPv4.ScopeAllow_AddFilter] Filter for physical address: %1, hardware type: %3 added to the IPv4 allowlist by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Filter for physical address: PhysicalAddress, hardware type: HWType added to the IPv4 Allow List by ClientName.

Message #

Filter for physical address: %1, hardware type: %3 added to the IPv4 Allow List by %2.

Fields #

NameDescription
PhysicalAddress UnicodeString—
ClientName UnicodeString—
HWType UInt32—

References #

Event ID 124 — [DHCPv4.ScopeAllow_DeleteFilter] Filter for physical address: %1, hardware type: %3 removed from the IPv4 allowlist by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Filter for physical address: PhysicalAddress, hardware type: HWType removed from the IPv4 Allow List by ClientName.

Message #

Filter for physical address: %1, hardware type: %3 removed from the IPv4 Allow List by %2.

Fields #

NameDescription
PhysicalAddress UnicodeString—
ClientName UnicodeString—
HWType UInt32—

References #

Event ID 125 — [DHCPv4.ScopeEnableDeny] Link Layer based filtering is Enabled in the blocklist of the IPv4 by %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Link Layer based filtering is Enabled in the Deny List of the IPv4 by ClientName.

Message #

Link Layer based filtering is Enabled in the Deny List of the IPv4 by %1

Fields #

NameDescription
ClientName UnicodeString—

References #

Event ID 126 — [DHCPv4.ScopeDisableDeny] Link Layer based filtering is Disabled in the blocklist of the IPv4 by %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Link Layer based filtering is Disabled in the Deny List of the IPv4 by ClientName.

Message #

Link Layer based filtering is Disabled in the Deny List of the IPv4 by %1

Fields #

NameDescription
ClientName UnicodeString—

References #

Event ID 127 — [DHCPv4.ScopeDeny_AddFilter] Filter for physical address: %1, hardware type: %3 added to the IPv4 blocklist by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Filter for physical address: PhysicalAddress, hardware type: HWType added to the IPv4 Deny List by ClientName.

Message #

Filter for physical address: %1, hardware type: %3 added to the IPv4 Deny List by %2.

Fields #

NameDescription
PhysicalAddress UnicodeString—
ClientName UnicodeString—
HWType UInt32—

References #

Event ID 128 — [DHCPv4.ScopeDeny_DeleteFilter] Filter for physical address: %1, hardware type: %3 removed from the IPv4 blocklist by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Filter for physical address: PhysicalAddress, hardware type: HWType removed from the IPv4 Deny List by ClientName.

Message #

Filter for physical address: %1, hardware type: %3 removed from the IPv4 Deny List by %2.

Fields #

NameDescription
PhysicalAddress UnicodeString—
ClientName UnicodeString—
HWType UInt32—

References #

Event ID 129 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv6 is Configured by .

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

Event ID 129 — Scope: IP_ScopeName for IPv6 is Configured by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Configured by ClientName.

Message #

Scope: %1 for IPv6 is Configured by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

Event ID 130 — [DHCPv6.ScopeDeleted] Scope: %1 for IPv6 is Deleted by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv6 is Deleted by .

References #

Event ID 130 — Scope: IP_ScopeName for IPv6 is Deleted by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Deleted by ClientName.

Message #

Scope: %1 for IPv6 is Deleted by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 131 — [DHCPv6.ScopeActivated] Scope: %1 for IPv6 is Activated by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv6 is Activated by .

References #

Event ID 131 — Scope: IP_ScopeName for IPv6 is Activated by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Activated by ClientName.

Message #

Scope: %1 for IPv6 is Activated by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 132 — [DHCPv6.ScopeDeActivated] Scope: %1 for IPv6 is DeActivated by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv6 is DeActivated by .

References #

Event ID 132 — Scope: IP_ScopeName for IPv6 is DeActivated by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is DeActivated by ClientName.

Message #

Scope: %1 for IPv6 is DeActivated by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Updated with Lease Preferred Lifetime: ModifiedDuration by ClientName. The previous configured Lease Preferred Lifetime was: OriginalDuration.

Message #

Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime: %2 by %3. The previous configured Lease Preferred Lifetime was: %4.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Updated with Lease Valid Lifetime: ModifiedDuration by ClientName. The previous configured Lease Valid Lifetime was: OriginalDuration.

Message #

Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Updated with Option Setting: OptionName by ClientName.

Message #

Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 136 — [DHCPv6.ScopeDNSEnable] Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Enabled for DNS Dynamic updates by ClientName.

Message #

Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 137 — [DHCPv6.ScopeDNSDisable] Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Disabled for DNS Dynamic updates by ClientName.

Message #

Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

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.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Updated with DNS Settings by ClientName: to always dynamically update DNS AAAA and PTR records.

Message #

Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Enabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.

Message #

Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Disabled for DNS Settings by ClientName: to discard DNS AAAA and PTR records when lease is deleted.

Message #

Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 142 — [DHCPv6.ScopeDHCIDEnable] Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Name Protection setting is Enabled on Scope: IP_Name for IPv6 by ClientName.

Message #

Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.

Fields #

NameDescription
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 143 — [DHCPv6.ScopeDHCIDDisable] Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Name Protection setting is Disabled on Scope: IP_Name for IPv6 by ClientName.

Message #

Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.

Fields #

NameDescription
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 145 — [DHCPv6.ReservationConfigured] Reservation: %1 for IPv6 is Configured under Scope %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 is Configured under Scope IP_Name by ClientName.

Message #

Reservation: %1 for IPv6 is Configured under Scope %2 by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 147 — [DHCPv6.ReservationDeleted] Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 is Deleted under Scope IP_Name by ClientName.

Message #

Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 148 — [DHCPv6.ReservationDNSEnable] Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 under Scope: IP_Name is Enabled for DNS Dynamic updates by ClientName.

Message #

Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 149 — [DHCPv6.ReservationDNSDisable] Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 under Scope: IP_Name is Disabled for DNS Dynamic updates by ClientName.

Message #

Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 ...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

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.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with DNS Settings by ClientName: to always dynamically update DNS AAAA and PTR records.

Message #

Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

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.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

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.

Message #

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.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 154 — [DHCPv6.ReservationOptionUpdate] Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Reservation: ReservationName for IPv6 under Scope: IP_Name is Updated with Option Setting: OptionName by ClientName.

Message #

Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 155 — [DHCPv6.ScopeExclusionAdded] Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Added exclusion IP Address range ExclusionRange in the Address Pool for IPv6 under Scope: IP_Name by ClientName.

Message #

Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

Fields #

NameDescription
ExclusionRange UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 156 — [DHCPv6.ScopeExclusionDeleted] Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Deleted exclusion IP Address range ExclusionRange in the Address Pool for IPv6 under Scope: IP_Name by ClientName.

Message #

Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

Fields #

NameDescription
ExclusionRange UnicodeString—
IP_Name UnicodeString—
ClientName UnicodeString—

References #

Event ID 157 — [DHCPv6.ScopeModified] Scope: %1 for IPv6 is Modified by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv6 is Modified by .

References #

Event ID 157 — Scope: IP_ScopeName for IPv6 is Modified by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv6 is Modified by ClientName.

Message #

Scope: %1 for IPv6 is Modified by %2.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 158 — [DHCPv6.ScopeStatelessEnabled] DHCPv6 Stateless client inventory has been enabled for the scope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been enabled for the scope IP_ScopeName.

Message #

DHCPv6 Stateless client inventory has been enabled for the scope %1.

Fields #

NameDescription
IP_ScopeName UnicodeString—

References #

Event ID 159 — [DHCPv6.ScopeStatelessDisabled] DHCPv6 Stateless client inventory has been disabled for the scope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been disabled for the scope IP_ScopeName.

Message #

DHCPv6 Stateless client inventory has been disabled for the scope %1.

Fields #

NameDescription
IP_ScopeName UnicodeString—

References #

Event ID 160 — [DHCPv6.ServerStatelessEnabled] DHCPv6 Stateless client inventory has been enabled for the server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been enabled for the server.

References #

Event ID 160 — DHCPv6 Stateless client inventory has been enabled for the server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been enabled for the server.

Message #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been disabled for the server.

References #

Event ID 161 — DHCPv6 Stateless client inventory has been disabled for the server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Stateless client inventory has been disabled for the server.

Message #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Purge time interval for DHCPv6 stateless client inventory for scope IP_ScopeName has been set to PurgeInterval hours.

Message #

Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours.

Fields #

NameDescription
IP_ScopeName UnicodeString—
PurgeInterval UInt32—

References #

Event ID 163 — [DHCPv6.ServerStatelessPurgeInterval] Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Purge time interval for DHCPv6 stateless client inventory for server has been set to PurgeInterval hours.

Message #

Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.

Fields #

NameDescription
PurgeInterval UInt32—

References #

Event ID 164 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: for IPv4 is Enabled for DNS Settings by : to disable dynamic updates for DNS PTR records.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Enabled for DNS Settings by ClientName: to disable dynamic updates for DNS PTR records.

Message #

Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope: IP_ScopeName for IPv4 is Disabled for DNS Settings by ClientName: to disable dynamic updates for DNS PTR records.

Message #

Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.

Fields #

NameDescription
IP_ScopeName UnicodeString—
ClientName UnicodeString—

References #

Event ID 166 — [DHCPv6.ServerOptionUpdate] Server level option %1 for IPv6 has been updated by %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option OptionName for IPv6 has been updated by ClientName.

Message #

Server level option %1 for IPv6 has been updated by %2.

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

References #

Event ID 167 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option for IPv4 has been removed by .

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 167 — Server level option OptionName for IPv4 has been removed by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option OptionName for IPv4 has been removed by ClientName.

Message #

Server level option %1 for IPv4 has been removed by %2.

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 168 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: has been removed from IPv4 scope: by .

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 168 — Option setting: OptionName has been removed from IPv4 scope: IP_ScopeName by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: OptionName has been removed from IPv4 scope: IP_ScopeName by ClientName.

Message #

Option setting: %2 has been removed from IPv4 scope: %1 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 169 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: has been removed from the reservation: in IPv4 scope: by .

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: OptionName has been removed from the reservation: ReservationName in IPv4 scope: IP_Name by ClientName.

Message #

Option setting: %3 has been removed from the reservation: %1 in IPv4 scope: %2 by %4.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 170 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option for IPv6 has been removed by .

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 170 — Server level option OptionName for IPv6 has been removed by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Server level option OptionName for IPv6 has been removed by ClientName.

Message #

Server level option %1 for IPv6 has been removed by %2.

Fields #

NameDescription
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 171 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: has been removed from IPv6 scope: by .

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 171 — Option setting: OptionName has been removed from IPv6 scope: IP_ScopeName by ClientName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: OptionName has been removed from IPv6 scope: IP_ScopeName by ClientName.

Message #

Option setting: %2 has been removed from IPv6 scope: %1 by %3.

Fields #

NameDescription
IP_ScopeName UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

Event ID 172 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: has been removed from the reservation: in IPv6 scope: by .

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Option setting: OptionName has been removed from the reservation: ReservationName in IPv6 scope: IP_Name by ClientName.

Message #

Option setting: %3 has been removed from the reservation: %1 in IPv6 scope: %2 by %4.

Fields #

NameDescription
ReservationName UnicodeString—
IP_Name UnicodeString—
OptionName UnicodeString—
ClientName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service received the unknown option , with a length of . The raw option data is given below.

Message #

The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below.

References #

Event ID 1001 — [EVENT_SERVER_FAILED_REGISTER_SC] The DHCP service failed to register with Service Controller.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to register with Service Controller. The following error occurred.

Message #

The DHCP service failed to register with Service Controller. The following error occurred: 
%1.

References #

Event ID 1002 — [EVENT_SERVER_INIT_DATA_FAILED] The DHCP service failed to initialize its global parameters.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize its global parameters. The following error occurred.

Message #

The DHCP service failed to initialize its global parameters. The following error occurred: 
%1

References #

Event ID 1003 — [EVENT_SERVER_INIT_REGISTRY_FAILED] The DHCP service failed to initialize its registry parameters.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize its registry parameters. The following error occurred.

Message #

The DHCP service failed to initialize its registry parameters. The following error occurred: 
%1

References #

Event ID 1004 — [EVENT_SERVER_INIT_DATABASE_FAILED] The DHCP service failed to initialize the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize the database. The following error occurred.

Message #

The DHCP service failed to initialize the database. The following error occurred: 
%1

References #

Event ID 1005 — [EVENT_SERVER_INIT_WINSOCK_FAILED] The DHCP service failed to initialize Winsock startup.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize Winsock startup. The following error occurred.

Message #

The DHCP service failed to initialize Winsock startup. The following error occurred: 
%1

References #

Event ID 1006 — [EVENT_SERVER_INIT_RPC_FAILED] The DHCP service failed to start as an RPC server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to start as a RPC server. The following error occurred.

Message #

The DHCP service failed to start as a RPC server. The following error occurred : 
%1

References #

Event ID 1007 — [EVENT_SERVER_INIT_SOCK_FAILED] The DHCP service failed to initialize Winsock data.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize Winsock data. The following error occurred.

Message #

The DHCP service failed to initialize Winsock data. The following error occurred: 
%1

References #

Event ID 1008 — [EVENT_SERVER_SHUTDOWN] The DHCP service is shutting down due to the following error: %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service is shutting down due to the following error.

Message #

The DHCP service is shutting down due to the following error: 
%1

References #

Event ID 1009 — [EVENT_SERVER_CLIENT_CLEANUP] The DHCP service encountered the following error while cleaning up the pending client records: %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service encountered the following error while cleaning up the pending client records.

Message #

The DHCP service encountered the following error while cleaning up the pending client records: 
%1

References #

Event ID 1010 — [EVENT_SERVER_DATABASE_CLEANUP] The DHCP service encountered the following error while cleaning up the database: %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service encountered the following error while cleaning up the database.

Message #

The DHCP service encountered the following error while cleaning up the database: 
%1

References #

Event ID 1011 — [EVENT_SERVER_LEASE_NACK] The DHCP service issued a NACK to the client, %2, for the address, %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service issued a NACK (negative acknowledgement message) to the client, , for the address, .

Message #

The DHCP service issued a NACK (negative acknowledgement message) to the client, %2, for the address, %1.

References #

Event ID 1012 — [EVENT_SERVER_LEASE_DECLINED] The DHCP client, %2, declined the address %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP client, , declined the address .

Message #

The DHCP client, %2, declined the address %1.

References #

Event ID 1013 — [EVENT_SERVER_LEASE_RELEASE] The DHCP Client, %2, released the address %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP Client, , released the address .

Message #

The DHCP Client, %2, released the address %1.

References #

Event ID 1016 — [EVENT_SERVER_DATABASE_BACKUP] The DHCP service encountered the following error when backing up the database: %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service encountered the following error when backing up the database.

Message #

The DHCP service encountered the following error when backing up the database: 
%1

References #

Event ID 1017 — [EVENT_SERVER_CONFIG_BACKUP] The DHCP service encountered the following error when backing up the registry configuration: %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service encountered the following error when backing up the registry configuration.

Message #

The DHCP service encountered the following error when backing up the registry configuration: 
%1

References #

Event ID 1018 — [EVENT_SERVER_DATABASE_RESTORE_FAILED] The DHCP service failed to restore the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to restore the database. The following error occurred.

Message #

The DHCP service failed to restore the database. The following error occurred: 
%1

References #

Event ID 1019 — [EVENT_SERVER_CONFIG_RESTORE_FAILED] The DHCP service failed to restore the DHCP registry configuration.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to restore the DHCP registry configuration. The following error occurred.

Message #

The DHCP service failed to restore the DHCP registry configuration. The following error occurred: 
%1

References #

Event ID 1020 — [EVENT_SERVER_LOW_ADDRESS_WARNING] Scope, %1, is %2 percent full with only %3 IP addresses remaining.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scope, , is percent full with only IP addresses remaining.

Message #

Scope, %1, is %2 percent full with only %3 IP addresses remaining.

References #

Event ID 1021 — [EVENT_SERVER_LOAD_JET_FAILED] The DHCP service couldn't load the JET database library successfully.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service could not load the JET database library successfully.

Message #

The DHCP service could not load the JET database library successfully.

References #

Event ID 1022 — [EVENT_SERVER_JET_CONV_REQUIRED] The DHCP service couldn't use the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP service could not use the database. If this service was started for the first time after the upgrade from NT 3.51 or earlier, you need to run the utility, upg351db.exe, on the DHCP database to convert it to the new JET database format. Restart the DHCP service after you have upgraded the database.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP service will now terminate because the existing database needs conversion to Windows 2000 format.  The conversion via the jetconv process, has initiated.  Do not reboot or stop the jetconv process.  The conversion may take up to 10 minutes depending on the size of the database.  Terminate DHCP now by clicking OK. This is required for the database conversion to succeed.  NOTE: The DHCP service will be restarted automatically when the conversion is completed.  To check conversion status, look at the Application event log for the jetconv process.

References #

Event ID 1024 — [EVENT_SERVER_INIT_AND_READY] The DHCP service has initialized and is ready.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has initialized and is ready.

Message #

The DHCP service has initialized and is ready

References #

Event ID 1025 — [EVENT_SERVER_BOOT_FILE_TABLE] The DHCP service was unable to read the BOOTP file table from the registry.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to read the BOOTP file table from the registry. The DHCP service will be unable to respond to BOOTP requests that specify the boot file name.

Message #

The DHCP service was unable to read the BOOTP file table from the registry.  The DHCP service will be unable to respond to BOOTP requests that specify the boot file name.

References #

Event ID 1026 — [EVENT_SERVER_BOOT_FILE_NAME] The DHCP service was unable to read the global BOOTP file name from the registry.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to read the global BOOTP file name from the registry.

Message #

The DHCP service was unable to read the global BOOTP file name from the registry.

References #

Event ID 1027 — [EVENT_SERVER_AUDIT_LOG_APPEND_FAILED] The audit log file can't be appended.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The audit log file cannot be appended.

Message #

The audit log file cannot be appended.

References #

Event ID 1028 — [EVENT_SERVER_INIT_AUDIT_LOG_FAILED] The DHCP service failed to initialize the audit log.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize the audit log. The following error occurred.

Message #

The DHCP service failed to initialize the audit log. The following error occurred: 
%1

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to ping for a new IP address. The address was leased to the client.

Message #

The DHCP service was unable to ping for a new IP address. The address was leased to the client.

References #

Event ID 1030 — [EVENT_SERVER_MOVE_AUDIT_LOG_FAILED] The audit log file couldn't be backed up.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The audit log file could not be backed up. The following error occurred.

Message #

The audit log file could not be backed up.  The following error occurred: 
%1

References #

Event ID 1031 — [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception.

#
Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The installed server callout .dll file has caused an exception. The exception was.

Message #

The installed server callout .dll file has caused an exception. The exception was: 
%1.  The server has ignored this exception. All further exceptions will be ignored.

Detection Patterns #

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.

#
Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The installed server callout .dll file has caused an exception. The exception was.

Message #

The installed server callout .dll file has caused an exception. The exception was: 
%1.  The server has ignored this exception and the .dll file could not be loaded.

Detection Patterns #

References #

Event ID 1033 — [EVENT_SERVER_CALLOUT_LOAD_SUCCESS] The DHCP service has successfully loaded one or more callout DLLs.

#
Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has successfully loaded one or more callout DLLs.

Message #

The DHCP service has successfully loaded one or more callout DLLs.

Detection Rules #

View all rules referencing this event →

Sigma # view in reference

References #

Event ID 1034 — [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs.

#
Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has failed to load one or more callout DLLs. The following error occured.

Message #

The DHCP service has failed to load one or more callout DLLs. The following error occured: 
%1

Detection Patterns #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to create or lookup the DHCP Users local group on this computer. The error code is in the data.

Message #

The DHCP service was unable to create or lookup the DHCP Users local group on this computer.  The error code is in the data.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer. The error code is in the data.

Message #

The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer.  The error code is in the data.

References #

Event ID 1037 — [EVENT_SERVER_CLEANUP_STARTED] The DHCP service has started to clean up the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has started to clean up the database.

Message #

The DHCP service has started to clean up the database.

References #

Event ID 1038 — [EVENT_SERVER_IPCLEANUP_FINISHED] The DHCP service has cleaned up the database for unicast IP addresses.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has cleaned up the database for unicast IP addresses -- leases have been recovered and records have been removed from the database.

Message #

The DHCP service has cleaned up the database for unicast IP addresses -- %1 leases have been recovered and %2 records have been removed from the database.

References #

Event ID 1039 — [EVENT_SERVER_MCASTCLEANUP_FINISHED] The DHCP service has cleaned up the database for multicast IP addresses.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service has cleaned up the database for multicast IP addresses -- leases have expired (been marked for deletion) and records have been removed from the database.

Message #

The DHCP service has cleaned up the database for multicast IP addresses -- %1 leases have expired (been marked for deletion) and %2 records have been removed from the database.

References #

Event ID 1040 — [EVENT_SERVER_DATABASE_RESTORE_SUCCEEDED] The DHCP service successfully restored the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service successfully restored the database.

Message #

The DHCP service successfully restored the database.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service is not servicing any DHCPv4 clients because none of the active network interfaces have statically configured IPv4 addresses, or there are no active interfaces.

Message #

The DHCP service is not servicing any DHCPv4 clients because none of the active network interfaces have statically configured IPv4 addresses, or there are no active interfaces.

References #

Event ID 1042 — [DHCP_ROGUE_EVENT_UNAUTHORIZED_INFO] The DHCP/BINL service running on this machine has detected a server on the network.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP/BINL service running on this machine has detected a server on the network. If the server does not belong to any domain, the domain is listed as empty.  The IP address of the server is listed in parentheses.  %1

References #

Event ID 1043 — [DHCP_ROGUE_EVENT_STARTED] The DHCP/BINL service on the local machine has determined that it's authorized to start.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.

Message #

The DHCP/BINL service on the local machine has determined that it is authorized to start.  It is servicing clients now.

References #

Event ID 1044 — [DHCP_ROGUE_EVENT_STARTED_DOMAIN] The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, has determined that it's authorized to start.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 #

The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, 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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on the local machine has determined that it is not authorized to start. It has stopped servicing clients. The following are some possible reasons for this.

Message #

The DHCP/BINL service on the local machine has determined that it is not authorized to start.  It has stopped servicing clients.  The following are some possible reasons for this: 
	This machine belongs to a workgroup and has encountered another DHCP Server (belonging to a Windows Administrative Domain) servicing the same network. 

	An unexpected network error occurred.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, has determined that it is not authorized to start.  It has stopped servicing clients.  The following are some possible reasons for this: 
	This machine is part of a directory service enterprise and is not authorized in the same domain.  (See help on the DHCP Service Management Tool for additional information). 

	This machine cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to a directory service enterprise on which the local machine is not authorized. 

	Some unexpected network error occurred.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.

Message #

The DHCP/BINL service on the local machine has determined that it is authorized to start.  It is servicing clients now. 
The DHCP/BINL service has determined that the machine was recently upgraded.  If the machine is intended to belong to a directory service enterprise, the DHCP service must be authorized in the directory service for it to start servicing clients.  (See help on DHCP Service Management Tool for authorizing the server).

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP/BINL Service on the local machine, belonging to Windows Domain %2, has determined that it is authorized to start.  It is servicing clients now.  It has determined that the computer was recently upgraded.  It has also determined that either there is no directory service enterprise for the domain or that the computer is not authorized in the directory service.  All DHCP services that belong to a directory service enterprise should be authorized in the directory service to service clients.   (See help on the DHCP Service Management Tool for authorizing a DHCP service in the directory service).

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on the local machine encountered an error while trying to find the domain of the local machine. The error was: .

Message #

The DHCP/BINL service on the local machine encountered an error while trying to find the domain of the local machine.  The error was: %3.

References #

Event ID 1050 — [DHCP_ROGUE_EVENT_NETWORK_FAILURE] The DHCP/BINL service on the local machine encountered a network error.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on the local machine encountered a network error. The error was: .

Message #

The DHCP/BINL service on the local machine encountered a network error. The error was: %3.

References #

Event ID 1051 — [DHCP_ROGUE_EVENT_UNAUTHORIZED] The DHCP/BINL service has determined that it isn't authorized to service clients on this network.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: %2.  All DHCP services that belong to a directory service enterprise must be authorized in the directory service to service clients.   (See help on the DHCP Service Management Tool for authorizing a DHCP server in the directory service).

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on this workgroup server has encountered another server with IP Address, , belonging to the domain .

Message #

The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service has encountered another server on this network with IP Address, , belonging to the domain: .

Message #

The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2.

References #

Event ID 1054 — [DHCP_ROGUE_EVENT_SHUTDOWN] The DHCP/BINL service on this computer is shutting down.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons.

Message #

The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons.

References #

Event ID 1055 — [DHCP_EVENT_DNS_REGPARAMS_FAILURE] The DHCP service was unable to impersonate the credentials necessary for DNS registrations.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to impersonate the credentials necessary for DNS registrations.

Message #

The DHCP service was unable to impersonate the credentials necessary for DNS registrations: 
%1.  The local system credentials is being used.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to convert the temporary database to ESE format.

Message #

The DHCP service was unable to convert the temporary database to ESE format: 
%1.

References #

Event ID 1058 — [EVENT_SERVER_INIT_CONFIG_FAILED] The DHCP service failed to initialize its configuration parameters.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to initialize its configuration parameters. The following error occurred.

Message #

The DHCP service failed to initialize its configuration parameters. The following error occurred: 
%1

References #

Event ID 1059 — [VENT_SERVER_COULDNT_SEE_DS] The DHCP service failed to see a directory server for authorization.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service failed to see a directory server for authorization.

Message #

The DHCP service failed to see a directory server for authorization.

References #

Event ID 1060 — [EVENT_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the audit log.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to access path specified for the audit log.

Message #

The DHCP service was unable to access path specified for the audit log.

References #

Event ID 1061 — [EVENT_SERVER_BACKUP_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the database backups.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to access path specified for the database backups.

Message #

The DHCP service was unable to access path specified for the database backups.

References #

Event ID 1062 — [EVENT_SERVER_DB_PATH_NOT_ACCESSIBLE] The DHCP service was unable to access path specified for the database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP service was unable to access path specified for the database.

Message #

The DHCP service was unable to access path specified for the database

References #

Event ID 1063 — [EVENT_SERVER_SCOPE_FULL] There are no IP addresses available for lease in the scope or superscope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

There are no IP addresses available for lease in the scope or superscope "%1".

Message #

There are no IP addresses available for lease in the scope or superscope "%1".

References #

Event ID 1064 — [EVENT_SERVER_BOOTP_FULL] There are no IP addresses available for BOOTP clients in the scope or superscope %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

There are no IP addresses available for BOOTP clients in the scope or superscope "%1".

Message #

There are no IP addresses available for BOOTP clients in the scope or superscope "%1".

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

There were some orphaned entries deleted in the configuration due to the deletion of a class or an option definition. Please recheck the server configuration.

Message #

There were some orphaned entries deleted in the configuration due to the deletion of a class or an option definition. Please recheck the server configuration.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.

Message #

This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The number of pending DHCPOFFER messages for delayed transmission to the client has exceeded the server's capacity of 1000 pending messages. The DHCP server will drop all subsequent DHCPDISCOVER messages for which the DHCPOFFER message response needs to be delayed as per the server configuration. The DHCP server will continue to process DHCPDISCOVER messages for which the DHCPOFFER message responses do not need to be delayed. The DHCP server will resume processing all DHCPDISCOVER messages once the number of pending DHCPOFFER messages for delayed transmission to the client is below the server's capacity.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The number pending DHCPOFFER messages for delayed transmission to the client is now below the server's capacity of 1000. The DHCP server will now resume processing all DHCPDISCOVER messages.

Message #

The number pending DHCPOFFER messages for delayed transmission to the client is now below the server's capacity of 1000. The DHCP server will now resume processing all DHCPDISCOVER messages.

References #

Event ID 1340 — [EVENT_SERVER_DNSDHCID_FAIL] The DNS registration for DHCPv4 Client IP address %1, FQDN %2, and DHCID %3 has been denied.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DNS registration for DHCPv4 Client IP address , FQDN and DHCID has been denied as there is probably an existing client with same FQDN already registered with DNS.

Message #

The DNS registration for DHCPv4 Client IP address %1 , FQDN %2 and DHCID %3 has been denied as there is probably an existing client with same FQDN already registered with DNS.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

There are no IP addresses available for lease in IP address range(s) of the policy in scope .

Message #

There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2.

References #

Event ID 1342 — [EVENT_SERVER_RESIDUAL_RANGES_FULL] IP address range of scope %1 is out of IP addresses.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

IP address range of scope is out of IP addresses.

Message #

IP address range of scope %1 is out of IP addresses.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Ip address range(s) for the scope policy is percent full with only IP addresses available .

Message #

Ip address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available .

References #

Event ID 1344 — [EVENT_SERVER_DNS_VALIDATION_FAILED] The DNS IP Address %1 isn't a valid DNS Server Address.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DNS IP Address is not a valid DNS Server Address.

Message #

The DNS IP Address %1 is not a valid DNS Server Address.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

IP address range of scope is percent full with only IP addresses available.

Message #

IP address range of scope %1 is %2 percent full with only %3 IP addresses available.

References #

Event ID 1377 — [EVENT_SERVER_SUPERSCOPE_LOW_ADDRESS_WARNING] SuperScope, %1, is %2 percent full with only %3 IP addresses remaining.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

SuperScope, , is percent full with only IP addresses remaining. This superscope has the following scopes.

Message #

SuperScope, %1, is %2 percent full with only %3 IP addresses remaining. This superscope has the following scopes %4

References #

Event ID 10000 — [EVENT_DHCPV6_ADDERESS_NACKED] DHCPv6 confirmation has been declined because the address wasn't appropriate to the link.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 confirmation has been declined because the address was not appropriate to the link or DHCPv6 renew request has a Zero lifetime for Client Address .

Message #

DHCPv6 confirmation has been declined because the address was not appropriate to the link or DHCPv6 renew request has a Zero lifetime for Client Address %1.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Renew, rebind or confirm received for IPv6 addresses for which there are no active lease available.

Message #

Renew, rebind or confirm received for IPv6 addresses %1 for which there are no active lease available

References #

Event ID 10002 — [EVENT_DHCPV6_SERVER_UNKNOWN_OPTION] DHCPv6 service received the unknown option %1, with a length of %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 service received the unknown option , with a length of . The raw option data is given below.

Message #

DHCPv6 service received the unknown option %1, with a length of %2. The raw option data is given below.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

There are no IPv6 addresses available to lease in the scope serving the network with Prefix .

Message #

There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1.

References #

Event ID 10004 — [EVENT_DHCPV6_SERVER_LEASE_DECLINED] The DHCPv6 client, %2, declined the address %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 client, , declined the address .

Message #

The DHCPv6 client, %2, declined the address %1.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Scope serving the network with prefix , is percent full with only IP addresses remaining.

Message #

DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining.

References #

Event ID 10006 — [EVENT_DHCPV6_CLIENT_DELETE] A DHCPv6 client %1 has been deleted from DHCPv6 database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

A DHCPV6 client has been deleted from DHCPV6 database.

Message #

A DHCPV6 client %1 has been deleted from DHCPV6 database.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process.

Message #

A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process.

References #

Event ID 10008 — [EVENT_DHCPV6_DROP_INVALID] An invalid DHCPv6 message has been dropped.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

An invalid DHCPV6 message has been dropped.

Message #

An invalid DHCPV6 message has been dropped.

References #

Event ID 10009 — [EVENT_DHCPV6_DROP_WRONG_SERVER] A DHCPv6 message that wasn't meant for this server has been dropped.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

A DHCPV6 message that was not meant for this server has been dropped.

Message #

A DHCPV6 message that was not meant for this server has been dropped.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server.

Message #

DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server.

References #

Event ID 10011 — [EVENT_DHCPV6_SERVER_AUDIT_LOG_APPEND_FAILED] DHCPv6 audit log file can't be appended, Error Code returned %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPV6 audit log file cannot be appended, Error Code returned .

Message #

DHCPV6 audit log file cannot be appended, Error Code returned %1.

References #

Event ID 10012 — [EVENT_DHCPV6_DROP_UNAUTH] A DHCPv6 message has been dropped because the server isn't authorized to process the message.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

A DHCPV6 message has been dropped because the server is not authorized to process the message.

Message #

A DHCPV6 message has been dropped because the server is not authorized to process the message.

References #

Event ID 10013 — [EVENT_DHCPv6_SERVER_INIT_AUDIT_LOG_FAILED] The DHCPv6 service failed to initialize the audit log.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 service failed to initialize the audit log. The following error occurred.

Message #

The DHCPv6 service failed to initialize the audit log. The following error occurred: 
%1

References #

Event ID 10014 — [EVENT_DHCPV6_SERVER_MOVE_AUDIT_LOG_FAILED] DHCPv6 audit log file couldn't be backed up.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 audit log file could not be backed up. Error code.

Message #

DHCPv6 audit log file could not be backed up.  Error code %1

References #

Event ID 10015 — [EVENT_DHCPV6_SERVER_AUDITLOG_PATH_NOT_ACCESSIBLE] The DHCPv6 service was unable to access path specified for the audit log.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

AThe DHCPv6 service was unable to access path specified for the audit log.

Message #

AThe DHCPv6 service was unable to access path specified for the audit log.

References #

Event ID 10016 — [EVENT_DHCPV6_SERVER_INIT_WINSOCK_FAILED] The DHCPv6 service failed to initialize Winsock startup.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 service failed to initialize Winsock startup. The following error occurred .

Message #

The DHCPv6 service failed to initialize Winsock startup. The following error occurred %1.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Message #

The DHCPv6 service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCPv6 service.   This is not a recommended security configuration.

References #

Event ID 10018 — [EVENT_DHCPV6_SERVER_INTERFACE_NOTIFICATION] The DHCPv6 Server failed to receive a notification of interface list changes.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCPv6 service.

Message #

The DHCPv6 Server failed to receive a notification of interface list changes.  Some of the interfaces will not be enabled in the DHCPv6 service.

References #

Event ID 10019 — [EVENT_DHCPV6_SERVER_INIT_CONFIG_FAILED] The DHCPv6 service failed to initialize its configuration parameters.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 service failed to initialize its configuration parameters. The following error occurred.

Message #

The DHCPv6 service failed to initialize its configuration parameters. The following error occurred: 
%1.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 service failed to initialize the database. The following error occurred.

Message #

DHCPv6 service failed to initialize the database. The following error occurred: 
%1.

References #

Event ID 10022 — [EVENT_DHCPV6_SERVER_INIT_AND_READY] The DHCPv6 service has initialized and is ready to serve.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCPv6 service has initialized and is ready to serve.

Message #

The DHCPv6 service has initialized and is ready to serve.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCPv6 Server is unable to bind to UDP port number as it is used by another application. This port must be made available to DHCPv6 Server to start servicing the clients.

Message #

DHCPv6 Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available to DHCPv6 Server to start servicing the clients.

References #

Event ID 10024 — [ERROR_LAST_DHCPV6_SERVER_ERROR] ERROR_LAST_DHCPV6_SERVER_ERROR

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

ERROR_LAST_DHCPV6_SERVER_ERROR.

Message #

ERROR_LAST_DHCPV6_SERVER_ERROR

References #

Event ID 10025 — [EVENT_DHCPV6_DNSDHCID_FAIL] The DNS registration for DHCPv6 Client IPv6 address %1, FQDN %2 and DHCID %3 have been denied.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DNS registration for DHCPv6 Client IPv6 address , FQDN and DHCID has been denied as there is probably an existing client with same FQDN already registered with DNS.

Message #

The DNS registration for DHCPv6 Client IPv6 address %1 , FQDN %2 and DHCID %3 has been denied as there is probably an existing client with same FQDN already registered with DNS.

References #

Event ID 20035 — [EVENT_SERVER_INTERFACE_NOTIFICATION] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The DHCP Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCP service.

Message #

The DHCP Server failed to receive a notification of interface list changes.  Some of the interfaces will not be enabled in the DHCP service.

References #

Event ID 20058 — [DHCPv4HA.BndUpd] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20058 — [DHCPv4HA.BndUpd] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20059 — [DHCPv4HA.BndAck] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20059 — [DHCPv4HA.BndAck] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20060 — [DHCPv4HA.Connect] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20060 — [DHCPv4HA.Connect] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20061 — [DHCPv4HA.ConnectAck] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20061 — [DHCPv4HA.ConnectAck] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20062 — [DHCPv4HA.UpdReqAll] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20062 — [DHCPv4HA.UpdReqAll] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20063 — [DHCPv4HA.UpdDone] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20063 — [DHCPv4HA.UpdDone] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20064 — [DHCPv4HA.UpdReq] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20064 — [DHCPv4HA.UpdReq] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20065 — [DHCPv4HA.State] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20065 — [DHCPv4HA.State] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20066 — [DHCPv4HA.Contact] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20066 — [DHCPv4HA.Contact] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20067 — [DHCPv4HA.Disconnect] %1 %3

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

References #

Event ID 20067 — [DHCPv4HA.Disconnect] RelationshipName PktContents

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Message #

%1 %3

Fields #

NameDescription
RelationshipName UnicodeString—
BufferSize UInt32—
PktContents Binary—

References #

Event ID 20068 — [DHCPv4HA.ScavengerStart] Scavenger started.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scavenger started.

References #

Event ID 20068 — Scavenger started.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

Scavenger started.

Message #

Scavenger started.

References #

Event ID 20069 — [DHCPv4HA.ScavengerEnd] Scavenger ended.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scavenger ended.

References #

Event ID 20069 — Scavenger ended.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

Scavenger ended.

Message #

Scavenger ended.

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

DHCP Server is unable to bind to UDP port number as it is used by another application. This port must be made available to DHCP Server to start servicing the clients.

Message #

DHCP Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available to DHCP Server to start servicing the clients.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
FilterNotifications

Description

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.

Message #

DHCP Services were denied to machine with hardware address %1, hardware type %4 and FQDN/Hostname %2 because it matched entry %3 in the Deny List.

Fields #

NameDescription
MACAddress UnicodeString—
HostName UnicodeString—
DenyFilter UnicodeString—
HWType UInt32—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
FilterNotifications

Description

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 Allow List.

Message #

DHCP Services were denied to machine with hardware address %1, hardware type %3 and FQDN/Hostname %2 because it did not match any entry in the Allow List.

Fields #

NameDescription
MACAddress UnicodeString—
HostName UnicodeString—
HWType UInt32—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

No DHCP clients are being served, as the Allow list is empty and the server was configured to provide DHCP services, to clients whose hardware addresses are present in the Allow List.

Message #

No DHCP clients are being served,  as the Allow list is empty and the server was configured to provide DHCP services, to clients whose hardware addresses are present in the Allow List.

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 ...

Provider
Microsoft-Windows-DHCP-Server
Channel
FilterNotifications

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 #

DHCP Services were denied to machine with hardware address %1, hardware type %4 and unspecified FQDN/Hostname%2 because it matched entry %3 in the Deny List.

Fields #

NameDescription
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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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 ...

Provider
Microsoft-Windows-DHCP-Server
Channel
FilterNotifications

Description

DHCP Services were denied to machine with hardware address MACAddress, hardware type HWType and unspecified FQDN/HostnameHostName because it did not match any entry in the Allow List.

Message #

DHCP Services were denied to machine with hardware address %1, hardware type %3 and unspecified FQDN/Hostname%2 because it did not match any entry in the Allow List.

Fields #

NameDescription
MACAddress UnicodeString—
HostName UnicodeString—
HWType UInt32—

References #

Event ID 20161 — [DHCPv4HA.AddrAllocationTriggered] Address allocation triggered for the failover relationship %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Address allocation triggered for the failover relationship .

References #

Event ID 20161 — Address allocation triggered for the failover relationship RelationshipName.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

Address allocation triggered for the failover relationship RelationshipName.

Message #

Address allocation triggered for the failover relationship %1.

Fields #

NameDescription
RelationshipName UnicodeString—

References #

Event ID 20162 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scavenger started purging stateless entries.

Event ID 20162 — Scavenger started purging stateless entries.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

Scavenger started purging stateless entries.

Message #

Scavenger started purging stateless entries.

Event ID 20163 — [DHCPv4Stateless.ScavengerEnd] Scavenger finished purging stateless entries.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

Scavenger finished purging stateless entries.

References #

Event ID 20163 — Scavenger finished purging stateless entries.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

Scavenger finished purging stateless entries.

Message #

Scavenger finished purging stateless entries.

References #

Event ID 20164 — [DHCPv4HA.TotalLeasesDeleted] The total leases deleted in scavenger are %1

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Description

The total leases deleted in scavenger are.

References #

Event ID 20164 — The total leases deleted in scavenger are number.

Provider
Microsoft-Windows-DHCP-Server
Channel
System

Description

The total leases deleted in scavenger are number.

Message #

The total leases deleted in scavenger are %1

Fields #

NameDescription
number UInt32—

References #

Event ID 20165 — [DHCPv4HA.FailoverScopeDeleted] Scope %1 which was part of failover relationship %2 wasn't found in DHCP server database.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
InitializeFailover

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
System
Task
DHCPFailover
Opcode
InitializeFailover

Description

Scope Server which was part of failover relationship RelationName was not found in DHCP server database. Please restore the DHCP server database.

Message #

Scope %1 which was part of failover relationship %2 was not found in DHCP server database. Please restore the DHCP server database.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20220 — [DHCPv4.UpdateServerPolicyState] Policy %2 for server is %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy for server is .

References #

Event ID 20220 — Policy PolicyName for server is String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy PolicyName for server is String1.

Message #

Policy %2 for server is %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20221 — [DHCPv4.UpdateScopePolicyState] Policy %2 for scope %3 is %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy for scope is .

References #

Event ID 20221 — Policy PolicyName for scope IP_ScopeName is String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy PolicyName for scope IP_ScopeName is String1.

Message #

Policy %2 for scope %3 is %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20222 — [DHCPv4.UpdateServerPolicyExpr] The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The conditions for server policy PolicyName have been set to String1. The conditions are grouped by logical operator String2.

Message #

The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.

Fields #

NameDescription
String1 UnicodeString—
String2 UnicodeString—
PolicyName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The conditions for scope IP_ScopeName policy PolicyName have been set to String1. The conditions are grouped by logical operator String2.

Message #

The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2.

Fields #

NameDescription
String1 UnicodeString—
String2 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20224 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

A new server wide IPv4 policy was created. The processing order of the policy is .

Fields #

NameDescription
PolicyName UnicodeString—
ProcessingOrder UInt32—

Event ID 20224 — A new server wide IPv4 policy PolicyName was created.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

A new server wide IPv4 policy PolicyName was created. The processing order of the policy is ProcessingOrder.

Message #

A new server wide IPv4 policy %1 was created. The processing order of the policy is %2.

Fields #

NameDescription
PolicyName UnicodeString—
ProcessingOrder UInt32—

Event ID 20225 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

A new scope policy was created in scope . The processing order of the policy is .

Fields #

NameDescription
PolicyName UnicodeString—
ProcessingOrder UInt32—
IP_ScopeName UnicodeString—

Event ID 20225 — A new scope policy PolicyName was created in scope IP_ScopeName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

A new scope policy PolicyName was created in scope IP_ScopeName. The processing order of the policy is ProcessingOrder.

Message #

A new scope policy %1 was created in scope %3. The processing order of the policy is %2.

Fields #

NameDescription
PolicyName UnicodeString—
ProcessingOrder UInt32—
IP_ScopeName UnicodeString—

Event ID 20226 — [DHCPv4.DeleteServerPolicy] Policy %1 was deleted from server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy was deleted from server.

References #

Event ID 20226 — Policy PolicyName was deleted from server.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy PolicyName was deleted from server.

Message #

Policy %1 was deleted from server.

Fields #

NameDescription
PolicyName UnicodeString—

References #

Event ID 20227 — [DHCPv4.DeleteScopePolicy] Policy %1 was deleted from scope %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy was deleted from scope .

References #

Event ID 20227 — Policy PolicyName was deleted from scope IP_ScopeName.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Policy PolicyName was deleted from scope IP_ScopeName.

Message #

Policy %1 was deleted from scope %2.

Fields #

NameDescription
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20228 — [DHCPv4.SetScopePolicyRange] The IP address range from %1 was set for the scope %3 policy %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The IP address range from String1 was set for the scope IP_ScopeName policy PolicyName.

Message #

The IP address range from %1 was set for the scope %3 policy %2.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20229 — [DHCPv4.RemoveScopePolicyRange] The IP address range from %1 was removed from the scope %3 policy %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The IP address range from String1 was removed from the scope IP_ScopeName policy PolicyName.

Message #

The IP address range from %1 was removed from the scope %3 policy %2.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20230 — [DHCPv4.SetServerPolicyOption] The value %2 was set for the option %1 for the server policy %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The value OptionValue was set for the option OptionName for the server policy PolicyName.

Message #

The value %2 was set for the option %1 for the server policy %3.

Fields #

NameDescription
OptionName UnicodeString—
OptionValue UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20231 — [DHCPv4.SetScopePolicyOption] The value %2 was set for the option %1 for the scope %4 policy %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The value OptionValue was set for the option OptionName for the scope IP_ScopeName policy PolicyName.

Message #

The value %2 was set for the option %1 for the scope %4 policy %3.

Fields #

NameDescription
OptionName UnicodeString—
OptionValue UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20232 — [DHCPv4.UnsetServerPolicyOption] The value %2 was removed from the option %1 for the server policy %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The value OptionValue was removed from the option OptionName for the server policy PolicyName.

Message #

The value %2 was removed from the option %1 for the server policy %3.

Fields #

NameDescription
OptionName UnicodeString—
OptionValue UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20233 — [DHCPv4.UnsetScopePolicyOption] The value %2 was removed from the option %1 for the scope %4 policy %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

The value OptionValue was removed from the option OptionName for the scope IP_ScopeName policy PolicyName.

Message #

The value %2 was removed from the option %1 for the scope %4 policy %3.

Fields #

NameDescription
OptionName UnicodeString—
OptionValue UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20234 — [DHCPv4.UpdateServerPolicyName] Server policy %2 has been renamed to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Server policy has been renamed to .

References #

Event ID 20234 — Server policy PolicyName has been renamed to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Server policy PolicyName has been renamed to String1.

Message #

Server policy %2 has been renamed to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20235 — [DHCPv4.UpdateScopePolicyName] Scope %3 policy %2 has been renamed to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Scope policy has been renamed to .

References #

Event ID 20235 — Scope IP_ScopeName policy PolicyName has been renamed to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Scope IP_ScopeName policy PolicyName has been renamed to String1.

Message #

Scope %3 policy %2 has been renamed to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20236 — [DHCPv4.UpdateServerPolicyDescription] Description of server policy %2 was set to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Description of server policy was set to .

References #

Event ID 20236 — Description of server policy PolicyName was set to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Description of server policy PolicyName was set to String1.

Message #

Description of server policy %2 was set to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20237 — [DHCPv4.UpdateScopePolicyDescription] Description of scope %3 policy %2 was set to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Description of scope policy was set to .

References #

Event ID 20237 — Description of scope IP_ScopeName policy PolicyName was set to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Description of scope IP_ScopeName policy PolicyName was set to String1.

Message #

Description of scope %3 policy %2 was set to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20238 — [DHCPv4.UpdateServerPolicyProcOrder] Processing order of server policy %3 was changed to %1 from %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Processing order of server policy PolicyName was changed to Integer1 from Integer2.

Message #

Processing order of server policy %3 was changed to %1 from %2.

Fields #

NameDescription
Integer1 UInt32—
Integer2 UInt32—
PolicyName UnicodeString—

References #

Event ID 20239 — [DHCPv4.UpdateScopePolicyProcOrder] Processing order of scope %4 policy %3 was changed to %1 from %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

Processing order of scope IP_ScopeName policy PolicyName was changed to Integer1 from Integer2.

Message #

Processing order of scope %4 policy %3 was changed to %1 from %2.

Fields #

NameDescription
Integer1 UInt32—
Integer2 UInt32—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20240 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CreateFailover

Fields #

NameDescription
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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CreateFailover

Message #

A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, mode: load balance, maximum client lead time: %4 seconds, load balance percentage on this server: %5, auto state switchover interval: %6 seconds.

Fields #

NameDescription
Server1Name UnicodeString—
Server2Name UnicodeString—
RelationshipName UnicodeString—
Mclt UInt32—
Percentage UInt32—
AutoSwitchoverInterval UInt32—

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CreateFailover

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CreateFailover

Message #

A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, mode: hot standby, maximum client lead time: %4 seconds, reserve address percentage on standby server: %5, auto state switchover interval: %6 seconds, standby server: %7.

Fields #

NameDescription
Server1Name UnicodeString—
Server2Name UnicodeString—
RelationshipName UnicodeString—
Mclt UInt32—
Percentage UInt32—
AutoSwitchoverInterval UInt32—
StandbyServer UnicodeString—

References #

Event ID 20242 — [DHCPv4.DeleteFailoverRelationship] Failover relationship %1 between %2 and %3 has been deleted.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
DeleteFailover

Description

Failover relationship between and has been deleted.

References #

Event ID 20242 — Failover relationship RelationshipName between Server1Name and Server2Name has been deleted.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
DeleteFailover

Description

Failover relationship RelationshipName between Server1Name and Server2Name has been deleted.

Message #

Failover relationship %1 between %2 and %3 has been deleted.

Fields #

NameDescription
RelationshipName UnicodeString—
Server1Name UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20243 — [DHCPv4.AddScopeRelationship] Scope %1 has been added to the failover relationship %2 with server %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
AddFailoverScope

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
AddFailoverScope

Description

Scope ScopeAddress has been added to the failover relationship RelationshipName with server Server2Name.

Message #

Scope %1 has been added to the failover relationship %2 with server %3.

Fields #

NameDescription
ScopeAddress UInt32—
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20244 — [DHCPv4.DeleteScopeRelationship] Scope %1 has been removed from the failover relationship %2 with server %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
RemoveFailoverScope

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
RemoveFailoverScope

Description

Scope ScopeAddress has been removed from the failover relationship RelationshipName with server Server2Name.

Message #

Scope %1 has been removed from the failover relationship %2 with server %3.

Fields #

NameDescription
ScopeAddress UInt32—
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

The failover configuration parameter MCLT for failover relationship RelationshipName with server Server2Name has been changed from OldValue seconds to NewValue seconds.

Message #

The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—
OldValue UInt32—
NewValue UInt32—

References #

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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 #

The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

The failover configuration parameter reserve address percentage for failover relationship RelationshipName with server Server2Name has been changed from OldValue to NewValue.

Message #

The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—
OldValue UInt32—
NewValue UInt32—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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 #

The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

The failover configuration parameter mode for failover relationship RelationshipName with server Server2Name has been changed from hot standby to load balance.

Message #

The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

The failover configuration parameter mode for failover relationship RelationshipName with server Server2Name has been changed from load balance to hot standby.

Message #

The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20251 — The failover state of server: Server for failover relationship: RelationName changed from: OldState to NewState.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
FailoverStateChange

Description

The failover state of server: Server for failover relationship: RelationName changed from: OldState to NewState.

Message #

The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

Fields #

NameDescription
Server UnicodeString—
RelationName UnicodeString—
OldState UnicodeString—
NewState UnicodeString—

References #

Event ID 20251 — [DHCPv4.ChangeFailoverRelationState] The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
FailoverStateChange

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
FailoverStateChange

Description

The failover state of server: Server for failover relationship: RelationName changed from: OldState to NewState.

Message #

The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

Fields #

NameDescription
Server UnicodeString—
RelationName UnicodeString—
OldState UnicodeString—
NewState UnicodeString—

References #

Event ID 20252 — [DHCPv4.ChangeFailoverRelationStateError] The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
FailoverStateChange

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
TimeOutOfSync

Description

The server detected that it is out of time synchronization with partner server: Server for failover relationship: RelationName. The time is out of sync by: time seconds .

Message #

The server detected that it is out of time synchronization with partner server: %1 for failover relationship: %2.  The time is out of sync by: %3 seconds .

Fields #

NameDescription
Server UnicodeString—
RelationName UnicodeString—
time UInt32—

References #

Event ID 20253 — [DHCPv4.FailoverServerTimeSync] The server detected that it's out of time synchronization with partner server: %1 for failover relationship: %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
TimeOutOfSync

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 .

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
CommUp

Description

Server has established contact with failover partner server Server for relationship RelationName .

Message #

Server has established contact with failover partner server %1 for relationship %2 .

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20254 — [DHCPv4.FailoverCommUp] Server has established contact with failover partner server %1 for relationship %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CommUp

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 .

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
CommDown

Description

Server has lost contact with failover partner server Server for relationship RelationName .

Message #

Server has lost contact with failover partner server  %1 for relationship %2 .

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20255 — [DHCPv4.FailoverCommDown] Server has lost contact with failover partner server %1 for relationship %2.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CommDown

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-UPDATE from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
FailoverStateChange

Description

The failover state of server: Server for failover relationship: RelationName changed to : NewState.

Message #

The failover state of server: %1 for failover relationship: %2 changed to : %3.

Fields #

NameDescription
Server UnicodeString—
RelationName UnicodeString—
NewState UnicodeString—

References #

Event ID 20259 — [DHCPv4.ChangeFailoverRelationStateNoPrevState] The failover state of server: %1 for failover relationship: %2 changed to: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
FailoverStateChange

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
FailoverStateChange

Description

The failover state of server: Server for failover relationship: RelationName changed to: NewState.

Message #

The failover state of server: %1 for failover relationship: %2 changed to: %3.

Fields #

NameDescription
Server UnicodeString—
RelationName UnicodeString—
NewState UnicodeString—

References #

Event ID 20260 — [DHCPv4.ChangeFailoverRelationStateErrorNoPrevState] The failover state of server: %1 for failover relationship: %2 changed to: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
FailoverStateChange

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-ACK from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-ACK from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message BINDING-ACK from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECT from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20264 — [DHCPv4.AuthFailedConnectMsgDigestFailedToCompare] Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECT from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  CONNECT from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20265 — [DHCPv4.AuthFailedConnectMsgDigestNotConfigured] Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECT from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  CONNECT from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20266 — [DHCPv4.AuthFailedConnectMsgDigestNotPresent] Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECTACK from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20267 — [DHCPv4.AuthFailedConnectAckMsgDigestFailedToCompare] Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECTACK from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20268 — [DHCPv4.AuthFailedConnectAckMsgDigestNotConfigured] Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONNECTACK from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20269 — [DHCPv4.AuthFailedConnectAckMsgDigestNotPresent] Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQALL from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20270 — [DHCPv4.AuthFailedUpdReqAllMsgDigestFailedToCompare] Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQALL from server for failover relationship was rejected because message digest failed to compare.

References #

Event ID 20271 — Failover protocol message UPDREQALL from server Server for failover relationship RelationName was rejected because message digest was not configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQALL from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQALL from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20272 — [DHCPv4.AuthFailedUpdReqAllMsgDigestNotPresent] Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDDONE from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20273 — [DHCPv4.AuthFailedUpdDoneMsgDigestFailedToCompare] Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDDONE from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20274 — [DHCPv4.AuthFailedUpdDoneMsgDigestNotConfigured] Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDDONE from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20275 — [DHCPv4.AuthFailedUpdDoneMsgDigestNotPresent] Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQ from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20276 — [DHCPv4.AuthFailedUpdReqMsgDigestFailedToCompare] Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQ from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20277 — [DHCPv4.AuthFailedUpdReqMsgDigestNotConfigured] Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message UPDREQ from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20278 — [DHCPv4.AuthFailedUpdReqMsgDigestNotPresent] Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message STATE from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20279 — [DHCPv4.AuthFailedStateMsgDigestFailedToCompare] Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message STATE from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  STATE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20280 — [DHCPv4.AuthFailedStateMsgDigestNotConfigured] Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message STATE from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  STATE from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20281 — [DHCPv4.AuthFailedStateMsgDigestNotPresent] Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONTACT from server Server for failover relationship RelationName was rejected because message digest failed to compare.

Message #

Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20282 — [DHCPv4.AuthFailedContactMsgDigestFailedToCompare] Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONTACT from server Server for failover relationship RelationName was rejected because message digest was not configured.

Message #

Failover protocol message  CONTACT from server %1 for failover relationship %2 was rejected because message digest was not configured.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20283 — [DHCPv4.AuthFailedContactMsgDigestNotConfigured] Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest wasn't configured.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Description

Failover protocol message CONTACT from server Server for failover relationship RelationName is rejected because message digest was not present.

Message #

Failover protocol message  CONTACT from server %1 for failover relationship %2 is rejected because message digest was not present.

Fields #

NameDescription
Server UInt32—
RelationName UnicodeString—

References #

Event ID 20284 — [DHCPv4.AuthFailedContactMsgDigestNotPresent] Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest wasn't present.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
MessageAuthentication

Message #

An invalid cryptographic algorithm %1 was specified for failover message authentication in FailoverCryptoAlgorithm under registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters\Failover. The operation is halted.

Fields #

NameDescription
Message UnicodeString—

References #

Event ID 20285 — [DHCPv4.InvalidAlgorithmProvider] An invalid cryptographic algorithm %1 was specified for failover message authentication.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
MessageAuthentication

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
BINDING_UPDATE

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 #

BINDING UPDATE message for IP address %1 could not be replicated to the partner server %2 of failover relation %3 as the internal BINDING UPDATE queue is full.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_UPDATE

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents

Message #

DHCP client request from %1 was dropped since the applicable IP address ranges in scope/superscope %2 are out of available IP addresses. This could be because of IP address ranges of a policy being out of available IP addresses.

Fields #

NameDescription
ClientID UnicodeString—
ScopeName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
FailoverIPPoolTakeover

Message #

This DHCP server %1 has transitioned to a PARTNER DOWN state for the failover relationship %2 and the MCLT period of %3 seconds has expired. The server has taken over the free IP address pool of the partner server %4 for all scopes which are part of the failover relationship.

Fields #

NameDescription
LocalServer UnicodeString—
RelationName UnicodeString—
Mclt UInt32—
PartnerServer UnicodeString—

Event ID 20288 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
FailoverIPPoolTakeover

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_UPDATE

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
BINDING_UPDATE

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 #

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.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_UPDATE

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
BINDING_UPDATE

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 #

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.

Fields #

NameDescription
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:...

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
BINDING_ACK

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 #

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.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_ACK

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...

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
DHCPFailover
Opcode
BINDING_ACK

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 #

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.

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_REQUEST

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_REQUEST

Description

A UPDREQ message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDREQ message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20294 — [DHCPv4.RecvUpdReqMessage] A UPDREQ message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_REQUEST

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_REQUEST

Description

A UPDREQ message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDREQ message with transaction id: %1 was received from partner server: %2 for failover relationship: %3

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20295 — [DHCPv4.SendUpdDoneMessage] A UPDDONE message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_DONE

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_DONE

Description

A UPDDONE message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDDONE message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20296 — [DHCPv4.RecvUpdDoneMessage] A UPDDONE message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_DONE

Description

A UPDDONE message with transaction id: was received from partner server: for failover relationship: .

References #

Event ID 20296 — A UPDDONE message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_DONE

Description

A UPDDONE message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDDONE message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20297 — [DHCPv4.SendUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_REQUEST_ALL

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_REQUEST_ALL

Description

A UPDREQALL message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDREQALL message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20298 — [DHCPv4.RecvUpdReqAllMessage] A UPDREQALL message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
UPDATE_REQUEST_ALL

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
UPDATE_REQUEST_ALL

Description

A UPDREQALL message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Message #

A UPDREQALL message with transaction id: %1 was received from partner server: %2 for failover relationship: %3

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20299 — [DHCPv4.SendContactMessage] A CONTACT message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONTACT

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONTACT

Description

A CONTACT message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.

Message #

A CONTACT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20300 — [DHCPv4.RecvContactMessage] A CONTACT message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONTACT

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONTACT

Description

A CONTACT message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Message #

A CONTACT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20301 — [DHCPv4.SendConnectMessage] A CONNECT message with transaction ID: %1 was sent to partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT

Description

A CONNECT message with transaction id: TransactionId was sent to partner server: PartnerServer for failover relationship: RelationName.

Message #

A CONNECT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20302 — [DHCPv4.RecvConnectMessage] A CONNECT message with transaction ID: %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT

Description

A CONNECT message with transaction id: TransactionId was received from partner server: PartnerServer for failover relationship: RelationName.

Message #

A CONNECT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
STATE

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
STATE

Description

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.

Message #

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.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—
state UnicodeString—
startTimeOfState UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
STATE

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
STATE

Description

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.

Message #

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.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—
state UnicodeString—
startTimeOfState UnicodeString—

References #

Event ID 20305 — [DHCPv4.SendConnectAckMessage] A CONNECTACK message with transaction ID %1 was sent to partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT_ACK

Description

A CONNECTACK message with transaction id TransactionId was sent to partner server : PartnerServer for failover relationship: RelationName.

Message #

A CONNECTACK message with transaction id %1 was sent to partner server : %2  for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

Event ID 20306 — [DHCPv4.RecvConnectAckMessage] A CONNECTACK message with transaction ID %1 was received from partner server: %2 for failover relationship: %3.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT_ACK

Description

A CONNECTACK message with transaction id TransactionId was received from partner server : PartnerServer for failover relationship: RelationName.

Message #

A CONNECTACK message with transaction id %1 was received from partner server : %2  for failover relationship: %3.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
BINDING_ACK

Description

A BINDING-ACK message with transaction id: TransactionId was sent for IP address: IPAddress to partner server: PartnerServer for failover relationship: RelationName.

Message #

A BINDING-ACK message with transaction id: %1 was sent for IP address: %2  to partner server: %3 for failover relationship: %4.

Fields #

NameDescription
TransactionId UInt32—
IPAddress UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
BINDING_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
BINDING_ACK

Description

A BINDING-ACK message with transaction id: TransactionId was received for IP address: IPAddress from partner server: PartnerServer for failover relationship: RelationName.

Message #

A BINDING-ACK message with transaction id: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4.

Fields #

NameDescription
TransactionId UInt32—
IPAddress UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT_ACK

Description

A CONNECTACK message with transaction id TransactionId was sent to partner server : PartnerServer for failover relationship: RelationName with reject reason: state.

Message #

A CONNECTACK message with transaction id %1 was sent to partner server : %2  for failover relationship: %3 with reject reason: %4.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—
state UnicodeString—

References #

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
CONNECT_ACK

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
AuditLog
Task
DHCPFailover
Opcode
CONNECT_ACK

Description

A CONNECTACK message with transaction id TransactionId was received from partner server : PartnerServer for failover relationship: RelationName with reject reason: state.

Message #

A CONNECTACK message with transaction id %1 was received from partner server : %2  for failover relationship: %3 with reject reason: %4.

Fields #

NameDescription
TransactionId UInt32—
PartnerServer UnicodeString—
RelationName UnicodeString—
state UnicodeString—

References #

Event ID 20311 — [DHCPv4.UpdateSharedSecret] The shared secret for failover relationship %2 with server %1 has been changed.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

The shared secret for failover relationship Server2Name with server RelationshipName has been changed.

Message #

The shared secret for failover relationship %2 with server %1 has been changed.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20312 — [DHCPv4.EnabledSharedSecret] Message authentication for failover relationship %2 with server %1 has been enabled.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

Message authentication for failover relationship Server2Name with server RelationshipName has been enabled.

Message #

Message authentication for failover relationship %2 with server %1 has been enabled.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20313 — [DHCPv4.DisabledSharedSecret] Message authentication for failover relationship %2 with server %1 has been disabled.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

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.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
DHCPFailover
Opcode
ChangeFailoverConfig

Description

Message authentication for failover relationship Server2Name with server RelationshipName has been disabled.

Message #

Message authentication for failover relationship %2 with server %1 has been disabled.

Fields #

NameDescription
RelationshipName UnicodeString—
Server2Name UnicodeString—

References #

Event ID 20314 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational

Fields #

NameDescription
Message AnsiString—

Event ID 20314 —

Provider
Microsoft-Windows-DHCP-Server
Channel
DebugLogs

Message #

%1

Fields #

NameDescription
Message AnsiString—

Event ID 20315 — [DHCPv4.UpdateScopePolicyDNSSuffix] DNSSuffix of scope %3 policy %2 was set to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

DNSSuffix of scope policy was set to .

References #

Event ID 20315 — DNSSuffix of scope IP_ScopeName policy PolicyName was set to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

DNSSuffix of scope IP_ScopeName policy PolicyName was set to String1.

Message #

DNSSuffix of scope %3 policy %2 was set to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—
IP_ScopeName UnicodeString—

References #

Event ID 20316 — [DHCPv4.UpdateServerPolicyDNSSuffix] DNSSuffix of server policy %2 was set to %1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

DNSSuffix of server policy was set to .

References #

Event ID 20316 — DNSSuffix of server policy PolicyName was set to String1.

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
Policy

Description

DNSSuffix of server policy PolicyName was set to String1.

Message #

DNSSuffix of server policy %2 was set to %1.

Fields #

NameDescription
String1 UnicodeString—
PolicyName UnicodeString—

References #

Event ID 20317 — Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

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 #

Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3. This is likely to be because the forward lookup zone for this record does not exist on the DNS server.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20317 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

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 #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

Description

Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.

Message #

Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20318 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

Description

Forward record registration for IPv4 address and FQDN failed with error .

Fields #

NameDescription
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).

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

Description

Forward record registration for IPv4 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).

Message #

Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
Errorvalue UInt32—
operation UnicodeString—

Event ID 20319 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

Description

Forward record registration for IPv4 address and FQDN failed with error ().

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

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 #

PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20320 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

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 #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20321 — PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

Description

PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error ErrorType.

Message #

PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20321 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

Description

PTR record registration for IPv4 address and FQDN failed with error .

Fields #

NameDescription
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).

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration.

Description

PTR record registration for IPv4 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).

Message #

PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
Errorvalue UInt32—
operation UnicodeString—

Event ID 20322 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration.

Description

PTR record registration for IPv4 address and FQDN failed with error ().

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

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 #

Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3. This is likely to be because the forward lookup zone for this record does not exist on the DNS server.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20323 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

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 #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

Description

Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.

Message #

Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20324 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

Description

Forward record registration for IPv6 address and FQDN failed with error .

Fields #

NameDescription
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).

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

Description

Forward record registration for IPv6 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).

Message #

Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
Errorvalue UInt32—
operation UnicodeString—

Event ID 20325 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

Description

Forward record registration for IPv6 address and FQDN failed with error ().

Fields #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

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 #

PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20326 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

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 #

NameDescription
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.

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

Description

PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error ErrorType.

Message #

PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3.

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
ErrorType UnicodeString—
operation UnicodeString—

Event ID 20327 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

Description

PTR record registration for IPv6 address and FQDN failed with error .

Fields #

NameDescription
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).

Provider
Microsoft-Windows-DHCP-Server
Channel
DhcpAdminEvents
Task
NameRegistration._125

Description

PTR record registration for IPv6 address IP_Name and FQDN FQDNName failed with error Errorvalue (operation).

Message #

PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
Errorvalue UInt32—
operation UnicodeString—

Event ID 20328 —

Provider
Microsoft-Windows-DHCP-Server
Channel
Operational
Task
NameRegistration._125

Description

PTR record registration for IPv6 address and FQDN failed with error ().

Fields #

NameDescription
IP_Name UnicodeString—
FQDNName UnicodeString—
Errorvalue UInt32—
operation UnicodeString—