dhcpsapi.dll.mui DHCP Server API Stub DLL 4ad3daf3f1b08f744341477b8001d350

File name:	dhcpsapi.dll.mui
Size:	132608 byte
MD5:	4ad3daf3f1b08f744341477b8001d350
SHA1:	5fc5e2d9dc17bfc83f0106155d7b842779eea66c
SHA256:	f9fa3f82b5b00704a9f742488113f35c662cbc0aeec08610556116dd26c73167
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	English (U.S.)	English
211	DHCP Users	DHCP Users
212	Members who have view-only access to the DHCP service	Members who have view-only access to the DHCP service
213	DHCP Administrators	DHCP Administrators
214	Members who have administrative access to the DHCP Service	Members who have administrative access to the DHCP Service
0x3E8	The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below.	The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below.
0x3E9	The DHCP service failed to register with Service Controller. The following error occurred: %n%1.	The DHCP service failed to register with Service Controller. The following error occurred: %n%1.
0x3EA	The DHCP service failed to initialize its global parameters. The following error occurred: %n%1	The DHCP service failed to initialize its global parameters. The following error occurred: %n%1
0x3EB	The DHCP service failed to initialize its registry parameters. The following error occurred: %n%1	The DHCP service failed to initialize its registry parameters. The following error occurred: %n%1
0x3EC	The DHCP service failed to initialize the database. The following error occurred: %n%1	The DHCP service failed to initialize the database. The following error occurred: %n%1
0x3ED	The DHCP service failed to initialize Winsock startup. The following error occurred: %n%1	The DHCP service failed to initialize Winsock startup. The following error occurred: %n%1
0x3EE	The DHCP service failed to start as a RPC server. The following error occurred : %n%1	The DHCP service failed to start as a RPC server. The following error occurred : %n%1
0x3EF	The DHCP service failed to initialize Winsock data. The following error occurred: %n%1	The DHCP service failed to initialize Winsock data. The following error occurred: %n%1
0x3F0	The DHCP service is shutting down due to the following error: %n%1	The DHCP service is shutting down due to the following error: %n%1
0x3F1	The DHCP service encountered the following error while cleaning up the pending client records: %n%1	The DHCP service encountered the following error while cleaning up the pending client records: %n%1
0x3F2	The DHCP service encountered the following error while cleaning up the database: %n%1	The DHCP service encountered the following error while cleaning up the database: %n%1
0x3F3	The DHCP service issued a NACK (negative acknowledgement message) to the client, %2, for the address, %1.	The DHCP service issued a NACK (negative acknowledgement message) to the client, %2, for the address, %1.
0x3F4	The DHCP client, %2, declined the address %1.	The DHCP client, %2, declined the address %1.
0x3F5	The DHCP Client, %2, released the address %1.	The DHCP Client, %2, released the address %1.
0x3F8	The DHCP service encountered the following error when backing up the database: %n%1	The DHCP service encountered the following error when backing up the database: %n%1
0x3F9	The DHCP service encountered the following error when backing up the registry configuration: %n%1	The DHCP service encountered the following error when backing up the registry configuration: %n%1
0x3FA	The DHCP service failed to restore the database. The following error occurred: %n%1	The DHCP service failed to restore the database. The following error occurred: %n%1
0x3FB	The DHCP service failed to restore the DHCP registry configuration. The following error occurred: %n%1	The DHCP service failed to restore the DHCP registry configuration. The following error occurred: %n%1
0x3FC	Scope, %1, is %2 percent full with only %3 IP addresses remaining.	Scope, %1, is %2 percent full with only %3 IP addresses remaining.
0x3FD	The DHCP service could not load the JET database library successfully.	The DHCP service could not load the JET database library successfully.
0x3FE	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.	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.
0x3FF	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.	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.
0x400	The DHCP service has initialized and is ready	The DHCP service has initialized and is ready
0x401	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.	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.
0x402	The DHCP service was unable to read the global BOOTP file name from the registry.	The DHCP service was unable to read the global BOOTP file name from the registry.
0x403	The audit log file cannot be appended.	The audit log file cannot be appended.
0x404	The DHCP service failed to initialize the audit log. The following error occurred: %n%1	The DHCP service failed to initialize the audit log. The following error occurred: %n%1
0x405	The DHCP service was unable to ping for a new IP address. The address was leased to the client.	The DHCP service was unable to ping for a new IP address. The address was leased to the client.
0x406	The audit log file could not be backed up. The following error occurred: %n%1	The audit log file could not be backed up. The following error occurred: %n%1
0x407	The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception. All further exceptions will be ignored.	The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception. All further exceptions will be ignored.
0x408	The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception and the .dll file could not be loaded.	The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception and the .dll file could not be loaded.
0x409	The DHCP service has successfully loaded one or more callout DLLs.	The DHCP service has successfully loaded one or more callout DLLs.
0x40A	The DHCP service has failed to load one or more callout DLLs. The following error occured: %n%1	The DHCP service has failed to load one or more callout DLLs. The following error occured: %n%1
0x40B	The DHCP service was unable to create or lookup the DHCP Users local group on this computer. The error code is in the data.	The DHCP service was unable to create or lookup the DHCP Users local group on this computer. The error code is in the data.
0x40C	The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer. The error code is in the data.	The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer. The error code is in the data.
0x40D	The DHCP service has started to clean up the database.	The DHCP service has started to clean up the database.
0x40E	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.	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.
0x40F	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.	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.
0x410	The DHCP service successfully restored the database.	The DHCP service successfully restored the database.
0x411	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.	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.
0x412	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	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
0x413	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 on the local machine has determined that it is authorized to start. It is servicing clients now.
0x414	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.	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.
0x415	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: %n%tThis machine belongs to a workgroup and has encountered another DHCP Server (belonging to a Windows Administrative Domain) servicing the same network. %n%n%tAn unexpected network error occurred.	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: %n%tThis machine belongs to a workgroup and has encountered another DHCP Server (belonging to a Windows Administrative Domain) servicing the same network. %n%n%tAn unexpected network error occurred.
0x416	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: %n%tThis 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). %n%n%tThis 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. %n%n%tSome unexpected network error occurred.	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: %n%tThis 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). %n%n%tThis 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. %n%n%tSome unexpected network error occurred.
0x417	The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now. %nThe 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).	The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now. %nThe 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).
0x418	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).	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).
0x419	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.	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.
0x41A	The DHCP/BINL service on the local machine encountered a network error. The error was: %3.	The DHCP/BINL service on the local machine encountered a network error. The error was: %3.
0x41B	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).	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).
0x41C	The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2.	The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2.
0x41D	The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2.	The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2.
0x41E	The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons.	The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons.
0x41F	The DHCP service was unable to impersonate the credentials necessary for DNS registrations: %n%1. The local system credentials is being used.	The DHCP service was unable to impersonate the credentials necessary for DNS registrations: %n%1. The local system credentials is being used.
0x420	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.	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.
0x421	The DHCP service was unable to convert the temporary database to ESE format: %n%1.	The DHCP service was unable to convert the temporary database to ESE format: %n%1.
0x422	The DHCP service failed to initialize its configuration parameters. The following error occurred: %n%1	The DHCP service failed to initialize its configuration parameters. The following error occurred: %n%1
0x423	The DHCP service failed to see a directory server for authorization.	The DHCP service failed to see a directory server for authorization.
0x424	The DHCP service was unable to access path specified for the audit log.	The DHCP service was unable to access path specified for the audit log.
0x425	The DHCP service was unable to access path specified for the database backups.	The DHCP service was unable to access path specified for the database backups.
0x426	The DHCP service was unable to access path specified for the database	The DHCP service was unable to access path specified for the database
0x427	There are no IP addresses available for lease in the scope or superscope \"%1\".	There are no IP addresses available for lease in the scope or superscope \"%1\".
0x428	There are no IP addresses available for BOOTP clients in the scope or superscope \"%1\".	There are no IP addresses available for BOOTP clients in the scope or superscope \"%1\".
0x429	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.	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.
0x42A	The DHCP/BINL service is not authorized in the directory service domain \"%2\" (Server IP Address %1)	The DHCP/BINL service is not authorized in the directory service domain \"%2\" (Server IP Address %1)
0x42B	The DHCP/BINL service is authorized in the directory service domain \"%2\" (Server IP Address %1)	The DHCP/BINL service is authorized in the directory service domain \"%2\" (Server IP Address %1)
0x42C	The DHCP/BINL service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1)	The DHCP/BINL service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1)
0x42D	Iashlpr could not contact the NPS server:%n%1, check if IAS service is started.	Iashlpr could not contact the NPS server:%n%1, check if IAS service is started.
0x42E	Iashlpr initialization failed: %1, so DHCP server cannot talk to NPS server. It could be that IAS service is not started.	Iashlpr initialization failed: %1, so DHCP server cannot talk to NPS server. It could be that IAS service is not started.
0x42F	Dynamic Bootp%0	Dynamic Bootp%0
0x430	Renew%0	Renew%0
0x431	Release%0	Release%0
0x432	Conflict%0	Conflict%0
0x433	Scope Full%0	Scope Full%0
0x434	Started%0	Started%0
0x435	Stopped%0	Stopped%0
0x436	Audit Log Paused%0	Audit Log Paused%0
0x437	dhcpsrv.log%0	dhcpsrv.log%0
0x438	BAD_ADDRESS%0	BAD_ADDRESS%0
0x439	This address is already in use%0	This address is already in use%0
0x43A	NACK%0	NACK%0
0x43B	Deleted%0	Deleted%0
0x43C	DNS record not deleted%0	DNS record not deleted%0
0x43D	Expired%0	Expired%0
0x43E	%%d leases expired and %%d leases deleted%0	%%d leases expired and %%d leases deleted%0
0x43F	Database Cleanup Begin%0	Database Cleanup Begin%0
0x440	%t%tMicrosoft DHCP Service Activity Log%n%n%nEvent ID Meaning%n00%tThe log was started.%n01%tThe log was stopped.%n02%tThe log was temporarily paused due to low disk space.%n10%tA new IP address was leased to a client.%n11%tA lease was renewed by a client.%n12%tA lease was released by a client.%n13%tAn IP address was found to be in use on the network.%n14%tA lease request could not be satisfied because the scope's address pool was exhausted.%n15%tA lease was denied.%n16%tA lease was deleted.%n17%tA lease was expired and DNS records for an expired leases have not been deleted.%n18%tA lease was expired and DNS records were deleted.%n20%tA BOOTP address was leased to a client.%n21%tA dynamic BOOTP address was leased to a client.%n22%tA BOOTP request could not be satisfied because the scope's address pool for BOOTP was exhausted.%n23%tA BOOTP IP address was deleted after checking to see it was not in use.%n24%tIP address cleanup operation has began.%n25%tIP address cleanup statistics.%n30%tDNS update request to the named DNS server.%n31%tDNS update failed.%n32%tDNS update successful.%n33%tPacket dropped due to NAP policy.%n34%tDNS update request failed.as the DNS update request queue limit exceeded.%n35%tDNS update request failed.%n36%tPacket dropped because the server is in failover standby role or the hash of the client ID does not match.%n50+%tCodes above 50 are used for Rogue Server Detection information.%n%nQResult: 0: NoQuarantine, 1:Quarantine, 2:Drop Packet, 3:Probation,6:No Quarantine Information ProbationTime:Year-Month-Day Hour:Minute:Second:MilliSecond.%n%nID,Date,Time,Description,IP Address,Host Name,MAC Address,User Name, TransactionID, QResult,Probationtime, CorrelationID,Dhcid,VendorClass(Hex),VendorClass(ASCII),UserClass(Hex),UserClass(ASCII),RelayAgentInformation,DnsRegError.	%t%tMicrosoft DHCP Service Activity Log%n%n%nEvent ID Meaning%n00%tThe log was started.%n01%tThe log was stopped.%n02%tThe log was temporarily paused due to low disk space.%n10%tA new IP address was leased to a client.%n11%tA lease was renewed by a client.%n12%tA lease was released by a client.%n13%tAn IP address was found to be in use on the network.%n14%tA lease request could not be satisfied because the scope's address pool was exhausted.%n15%tA lease was denied.%n16%tA lease was deleted.%n17%tA lease was expired and DNS records for an expired leases have not been deleted.%n18%tA lease was expired and DNS records were deleted.%n20%tA BOOTP address was leased to a client.%n21%tA dynamic BOOTP address was leased to a client.%n22%tA BOOTP request could not be satisfied because the scope's address pool for BOOTP was exhausted.%n23%tA BOOTP IP address was deleted after checking to see it was not in use.%n24%tIP address cleanup operation has began.%n25%tIP address cleanup statistics.%n30%tDNS update request to the named DNS server.%n31%tDNS update failed.%n32%tDNS update successful.%n33%tPacket dropped due to NAP policy.%n34%tDNS update request failed.as the DNS update request queue limit exceeded.%n35%tDNS update request failed.%n36%tPacket dropped because the server is in failover standby role or the hash of the client ID does not match.%n50+%tCodes above 50 are used for Rogue Server Detection information.%n%nQResult: 0: NoQuarantine, 1:Quarantine, 2:Drop Packet, 3:Probation,6:No Quarantine Information ProbationTime:Year-Month-Day Hour:Minute:Second:MilliSecond.%n%nID,Date,Time,Description,IP Address,Host Name,MAC Address,User Name, TransactionID, QResult,Probationtime, CorrelationID,Dhcid,VendorClass(Hex),VendorClass(ASCII),UserClass(Hex),UserClass(ASCII),RelayAgentInformation,DnsRegError.
0x441	BOOTP Range Full%0	BOOTP Range Full%0
0x442	BOOTP deleted%0	BOOTP deleted%0
0x443	DhcpSrvLog-Sun.log%0	DhcpSrvLog-Sun.log%0
0x444	DhcpSrvLog-Mon.log%0	DhcpSrvLog-Mon.log%0
0x445	DhcpSrvLog-Tue.log%0	DhcpSrvLog-Tue.log%0
0x446	DhcpSrvLog-Wed.log%0	DhcpSrvLog-Wed.log%0
0x447	DhcpSrvLog-Thu.log%0	DhcpSrvLog-Thu.log%0
0x448	DhcpSrvLog-Fri.log%0	DhcpSrvLog-Fri.log%0
0x449	DhcpSrvLog-Sat.log%0	DhcpSrvLog-Sat.log%0
0x44A	Unreachable Domain%0	Unreachable Domain%0
0x44B	Authorization succeeded%0	Authorization succeeded%0
0x44C	Server Upgraded%0	Server Upgraded%0
0x44D	Cached authorization%0	Cached authorization%0
0x44E	Authorization failed%0	Authorization failed%0
0x44F	Authorized(servicing)%0	Authorized(servicing)%0
0x450	Authorization failure, stopped servicing%0	Authorization failure, stopped servicing%0
0x451	Server found in our domain%0	Server found in our domain%0
0x452	Could not find domain%0	Could not find domain%0
0x453	Network failure%0	Network failure%0
0x454	No DC is DS Enabled%0	No DC is DS Enabled%0
0x455	Server found that belongs to DS domain%0	Server found that belongs to DS domain%0
0x456	Another server was found%0	Another server was found%0
0x457	Restarting rogue detection%0	Restarting rogue detection%0
0x458	No static IP address bound to DHCP server%0	No static IP address bound to DHCP server%0
0x459	Microsoft Windows 2000 Options%0	Microsoft Windows 2000 Options%0
0x45A	Microsoft vendor-specific options for Windows 2000 and above Clients%0	Microsoft vendor-specific options for Windows 2000 and above Clients%0
0x45B	Microsoft Windows 98 Options%0	Microsoft Windows 98 Options%0
0x45C	Microsoft vendor-specific options for Windows 98 Clients%0	Microsoft vendor-specific options for Windows 98 Clients%0
0x45D	Microsoft Options%0	Microsoft Options%0
0x45E	Microsoft vendor-specific options applicable to all Windows Clients%0	Microsoft vendor-specific options applicable to all Windows Clients%0
0x45F	Microsoft Disable Netbios Option %0	Microsoft Disable Netbios Option %0
0x460	Option for enabling or disabling Netbios for Microsoft Windows 2000 Clients%0	Option for enabling or disabling Netbios for Microsoft Windows 2000 Clients%0
0x461	Microsoft Release DHCP Lease On Shutdown Option%0	Microsoft Release DHCP Lease On Shutdown Option%0
0x462	Option for enabling or disabling Windows 2000 Clients to release DHCP lease on shutdown%0	Option for enabling or disabling Windows 2000 Clients to release DHCP lease on shutdown%0
0x463	Microsoft Default Router Metric Base%0	Microsoft Default Router Metric Base%0
0x464	Default Router Base Metrics for Microsoft Windows 2000 Clients%0	Default Router Base Metrics for Microsoft Windows 2000 Clients%0
0x465	Internal%0	Internal%0
0x466	DHCP Users%0	DHCP Users%0
0x467	Members who have view-only access to the DHCP service%0	Members who have view-only access to the DHCP service%0
0x468	DHCP Administrators%0	DHCP Administrators%0
0x469	Members who have administrative access to DHCP service%0	Members who have administrative access to DHCP service%0
0x46A	Default Routing and Remote Access Class%0	Default Routing and Remote Access Class%0
0x46B	User class for remote access clients%0	User class for remote access clients%0
0x46C	Default BOOTP Class%0	Default BOOTP Class%0
0x46D	User class for BOOTP Clients%0	User class for BOOTP Clients%0
0x46E	Classless Static Routes%0	Classless Static Routes%0
0x46F	Destination, mask and router IP addresses in priority order%0	Destination, mask and router IP addresses in priority order%0
0x470	DNS Update Request%0	DNS Update Request%0
0x471	DNS Update Failed%0	DNS Update Failed%0
0x472	DNS Update Successful%0	DNS Update Successful%0
0x473	Default Network Access Protection Class%0	Default Network Access Protection Class%0
0x474	Default special user class for Restricted Access clients%0	Default special user class for Restricted Access clients%0
0x475	Assign%0	Assign%0
0x476	The DHCP server is unable to reach the NPS server for determining the client's NAP access state %0.	The DHCP server is unable to reach the NPS server for determining the client's NAP access state %0.
0x477	Bootp%0	Bootp%0
0x478	This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.	This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.
0x479	Microsoft Windows Options%0	Microsoft Windows Options%0
0x47A	Microsoft vendor-specific options for Windows Clients%0	Microsoft vendor-specific options for Windows Clients%0
0x47B	Enabled%0	Enabled%0
0x47C	Disabled%0	Disabled%0
0x47D	EQ %0	EQ %0
0x47E	NEQ %0	NEQ %0
0x47F	AND%0	AND%0
0x480	OR%0	OR%0
0x481	Vendor Class %0	Vendor Class %0
0x482	User Class %0	User Class %0
0x483	MAC address %0	MAC address %0
0x484	Client Id %0	Client Id %0
0x485	Relay Agent Info %0	Relay Agent Info %0
0x486	Relay Agent Info - Circuit Id %0	Relay Agent Info - Circuit Id %0
0x487	Relay Agent Info - Remote Id %0	Relay Agent Info - Remote Id %0
0x488	Relay Agent Info - Subscriber Id %0	Relay Agent Info - Subscriber Id %0
0x489	, %0	, %0
0x48A	; %0	; %0
0x48B	*%0	*%0
0x48C	Fully Qualified Domain Name %0	Fully Qualified Domain Name %0
0x48D	Is Single Label%0	Is Single Label%0
0x48E	Is Not Single Label%0	Is Not Single Label%0
0x48F	Reserved	Reserved
0x498	DhcpV6SrvLog-Sun.log%0	DhcpV6SrvLog-Sun.log%0
0x499	DhcpV6SrvLog-Mon.log%0	DhcpV6SrvLog-Mon.log%0
0x49A	DhcpV6SrvLog-Tue.log%0	DhcpV6SrvLog-Tue.log%0
0x49B	DhcpV6SrvLog-Wed.log%0	DhcpV6SrvLog-Wed.log%0
0x49C	DhcpV6SrvLog-Thu.log%0	DhcpV6SrvLog-Thu.log%0
0x49D	DhcpV6SrvLog-Fri.log%0	DhcpV6SrvLog-Fri.log%0
0x49E	DhcpV6SrvLog-Sat.log%0	DhcpV6SrvLog-Sat.log%0
0x49F	SIP Server Domain Name List %0	SIP Server Domain Name List %0
0x4A0	Domain Name of SIP servers available to the client %0	Domain Name of SIP servers available to the client %0
0x4A1	SIP Servers IPv6 Address List %0	SIP Servers IPv6 Address List %0
0x4A2	IPv6 addresses of SIP servers available to the client %0	IPv6 addresses of SIP servers available to the client %0
0x4A3	DNS Recursive Name Server IPv6 Address List %0	DNS Recursive Name Server IPv6 Address List %0
0x4A4	IPv6 Addresses of DNS recursive name servers available to the client %0	IPv6 Addresses of DNS recursive name servers available to the client %0
0x4A5	Domain Search List %0	Domain Search List %0
0x4A6	Domain search list used by clients to resolve hostnames with DNS, by preference %0	Domain search list used by clients to resolve hostnames with DNS, by preference %0
0x4A7	NIS IPv6 Address List %0	NIS IPv6 Address List %0
0x4A8	IPv6 Addresses of NIS servers available to the client %0	IPv6 Addresses of NIS servers available to the client %0
0x4A9	NIS+ IPv6 Address List %0	NIS+ IPv6 Address List %0
0x4AA	IPv6 Addresses of NIS+ servers available to the client %0	IPv6 Addresses of NIS+ servers available to the client %0
0x4AB	NIS Domain List %0	NIS Domain List %0
0x4AC	Domain names of NIS servers available to the client %0	Domain names of NIS servers available to the client %0
0x4AD	NIS+ Domain Name List %0	NIS+ Domain Name List %0
0x4AE	Domain names of NIS+ servers available to the client %0	Domain names of NIS+ servers available to the client %0
0x4AF	SNTP Servers IPv6 Address List %0	SNTP Servers IPv6 Address List %0
0x4B0	IPv6 Addresses of SNTP servers available to the client %0	IPv6 Addresses of SNTP servers available to the client %0
0x4B1	Information Refresh Time %0	Information Refresh Time %0
0x4B2	This option specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6 Server %0	This option specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6 Server %0
0x4B3	%t%tMicrosoft DHCPv6 Service Activity Log%n%n%nEvent ID Meaning%n11000%tDHCPv6 Solicit.%n11001%tDHCPv6 Advertise.%n11002%tDHCPv6 Request.%n11003%tDHCPv6 Confirm.%n11004%tDHCPv6 Renew.%n11005%tDHCPv6 Rebind.%n11006%tDHCPv6 Decline.%n11007%tDHCPv6 Release.%n11008%tDHCPv6 Information Request.%n11009%tDHCPv6 Scope Full.%n11010%tDHCPv6 Started.%n11011%tDHCPv6 Stopped.%n11012%tDHCPv6 Audit log paused.%n11013%tDHCPv6 Log File.%n11014%tDHCPv6 Bad Address.%n11015%tDHCPv6 Address is already in use.%n11016%tDHCPv6 Client deleted.%n11017%tDHCPv6 DNS record not deleted.%n11018%tDHCPv6 Expired.%n11019%tDHCPv6 Leases Expired and Leases Deleted .%n11020%tDHCPv6 Database cleanup begin.%n11021%tDHCPv6 Database cleanup end.%n11022%tDNS IPv6 Update Request.%n11023%tDNS IPv6 Update Failed.%n11024%tDNS IPv6 Update Successful.%n11028%tDNS IPv6 update request failed as the DNS update request queue limit exceeded.%n11029%tDNS IPv6 update request failed.%n11030%tDHCPv6 stateless client records purged.%n11031%tDHCPv6 stateless client record is purged as the purge interval has expired for this client record.%n11032%tDHCPV6 Information Request from IPV6 Stateless Client.%n%nID,Date,Time,Description,IPv6 Address,Host Name,Error Code, Duid Length, Duid Bytes(Hex),User Name,Dhcid,Subnet Prefix.	%t%tMicrosoft DHCPv6 Service Activity Log%n%n%nEvent ID Meaning%n11000%tDHCPv6 Solicit.%n11001%tDHCPv6 Advertise.%n11002%tDHCPv6 Request.%n11003%tDHCPv6 Confirm.%n11004%tDHCPv6 Renew.%n11005%tDHCPv6 Rebind.%n11006%tDHCPv6 Decline.%n11007%tDHCPv6 Release.%n11008%tDHCPv6 Information Request.%n11009%tDHCPv6 Scope Full.%n11010%tDHCPv6 Started.%n11011%tDHCPv6 Stopped.%n11012%tDHCPv6 Audit log paused.%n11013%tDHCPv6 Log File.%n11014%tDHCPv6 Bad Address.%n11015%tDHCPv6 Address is already in use.%n11016%tDHCPv6 Client deleted.%n11017%tDHCPv6 DNS record not deleted.%n11018%tDHCPv6 Expired.%n11019%tDHCPv6 Leases Expired and Leases Deleted .%n11020%tDHCPv6 Database cleanup begin.%n11021%tDHCPv6 Database cleanup end.%n11022%tDNS IPv6 Update Request.%n11023%tDNS IPv6 Update Failed.%n11024%tDNS IPv6 Update Successful.%n11028%tDNS IPv6 update request failed as the DNS update request queue limit exceeded.%n11029%tDNS IPv6 update request failed.%n11030%tDHCPv6 stateless client records purged.%n11031%tDHCPv6 stateless client record is purged as the purge interval has expired for this client record.%n11032%tDHCPV6 Information Request from IPV6 Stateless Client.%n%nID,Date,Time,Description,IPv6 Address,Host Name,Error Code, Duid Length, Duid Bytes(Hex),User Name,Dhcid,Subnet Prefix.
0x4B4	Packet dropped%0	Packet dropped%0
0x4B5	DHCP Standard Options%0	DHCP Standard Options%0
0x4B6	Default User Class%0	Default User Class%0
0x4B7	%0	%0
0x4B8	UTC offset in seconds%0	UTC offset in seconds%0
0x4B9	Router%0	Router%0
0x4BA	Array of router addresses ordered by preference%0	Array of router addresses ordered by preference%0
0x4BB	Time Server%0	Time Server%0
0x4BC	Array of time server addresses, by preference%0	Array of time server addresses, by preference%0
0x4BD	Name Servers%0	Name Servers%0
0x4BE	Array of name servers [IEN 116], by preference%0	Array of name servers [IEN 116], by preference%0
0x4BF	DNS Servers%0	DNS Servers%0
0x4C0	Array of DNS servers, by preference%0	Array of DNS servers, by preference%0
0x4C1	Log Servers%0	Log Servers%0
0x4C2	Array of MIT_LCS UDP log servers on subnet%0	Array of MIT_LCS UDP log servers on subnet%0
0x4C3	Cookie Servers%0	Cookie Servers%0
0x4C4	Array of cookie servers, RFC 865%0	Array of cookie servers, RFC 865%0
0x4C5	LPR Servers%0	LPR Servers%0
0x4C6	Array of RFC 1179 servers, by preference%0	Array of RFC 1179 servers, by preference%0
0x4C7	Impress Servers%0	Impress Servers%0
0x4C8	Array of Imagen Impress Servers%0	Array of Imagen Impress Servers%0
0x4C9	Resource Location Servers%0	Resource Location Servers%0
0x4CA	Array of RFC 887 ResLoc Servers on subnet, by preference%0	Array of RFC 887 ResLoc Servers on subnet, by preference%0
0x4CB	Host Name%0	Host Name%0
0x4CC	Host name for client, RFC 1035 character set%0	Host name for client, RFC 1035 character set%0
0x4CD	Boot File Size%0	Boot File Size%0
0x4CE	Size of boot image file in 512-octet blocks%0	Size of boot image file in 512-octet blocks%0
0x4CF	Merit Dump File%0	Merit Dump File%0
0x4D0	Path name for crash dump file%0	Path name for crash dump file%0
0x4D1	DNS Domain Name%0	DNS Domain Name%0
0x4D2	DNS Domain name for client resolutions%0	DNS Domain name for client resolutions%0
0x4D3	Swap Server%0	Swap Server%0
0x4D4	Address of client's swap server%0	Address of client's swap server%0
0x4D5	Root Path%0	Root Path%0
0x4D6	Path name for client's root disk, char set NVT ASCII%0	Path name for client's root disk, char set NVT ASCII%0
0x4D7	Extensions Path%0	Extensions Path%0
0x4D8	tftp file for option extensions%0	tftp file for option extensions%0
0x4D9	IP Layer Forwarding%0	IP Layer Forwarding%0
0x4DA	Disable/enable IP packet forwarding on this client%0	Disable/enable IP packet forwarding on this client%0
0x4DB	Nonlocal Source Routing%0	Nonlocal Source Routing%0
0x4DC	Disable/enable nonlocal datagrams%0	Disable/enable nonlocal datagrams%0
0x4DD	Policy Filter Masks%0	Policy Filter Masks%0
0x4DE	Destination/mask IP address pairs to filter source routes%0	Destination/mask IP address pairs to filter source routes%0
0x4DF	Max DG Reassembly Size%0	Max DG Reassembly Size%0
0x4E0	Maximum size datagram for reassembly by client; max 576%0	Maximum size datagram for reassembly by client; max 576%0
0x4E1	Default IP Time-to-live%0	Default IP Time-to-live%0
0x4E2	Default TTL for client's use on outgoing DGs%0	Default TTL for client's use on outgoing DGs%0
0x4E3	Path MTU Aging Timeout%0	Path MTU Aging Timeout%0
0x4E4	Timeout in seconds for aging Path MTU values; RFC 1191%0	Timeout in seconds for aging Path MTU values; RFC 1191%0
0x4E5	Path MTU Plateau Table%0	Path MTU Plateau Table%0
0x4E6	MTU discovery sizes, sorted by size, all = 68%0	MTU discovery sizes, sorted by size, all = 68%0
0x4E7	MTU Option%0	MTU Option%0
0x4E8	MTU discovery size, = 68%0	MTU discovery size, = 68%0
0x4E9	All subnets are local%0	All subnets are local%0
0x4EA	The client assumes that all subnets are local%0	The client assumes that all subnets are local%0
0x4EB	Broadcast Address%0	Broadcast Address%0
0x4EC	Broadcast address%0	Broadcast address%0
0x4ED	Perform Mask Discovery%0	Perform Mask Discovery%0
0x4EE	The client should use ICMP for subnet mask discovery.%0	The client should use ICMP for subnet mask discovery.%0
0x4EF	Mask Supplier Option%0	Mask Supplier Option%0
0x4F0	The client should respond to subnet mask requests via ICMP.%0	The client should respond to subnet mask requests via ICMP.%0
0x4F1	Perform Router Discovery%0	Perform Router Discovery%0
0x4F2	The client should solicit routers using RFC 1256.%0	The client should solicit routers using RFC 1256.%0
0x4F3	Router Solicitation Address%0	Router Solicitation Address%0
0x4F4	Address to use for router solicitation%0	Address to use for router solicitation%0
0x4F5	Static Route Option%0	Static Route Option%0
0x4F6	Destination/router address pairs, in priority order%0	Destination/router address pairs, in priority order%0
0x4F7	Trailer Encapsulation%0	Trailer Encapsulation%0
0x4F8	The client should negotiate use of trailers (RFC 983).%0	The client should negotiate use of trailers (RFC 983).%0
0x4F9	ARP Cache Timeout%0	ARP Cache Timeout%0
0x4FA	Timeout in seconds for ARP cache entries%0	Timeout in seconds for ARP cache entries%0
0x4FB	Ethernet Encapsulation%0	Ethernet Encapsulation%0
0x4FC	0=client should use ENet V2; 1= IEEE 802.3%0	0=client should use ENet V2; 1= IEEE 802.3%0
0x4FD	TCP Default Time-to-live%0	TCP Default Time-to-live%0
0x4FE	TTL that client uses when sending TCP segments%0	TTL that client uses when sending TCP segments%0
0x4FF	Keepalive Interval%0	Keepalive Interval%0
0x500	Keepalive timeout in seconds%0	Keepalive timeout in seconds%0
0x501	Keepalive Garbage%0	Keepalive Garbage%0
0x502	Send garbage octet%0	Send garbage octet%0
0x503	NIS Domain Name%0	NIS Domain Name%0
0x504	Name of Network Information Service domain%0	Name of Network Information Service domain%0
0x505	NIS Servers%0	NIS Servers%0
0x506	Addresses of NIS servers on client's subnet%0	Addresses of NIS servers on client's subnet%0
0x507	NTP Servers%0	NTP Servers%0
0x508	Addresses of Network Time Protocol servers%0	Addresses of Network Time Protocol servers%0
0x509	Vendor Specific Info%0	Vendor Specific Info%0
0x50A	Embedded vendor-specific options%0	Embedded vendor-specific options%0
0x50B	WINS/NBNS Servers%0	WINS/NBNS Servers%0
0x50C	NBNS Address(es) in priority order%0	NBNS Address(es) in priority order%0
0x50D	NetBIOS over TCP/IP NBDD%0	NetBIOS over TCP/IP NBDD%0
0x50E	NetBIOS over TCP/IP NBDD address(es) in priority order%0	NetBIOS over TCP/IP NBDD address(es) in priority order%0
0x50F	WINS/NBT Node Type%0	WINS/NBT Node Type%0
0x510	0x1 = B-node, 0x2 = P-node, 0x4 = M-node, 0x8 = H-node%0	0x1 = B-node, 0x2 = P-node, 0x4 = M-node, 0x8 = H-node%0
0x511	NetBIOS Scope ID%0	NetBIOS Scope ID%0
0x512	NetBIOS over TCP/IP Scope ID%0	NetBIOS over TCP/IP Scope ID%0
0x513	X Window System Font%0	X Window System Font%0
0x514	Array of X Windows font servers%0	Array of X Windows font servers%0
0x515	X Window System Display%0	X Window System Display%0
0x516	Array of X Windows Display Mgr servers%0	Array of X Windows Display Mgr servers%0
0x517	Lease%0	Lease%0
0x518	Client IP address lease time in seconds%0	Client IP address lease time in seconds%0
0x519	Renewal (T1) Time Value%0	Renewal (T1) Time Value%0
0x51A	Time between addr assignment to RENEWING state%0	Time between addr assignment to RENEWING state%0
0x51B	Rebinding (T2) Time Value%0	Rebinding (T2) Time Value%0
0x51C	Time from addr assignment to REBINDING state%0	Time from addr assignment to REBINDING state%0
0x51D	NIS+ Domain Name%0	NIS+ Domain Name%0
0x51E	The name of the client's NIS+ domain.%0	The name of the client's NIS+ domain.%0
0x51F	NIS+ Servers%0	NIS+ Servers%0
0x520	A list of IP addresses indicating NIS+ servers%0	A list of IP addresses indicating NIS+ servers%0
0x521	Boot Server Host Name%0	Boot Server Host Name%0
0x522	TFTP boot server host name%0	TFTP boot server host name%0
0x523	Bootfile Name%0	Bootfile Name%0
0x525	Mobile IP Home Agents%0	Mobile IP Home Agents%0
0x526	Mobile IP home agents in priority order%0	Mobile IP home agents in priority order%0
0x527	Simple Mail Transport Protocol (SMTP) Servers%0	Simple Mail Transport Protocol (SMTP) Servers%0
0x528	List of SMTP servers available to the client%0	List of SMTP servers available to the client%0
0x529	Post Office Protocol (POP3) Servers%0	Post Office Protocol (POP3) Servers%0
0x52A	List of POP3 servers available to the client%0	List of POP3 servers available to the client%0
0x52B	Network News Transport Protocol (NNTP) Servers%0	Network News Transport Protocol (NNTP) Servers%0
0x52C	List of NNTP servers available to the client%0	List of NNTP servers available to the client%0
0x52D	World Wide Web (WWW) Servers%0	World Wide Web (WWW) Servers%0
0x52E	List of WWW servers available to the client%0	List of WWW servers available to the client%0
0x52F	Finger Servers%0	Finger Servers%0
0x530	List of Finger servers available to the client%0	List of Finger servers available to the client%0
0x531	Internet Relay Chat (IRC) Servers%0	Internet Relay Chat (IRC) Servers%0
0x532	List of IRC servers available to the client%0	List of IRC servers available to the client%0
0x533	StreetTalk Servers%0	StreetTalk Servers%0
0x534	List of StreetTalk servers available to the client%0	List of StreetTalk servers available to the client%0
0x535	Subnet Mask%0	Subnet Mask%0
0x536	StreetTalk Directory Assistance (STDA) Servers%0	StreetTalk Directory Assistance (STDA) Servers%0
0x537	List of STDA servers available to the client%0	List of STDA servers available to the client%0
0x538	Subnet mask in network byte order%0	Subnet mask in network byte order%0
0x539	Time Offset%0	Time Offset%0
0x53A	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.	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.
0x53B	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.	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.
0x53C	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.	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.
0x53D	There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2.	There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2.
0x53E	IP address range of scope %1 is out of IP addresses.	IP address range of scope %1 is out of IP addresses.
0x53F	Ip address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available .	Ip address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available .
0x540	The DNS IP Address %1 is not a valid DNS Server Address.	The DNS IP Address %1 is not a valid DNS Server Address.
0x541	DNS update request failed as the DNS update requests queue limit exceeded%0	DNS update request failed as the DNS update requests queue limit exceeded%0
0x542	DNS update request failed%0	DNS update request failed%0
0x543	DNS IPv6 update request failed as the DNS update requests queue limit exceeded%0	DNS IPv6 update request failed as the DNS update requests queue limit exceeded%0
0x544	DNS IPv6 update request failed%0	DNS IPv6 update request failed%0
0x545	Reserved%0	Reserved%0
0x546	Illegal IP address (not part of any address pool)%0	Illegal IP address (not part of any address pool)%0
0x547	Fatal conflict exists: address in use by other client%0	Fatal conflict exists: address in use by other client%0
0x548	Missing binding information%0	Missing binding information%0
0x549	Connection rejected, time mismatch too great%0	Connection rejected, time mismatch too great%0
0x54A	Connection rejected, invalid MCLT%0	Connection rejected, invalid MCLT%0
0x54B	Connection rejected, unknown reason%0	Connection rejected, unknown reason%0
0x54C	Connection rejected, duplicate connection%0	Connection rejected, duplicate connection%0
0x54D	Connection rejected, invalid failover partner%0	Connection rejected, invalid failover partner%0
0x54E	TLS not supported%0	TLS not supported%0
0x54F	TLS supported but not configured%0	TLS supported but not configured%0
0x550	TLS required but not supported by partner%0	TLS required but not supported by partner%0
0x551	Message digest not supported%0	Message digest not supported%0
0x552	Message digest not configured%0	Message digest not configured%0
0x553	Protocol version mismatch%0	Protocol version mismatch%0
0x554	Outdated binding information%0	Outdated binding information%0
0x555	Less critical binding information%0	Less critical binding information%0
0x556	No traffic within sufficient time%0	No traffic within sufficient time%0
0x557	Hash bucket assignment conflict%0	Hash bucket assignment conflict%0
0x558	IP not reserved on this server%0	IP not reserved on this server%0
0x559	Message digest failed to compare%0	Message digest failed to compare%0
0x55A	Missing message digest%0	Missing message digest%0
0x55B	Address is allocated to this server%0	Address is allocated to this server%0
0x55C	Address is allocated to the partner server%0	Address is allocated to the partner server%0
0x55D	Reject Reason Unknown%0	Reject Reason Unknown%0
0x55E	Packet dropped because of Client ID hash mismatch or standby server.%0	Packet dropped because of Client ID hash mismatch or standby server.%0
0x560	IP address range of scope %1 is %2 percent full with only %3 IP addresses available.	IP address range of scope %1 is %2 percent full with only %3 IP addresses available.
0x561	SuperScope, %1, is %2 percent full with only %3 IP addresses remaining. This superscope has the following scopes %4	SuperScope, %1, is %2 percent full with only %3 IP addresses remaining. This superscope has the following scopes %4
0x00002710	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.	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.
0x00002711	Renew, rebind or confirm received for IPv6 addresses %1 for which there are no active lease available	Renew, rebind or confirm received for IPv6 addresses %1 for which there are no active lease available
0x00002712	DHCPv6 service received the unknown option %1, with a length of %2. The raw option data is given below.	DHCPv6 service received the unknown option %1, with a length of %2. The raw option data is given below.
0x00002713	There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1.	There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1.
0x00002714	The DHCPv6 client, %2, declined the address %1.	The DHCPv6 client, %2, declined the address %1.
0x00002715	DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining.	DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining.
0x00002716	A DHCPV6 client %1 has been deleted from DHCPV6 database.	A DHCPV6 client %1 has been deleted from DHCPV6 database.
0x00002717	A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process.	A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process.
0x00002718	An invalid DHCPV6 message has been dropped.	An invalid DHCPV6 message has been dropped.
0x00002719	A DHCPV6 message that was not meant for this server has been dropped.	A DHCPV6 message that was not meant for this server has been dropped.
0x0000271A	DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server.	DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server.
0x0000271B	DHCPV6 audit log file cannot be appended, Error Code returned %1.	DHCPV6 audit log file cannot be appended, Error Code returned %1.
0x0000271C	A DHCPV6 message has been dropped because the server is not authorized to process the message.	A DHCPV6 message has been dropped because the server is not authorized to process the message.
0x0000271D	The DHCPv6 service failed to initialize the audit log. The following error occurred: %n%1	The DHCPv6 service failed to initialize the audit log. The following error occurred: %n%1
0x0000271E	DHCPv6 audit log file could not be backed up. Error code %1	DHCPv6 audit log file could not be backed up. Error code %1
0x0000271F	AThe DHCPv6 service was unable to access path specified for the audit log.	AThe DHCPv6 service was unable to access path specified for the audit log.
0x00002720	The DHCPv6 service failed to initialize Winsock startup. The following error occurred %1.	The DHCPv6 service failed to initialize Winsock startup. The following error occurred %1.
0x00002721	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.	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.
0x00002722	The DHCPv6 Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCPv6 service.	The DHCPv6 Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCPv6 service.
0x00002723	The DHCPv6 service failed to initialize its configuration parameters. The following error occurred: %n%1.	The DHCPv6 service failed to initialize its configuration parameters. The following error occurred: %n%1.
0x00002724	This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.	This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.
0x00002725	DHCPv6 service failed to initialize the database. The following error occurred: %n%1.	DHCPv6 service failed to initialize the database. The following error occurred: %n%1.
0x00002726	The DHCPv6 service has initialized and is ready to serve.	The DHCPv6 service has initialized and is ready to serve.
0x00002727	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.	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.
0x00002728	ERROR_LAST_DHCPV6_SERVER_ERROR	ERROR_LAST_DHCPV6_SERVER_ERROR
0x00002729	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.	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.
0x00002AF8	DHCPV6 Solicit%0	DHCPV6 Solicit%0
0x00002AF9	DHCPV6 Advertise%0	DHCPV6 Advertise%0
0x00002AFA	DHCPV6 Request%0	DHCPV6 Request%0
0x00002AFB	DHCPV6 Confirm%0	DHCPV6 Confirm%0
0x00002AFC	DHCPV6 Renew%0	DHCPV6 Renew%0
0x00002AFD	DHCPV6 Rebind%0	DHCPV6 Rebind%0
0x00002AFE	DHCPV6 Decline%0	DHCPV6 Decline%0
0x00002AFF	DHCPV6 Release%0	DHCPV6 Release%0
0x00002B00	DHCPV6 Information Request%0	DHCPV6 Information Request%0
0x00002B01	DHCPV6 Scope Full%0	DHCPV6 Scope Full%0
0x00002B02	DHCPV6 Started%0	DHCPV6 Started%0
0x00002B03	DHCPV6 Stopped%0	DHCPV6 Stopped%0
0x00002B04	DHCPV6 Audit Log Paused%0	DHCPV6 Audit Log Paused%0
0x00002B05	DHCPV6 dhcpsrv.log%0	DHCPV6 dhcpsrv.log%0
0x00002B06	DHCPV6 Bad Address%0	DHCPV6 Bad Address%0
0x00002B07	DHCPV6 address is already in use%0	DHCPV6 address is already in use%0
0x00002B08	DHCPV6 client Deleted%0	DHCPV6 client Deleted%0
0x00002B09	DHCPV6 DNS record not deleted%0	DHCPV6 DNS record not deleted%0
0x00002B0A	DHCPV6 Expired%0	DHCPV6 Expired%0
0x00002B0B	DHCPV6 %%I64d leases expired and %%I64d leases deleted%0	DHCPV6 %%I64d leases expired and %%I64d leases deleted%0
0x00002B0C	DHCPV6 Database Cleanup Begin%0	DHCPV6 Database Cleanup Begin%0
0x00002B0D	DHCPV6 Database Cleanup End%0	DHCPV6 Database Cleanup End%0
0x00002B0E	DNS IPv6 Update Request%0	DNS IPv6 Update Request%0
0x00002B0F	DNS IPv6 Update Failed%0	DNS IPv6 Update Failed%0
0x00002B10	DNS IPv6 Update Successful%0	DNS IPv6 Update Successful%0
0x00002B11	%%I64d DHCPV6 Stateless client records purged%0	%%I64d DHCPV6 Stateless client records purged%0
0x00002B12	DHCPv6 stateless client record is purged as the purge interval has expired for this client record%0	DHCPv6 stateless client record is purged as the purge interval has expired for this client record%0
0x00002B13	DHCPV6 Information Request from IPV6 Stateless Client%0	DHCPV6 Information Request from IPV6 Stateless Client%0
0x00002B15	The DHCPV6 service is not authorized in the directory service domain \"%2\" (Server IP Address %1)	The DHCPV6 service is not authorized in the directory service domain \"%2\" (Server IP Address %1)
0x00002B16	The DHCPV6 service is authorized in the directory service domain \"%2\" (Server IP Address %1)	The DHCPV6 service is authorized in the directory service domain \"%2\" (Server IP Address %1)
0x00002B17	The DHCPV6 service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1)	The DHCPV6 service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1)
0x00004E20	The DHCP server initialization parameters are incorrect.	The DHCP server initialization parameters are incorrect.
0x00004E21	The DHCP server was unable to open the DHCP client database.	The DHCP server was unable to open the DHCP client database.
0x00004E22	The DHCP server was unable to start as an RPC server.	The DHCP server was unable to start as an RPC server.
0x00004E23	The DHCP server was unable to establish a socket connection.	The DHCP server was unable to establish a socket connection.
0x00004E24	The specified subnet already exists.	The specified subnet already exists.
0x00004E25	The specified subnet does not exist.	The specified subnet does not exist.
0x00004E26	The primary host information for the specified subnet was not found.	The primary host information for the specified subnet was not found.
0x00004E27	The specified DHCP element cannot be removed because it has been used.	The specified DHCP element cannot be removed because it has been used.
0x00004E29	The specified option already exists.	The specified option already exists.
0x00004E2A	The specified option does not exist.	The specified option does not exist.
0x00004E2B	The specified address is not available.	The specified address is not available.
0x00004E2C	The specified IP address range is full.	The specified IP address range is full.
0x00004E2D	An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.	An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
0x00004E2E	The specified client already exists in the database.	The specified client already exists in the database.
0x00004E2F	The DHCP server received a message that is not valid.	The DHCP server received a message that is not valid.
0x00004E30	The DHCP server received a message from a client that is not valid.	The DHCP server received a message from a client that is not valid.
0x00004E31	The DHCP server service is paused.	The DHCP server service is paused.
0x00004E32	The specified DHCP client is not a reserved client.	The specified DHCP client is not a reserved client.
0x00004E33	The specified DHCP client is a reserved client.	The specified DHCP client is a reserved client.
0x00004E34	The specified IP address range is too small.	The specified IP address range is too small.
0x00004E35	The specified IP address range already exists.	The specified IP address range already exists.
0x00004E36	The specified IP address or hardware address is being used by another client.	The specified IP address or hardware address is being used by another client.
0x00004E37	The specified range either overlaps an existing range or is not valid.	The specified range either overlaps an existing range or is not valid.
0x00004E38	The specified range is an extension of an existing range.	The specified range is an extension of an existing range.
0x00004E39	The range extension specified is too small. The range must be extended by multiples of 32 addresses.	The range extension specified is too small. The range must be extended by multiples of 32 addresses.
0x00004E3A	The range was extended less than the specified backward extension. Extend the range by multiples of 32 addresses.	The range was extended less than the specified backward extension. Extend the range by multiples of 32 addresses.
0x00004E3B	DHCP database needs to be upgraded to a newer format. Look at the DHCP server event log for more information.	DHCP database needs to be upgraded to a newer format. Look at the DHCP server event log for more information.
0x00004E3C	The format of the bootstrap protocol file table is incorrect. The correct format is: ,, ,, etc...	The format of the bootstrap protocol file table is incorrect. The correct format is: ,, ,, etc...
0x00004E3D	ERROR_SERVER_UNKNOWN_BOOT_FILE_NAME	ERROR_SERVER_UNKNOWN_BOOT_FILE_NAME
0x00004E3E	The specified superscope name is too long.	The specified superscope name is too long.
0x00004E40	This IP address is already in use.	This IP address is already in use.
0x00004E41	The DHCP audit-log file path is too long.	The DHCP audit-log file path is too long.
0x00004E42	The DHCP service received a request for a valid IP address that is not administered by this server.	The DHCP service received a request for a valid IP address that is not administered by this server.
0x00004E43	The DHCP Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCP service.	The DHCP Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCP service.
0x00004E44	The DHCP database needs to be upgraded to the current Jet format. Look at the DHCP service event log for more information.	The DHCP database needs to be upgraded to the current Jet format. Look at the DHCP service event log for more information.
0x00004E45	The DHCP Server is not servicing any clients on the network because it could not determine if it is authorized to run. This might be due to network problems or insufficient resources.	The DHCP Server is not servicing any clients on the network because it could not determine if it is authorized to run. This might be due to network problems or insufficient resources.
0x00004E46	The DHCP service is shutting down because another DHCP server with the IP address %1 is active on the network.	The DHCP service is shutting down because another DHCP server with the IP address %1 is active on the network.
0x00004E47	The DHCP service is not servicing any clients on the network because it has determined that it is not authorized to run.	The DHCP service is not servicing any clients on the network because it has determined that it is not authorized to run.
0x00004E48	The DHCP service is unable to contact the directory service for domain %1. The DHCP service will continue to attempt to contact the directory service. During this time, no clients on the network will be serviced.	The DHCP service is unable to contact the directory service for domain %1. The DHCP service will continue to attempt to contact the directory service. During this time, no clients on the network will be serviced.
0x00004E49	The DHCP service is not servicing any clients on the network because its authorization information conflicts with another DHCP server whose IP address is %1 and is active on domain %2.	The DHCP service is not servicing any clients on the network because its authorization information conflicts with another DHCP server whose IP address is %1 and is active on domain %2.
0x00004E4A	The DHCP service is ignoring a request from another DHCP service because it is on a different directory service enterprise (Directory Service Enterprise root = %1)	The DHCP service is ignoring a request from another DHCP service because it is on a different directory service enterprise (Directory Service Enterprise root = %1)
0x00004E4B	The DHCP service has detected a directory service environment on the network. If there is directory service on the network, DHCP service can only run on a server which is part of the directory service. Since this server belongs to a workgroup, the DHCP service is terminating.	The DHCP service has detected a directory service environment on the network. If there is directory service on the network, DHCP service can only run on a server which is part of the directory service. Since this server belongs to a workgroup, the DHCP service is terminating.
0x00004E4C	The class name being used is unknown or incorrect.	The class name being used is unknown or incorrect.
0x00004E4D	The class name is already in use or the class information is already in use.	The class name is already in use or the class information is already in use.
0x00004E4E	The specified scope name is too long. The name is limited to a maximum of 256 characters.	The specified scope name is too long. The name is limited to a maximum of 256 characters.
0x00004E4F	There is already a default scope configured on the server.	There is already a default scope configured on the server.
0x00004E50	The Dynamic BOOTP attribute cannot be turned on or off.	The Dynamic BOOTP attribute cannot be turned on or off.
0x00004E51	Conversion of a scope to a DHCP Only scope or to a BOOTP Only scope is not allowed when DHCP and BOOTP clients both exist in the scope. Manually delete either the DHCP or the BOOTP clients from the scope, as appropriate for the type of scope being created.	Conversion of a scope to a DHCP Only scope or to a BOOTP Only scope is not allowed when DHCP and BOOTP clients both exist in the scope. Manually delete either the DHCP or the BOOTP clients from the scope, as appropriate for the type of scope being created.
0x00004E52	The network has changed. Retry this operation after checking for the network changes. Network changes may be caused by interfaces that are new or no longer valid, or by IP addresses that are new or no longer valid.	The network has changed. Retry this operation after checking for the network changes. Network changes may be caused by interfaces that are new or no longer valid, or by IP addresses that are new or no longer valid.
0x00004E53	The bindings to internal IP addresses cannot be modified.	The bindings to internal IP addresses cannot be modified.
0x00004E54	The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the subnet address and mask of an existing scope.	The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the subnet address and mask of an existing scope.
0x00004E55	The multicast scope parameters are incorrect. Either the scope already exists or its properties are inconsistent with the properties of another existing scope.	The multicast scope parameters are incorrect. Either the scope already exists or its properties are inconsistent with the properties of another existing scope.
0x00004E56	The multicast scope range must have atleast 256 IP addresses.	The multicast scope range must have atleast 256 IP addresses.
0x00004E57	The exemption parameters are incorrect. The exemption already exists.	The exemption parameters are incorrect. The exemption already exists.
0x00004E58	The exemption parameters are incorrect. The specified exemption does not exist.	The exemption parameters are incorrect. The specified exemption does not exist.
0x00004E59	Incorrect Parameter. Acceptable values are between 600 and 4294967295.	Incorrect Parameter. Acceptable values are between 600 and 4294967295.
0x00004E5A	%1 %3	%1 %3
0x00004E64	Scavenger started.	Scavenger started.
0x00004E65	Scavenger ended.	Scavenger ended.
0x00004E66	The DHCP service could not contact Active Directory.	The DHCP service could not contact Active Directory.
0x00004E67	The DHCP service root could not be found in the Active Directory.	The DHCP service root could not be found in the Active Directory.
0x00004E68	An unexpected error occurred while accessing the Active Directory.	An unexpected error occurred while accessing the Active Directory.
0x00004E69	There were too many errors to proceed.	There were too many errors to proceed.
0x00004E6A	A DHCP service could not be found.	A DHCP service could not be found.
0x00004E6B	The specified options are already present in the directory service.	The specified options are already present in the directory service.
0x00004E6C	The specified options are not present in the directory service.	The specified options are not present in the directory service.
0x00004E6D	The specified classes already exist in the directory service.	The specified classes already exist in the directory service.
0x00004E6E	The specified classes do not exist in the directory service.	The specified classes do not exist in the directory service.
0x00004E6F	The specified servers are already present in the directory service.	The specified servers are already present in the directory service.
0x00004E70	The specified servers are not present in the directory service.	The specified servers are not present in the directory service.
0x00004E71	The specified server address does not belong to the identified server name.	The specified server address does not belong to the identified server name.
0x00004E72	The specified subnets already exist in the directory service.	The specified subnets already exist in the directory service.
0x00004E73	The specified subnet belongs to a different superscope.	The specified subnet belongs to a different superscope.
0x00004E74	The specified subnet is not present in the directory service.	The specified subnet is not present in the directory service.
0x00004E75	The specified reservation is not present in the directory service.	The specified reservation is not present in the directory service.
0x00004E76	The reservation specified conflicts with an existing reservation in the directory service.	The reservation specified conflicts with an existing reservation in the directory service.
0x00004E77	The specified IP range conflicts with some existing IP range in the directory service.	The specified IP range conflicts with some existing IP range in the directory service.
0x00004E78	The specified IP range is not present in the directory service.	The specified IP range is not present in the directory service.
0x00004E79	This class cannot be deleted.	This class cannot be deleted.
0x00004E7A	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.	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.
0x00004E7B	The given subnet prefix is invalid. It represents either a non-unicast or link local address range.	The given subnet prefix is invalid. It represents either a non-unicast or link local address range.
0x00004E7C	The given delay value is invalid. The valid value is from 0 to 1000.	The given delay value is invalid. The valid value is from 0 to 1000.
0x00004E7D	Address or Address pattern is already contained in one of the list.	Address or Address pattern is already contained in one of the list.
0x00004E7E	Address to be added to Deny list or to be deleted from allow list, has an associated reservation.	Address to be added to Deny list or to be deleted from allow list, has an associated reservation.
0x00004E7F	Address or Address pattern is not contained in either list.	Address or Address pattern is not contained in either list.
0x00004E82	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.	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.
0x00004E85	This Hardware Type is already exempt.	This Hardware Type is already exempt.
0x00004E86	You are trying to delete an undefined Hardware Type. To define/add a Hardware Type, use 'add filterexemption'.	You are trying to delete an undefined Hardware Type. To define/add a Hardware Type, use 'add filterexemption'.
0x00004E87	Conflict in types for the same option on Host and Added DHCP Servers.	Conflict in types for the same option on Host and Added DHCP Servers.
0x00004E88	The parent expression specified does not exist.	The parent expression specified does not exist.
0x00004E89	The DHCP server policy already exists	The DHCP server policy already exists
0x00004E8A	The DHCP server policy range specified already exists in the given scope.	The DHCP server policy range specified already exists in the given scope.
0x00004E8B	The DHCP server policy range specified is invalid or does not match the given subnet.	The DHCP server policy range specified is invalid or does not match the given subnet.
0x00004E8C	DHCP server policy ranges can only be added to scope level policies.	DHCP server policy ranges can only be added to scope level policies.
0x00004E8D	The DHCP server policy contains an invalid expression.	The DHCP server policy contains an invalid expression.
0x00004E8E	The processing order specified for the DHCP server policy is invalid.	The processing order specified for the DHCP server policy is invalid.
0x00004E8F	The DHCP server policy was not found.	The DHCP server policy was not found.
0x00004E90	There is an IP address range configured for a policy in this scope. This operation on the scope IP address range cannot be performed till the policy IP address range is suitably modified. Please change the IP address range of the policy before performing this operation.	There is an IP address range configured for a policy in this scope. This operation on the scope IP address range cannot be performed till the policy IP address range is suitably modified. Please change the IP address range of the policy before performing this operation.
0x00004E91	The DHCP scope is already in a failover relationship.	The DHCP scope is already in a failover relationship.
0x00004E92	The DHCP failover relationship already exists.	The DHCP failover relationship already exists.
0x00004E93	The DHCP failover relationship does not exist.	The DHCP failover relationship does not exist.
0x00004E94	The DHCP scope is not part of failover relationship	The DHCP scope is not part of failover relationship
0x00004E95	The DHCP failover relationship is a secondary.	The DHCP failover relationship is a secondary.
0x00004E96	The DHCP failover is not supported	The DHCP failover is not supported
0x00004E97	The DHCP servers in the failover relationship has time out of synchronization.	The DHCP servers in the failover relationship has time out of synchronization.
0x00004E98	The DHCP failover relationship state is not NORMAL.	The DHCP failover relationship state is not NORMAL.
0x00004E99	The user does not have administrative permissions for the DHCP server	The user does not have administrative permissions for the DHCP server
0x00004E9A	The specified DHCP server is not reachable. Please provide a DHCP server that is reachable.	The specified DHCP server is not reachable. Please provide a DHCP server that is reachable.
0x00004E9B	The DHCP Server Service is not running on the specified server. Please ensure that the DHCP Server service is running on the specified computer	The DHCP Server Service is not running on the specified server. Please ensure that the DHCP Server service is running on the specified computer
0x00004E9C	Unable to resolve DNS name	Unable to resolve DNS name
0x00004E9D	The specified DHCP failover relationship name is too long. The name is limited to a maximum of 126 characters	The specified DHCP failover relationship name is too long. The name is limited to a maximum of 126 characters
0x00004E9E	The specified DHCP Server has reached the end of the selected range while finding the free IP address	The specified DHCP Server has reached the end of the selected range while finding the free IP address
0x00004E9F	The synchronization of leases in the scopes being added to the failover relationship failed.	The synchronization of leases in the scopes being added to the failover relationship failed.
0x00004EA0	The relationship cannot be created on the DHCP server as the maximum number of allowed relationship has exceeded.	The relationship cannot be created on the DHCP server as the maximum number of allowed relationship has exceeded.
0x00004EA1	A Scope configured for failover cannot be changed to type BOOTP or BOTH if one of the servers in the failover relationship is Windows Server 2012.	A Scope configured for failover cannot be changed to type BOOTP or BOTH if one of the servers in the failover relationship is Windows Server 2012.
0x00004EA2	Number of scopes being added to the failover relationship exceeds the max number of scopes which can be added to a failover relationship at one time.	Number of scopes being added to the failover relationship exceeds the max number of scopes which can be added to a failover relationship at one time.
0x00004EA3	A scope supporting BOOTP clients cannot be added to a failover relationship.	A scope supporting BOOTP clients cannot be added to a failover relationship.
0x00004EA4	An IP address range of a scope which is part of a failover relationship cannot be deleted. The scope will need to be removed from the failover relationship before deleting the range.	An IP address range of a scope which is part of a failover relationship cannot be deleted. The scope will need to be removed from the failover relationship before deleting the range.
0x00004EA5	The server is reintegrating with it's failover partner server. During reintegration, addition or deletion of scopes to the failover relationship is not permitted. Please try this operation after sometime.	The server is reintegrating with it's failover partner server. During reintegration, addition or deletion of scopes to the failover relationship is not permitted. Please try this operation after sometime.
0x00004EA6	A scope configured for failover has settings that are not supported if one of the servers in the failover relationship is running Windows Server 2012.	A scope configured for failover has settings that are not supported if one of the servers in the failover relationship is running Windows Server 2012.
0x00004EA7	IP Address range cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions.	IP Address range cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions.
0x00004EA8	Option values cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions.	Option values cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions.
0x00004EA9	Fully qualified domain name based conditions cannot be used in a policy with configured options or IP address ranges.	Fully qualified domain name based conditions cannot be used in a policy with configured options or IP address ranges.
0x00004EAA	Network Access Protection is not supported by the server.	Network Access Protection is not supported by the server.
0x00004EAB	ERROR_LAST_DHCP_SERVER_ERROR	ERROR_LAST_DHCP_SERVER_ERROR
0x00004EC1	Address allocation triggered for the failover relationship %1.	Address allocation triggered for the failover relationship %1.
0x00004EC2	Scavenger started purging stateless entries.	Scavenger started purging stateless entries.
0x00004EC3	Scavenger finished purging stateless entries.	Scavenger finished purging stateless entries.
0x00004EC4	The total leases deleted in scavenger are %1	The total leases deleted in scavenger are %1
0x00004EC5	Scope %1 which was part of failover relationship %2 was not found in DHCP server database. Please restore the DHCP server database.	Scope %1 which was part of failover relationship %2 was not found in DHCP server database. Please restore the DHCP server database.
0x10000038	Classic	Classic
0x30000065	CreateFailover	CreateFailover
0x30000066	DeleteFailover	DeleteFailover
0x30000067	AddFailoverScope	AddFailoverScope
0x30000068	RemoveFailoverScope	RemoveFailoverScope
0x30000069	ChangeFailoverConfig	ChangeFailoverConfig
0x3000006A	FailoverStateChange	FailoverStateChange
0x3000006B	TimeOutOfSync	TimeOutOfSync
0x3000006C	CommUp	CommUp
0x3000006D	CommDown	CommDown
0x3000006E	BINDING-UPDATE	BINDING-UPDATE
0x3000006F	BINDING-ACK	BINDING-ACK
0x30000070	CONNECT	CONNECT
0x30000071	CONNECT-ACK	CONNECT-ACK
0x30000072	UPDATE-REQUEST-ALL	UPDATE-REQUEST-ALL
0x30000073	UPDATE-REQUEST	UPDATE-REQUEST
0x30000074	UPDATE-DONE	UPDATE-DONE
0x30000075	STATE	STATE
0x30000076	CONTACT	CONTACT
0x30000077	MessageAuthentication	MessageAuthentication
0x30000078	InitializeFailover	InitializeFailover
0x30000079	FailoverIPPoolTakeover	FailoverIPPoolTakeover
0x50000002	Error	Error
0x50000003	Warning	Warning
0x50000004	Information	Information
0x7000007A	DHCP Failover	DHCP Failover
0x7000007B	Policy	Policy
0x7000007C	Name Registration.	Name Registration.
0x90000001	Microsoft-Windows-DHCP Server Events/Operational	Microsoft-Windows-DHCP Server Events/Operational
0x90000002	Microsoft-Windows-DHCP Server Events/FilterNotifications	Microsoft-Windows-DHCP Server Events/FilterNotifications
0x90000003	Microsoft-Windows-DHCP Server Events/Admin	Microsoft-Windows-DHCP Server Events/Admin
0x90000004	Microsoft-Windows-DHCP Server Events/AuditLogs	Microsoft-Windows-DHCP Server Events/AuditLogs
0x90000005	Microsoft-Windows-DHCP Server Events/DebugLogs	Microsoft-Windows-DHCP Server Events/DebugLogs
0x90000006	System	System
0xB0000046	Scope: %1 for IPv4 is Configured by %2.	Scope: %1 for IPv4 is Configured by %2.
0xB0000047	Scope: %1 for IPv4 is Modified by %2.	Scope: %1 for IPv4 is Modified by %2.
0xB0000048	Scope: %1 for IPv4 is Deleted by %2.	Scope: %1 for IPv4 is Deleted by %2.
0xB0000049	Scope: %1 for IPv4 is Activated by %2.	Scope: %1 for IPv4 is Activated by %2.
0xB000004A	Scope: %1 for IPv4 is DeActivated by %2.	Scope: %1 for IPv4 is DeActivated by %2.
0xB000004B	Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds.	Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds.
0xB000004C	Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3	Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3
0xB000004D	Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.	Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.
0xB000004E	Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.	Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.
0xB000004F	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 .	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 .
0xB0000050	Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records.	Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records.
0xB0000051	Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.	Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.
0xB0000052	Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.	Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.
0xB0000053	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.	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.
0xB0000054	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.	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.
0xB0000055	Policy based assignment has been disabled for scope %1.	Policy based assignment has been disabled for scope %1.
0xB0000056	Policy based assignment has been enabled for scope %1.	Policy based assignment has been enabled for scope %1.
0xB0000057	Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.	Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.
0xB0000058	Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.	Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.
0xB0000059	Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.	Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.
0xB000005A	NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.	NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.
0xB000005B	NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.	NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.
0xB000005C	NAP Profile is configured on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3.	NAP Profile is configured on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3.
0xB000005D	NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4.	NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4.
0xB000005E	The following NAP Profile: %1 is deleted on Scope: %2 by %3.	The following NAP Profile: %1 is deleted on Scope: %2 by %3.
0xB000005F	Scope: %1 for Multicast IPv4 is Configured by %2.	Scope: %1 for Multicast IPv4 is Configured by %2.
0xB0000060	Scope: %1 for Multicast IPv4 is Deleted by %2.	Scope: %1 for Multicast IPv4 is Deleted by %2.
0xB0000061	Scope: %1 for IPv4 is Added in Superscope: %2 by %3.	Scope: %1 for IPv4 is Added in Superscope: %2 by %3.
0xB0000062	SuperScope: %1 for IPv4 is Configured by %2.	SuperScope: %1 for IPv4 is Configured by %2.
0xB0000063	SuperScope: %1 for IPv4 is Deleted by %2.	SuperScope: %1 for IPv4 is Deleted by %2.
0xB0000064	Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.	Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.
0xB0000065	Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.	Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.
0xB0000066	Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.	Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.
0xB0000067	Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.	Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.
0xB0000068	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.	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.
0xB0000069	Server level option %1 for IPv4 has been updated by %2.	Server level option %1 for IPv4 has been updated by %2.
0xB000006A	Reservation: %1 for IPv4 is Configured under Scope %2 by %3.	Reservation: %1 for IPv4 is Configured under Scope %2 by %3.
0xB000006B	Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.	Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.
0xB000006C	Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.	Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.
0xB000006D	Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.	Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.
0xB000006E	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.	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.
0xB000006F	Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records.	Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records.
0xB0000070	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.	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.
0xB0000071	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.	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.
0xB0000072	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.	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.
0xB0000073	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.	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.
0xB0000074	Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4.	Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4.
0xB0000075	Policy based assignment has been disabled at server level.	Policy based assignment has been disabled at server level.
0xB0000076	Policy based assignment has been enabled at server level.	Policy based assignment has been enabled at server level.
0xB0000077	Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.	Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.
0xB0000078	Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.	Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.
0xB0000079	Link Layer based filtering is Enabled in the Allow List of the IPv4 by %1	Link Layer based filtering is Enabled in the Allow List of the IPv4 by %1
0xB000007A	Link Layer based filtering is Disabled in the Allow List of the IPv4 by %1	Link Layer based filtering is Disabled in the Allow List of the IPv4 by %1
0xB000007B	Filter for physical address: %1, hardware type: %3 added to the IPv4 Allow List by %2.	Filter for physical address: %1, hardware type: %3 added to the IPv4 Allow List by %2.
0xB000007C	Filter for physical address: %1, hardware type: %3 removed from the IPv4 Allow List by %2.	Filter for physical address: %1, hardware type: %3 removed from the IPv4 Allow List by %2.
0xB000007D	Link Layer based filtering is Enabled in the Deny List of the IPv4 by %1	Link Layer based filtering is Enabled in the Deny List of the IPv4 by %1
0xB000007E	Link Layer based filtering is Disabled in the Deny List of the IPv4 by %1	Link Layer based filtering is Disabled in the Deny List of the IPv4 by %1
0xB000007F	Filter for physical address: %1, hardware type: %3 added to the IPv4 Deny List by %2.	Filter for physical address: %1, hardware type: %3 added to the IPv4 Deny List by %2.
0xB0000080	Filter for physical address: %1, hardware type: %3 removed from the IPv4 Deny List by %2.	Filter for physical address: %1, hardware type: %3 removed from the IPv4 Deny List by %2.
0xB0000081	Scope: %1 for IPv6 is Configured by %2.	Scope: %1 for IPv6 is Configured by %2.
0xB0000082	Scope: %1 for IPv6 is Deleted by %2.	Scope: %1 for IPv6 is Deleted by %2.
0xB0000083	Scope: %1 for IPv6 is Activated by %2.	Scope: %1 for IPv6 is Activated by %2.
0xB0000084	Scope: %1 for IPv6 is DeActivated by %2.	Scope: %1 for IPv6 is DeActivated by %2.
0xB0000085	Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime: %2 by %3. The previous configured Lease Preferred Lifetime was: %4.	Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime: %2 by %3. The previous configured Lease Preferred Lifetime was: %4.
0xB0000086	Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4.	Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4.
0xB0000087	Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3.	Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3.
0xB0000088	Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.	Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.
0xB0000089	Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.	Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.
0xB000008A	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.	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.
0xB000008B	Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records.	Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records.
0xB000008C	Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.	Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.
0xB000008D	Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.	Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.
0xB000008E	Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.	Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.
0xB000008F	Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.	Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.
0xB0000091	Reservation: %1 for IPv6 is Configured under Scope %2 by %3.	Reservation: %1 for IPv6 is Configured under Scope %2 by %3.
0xB0000093	Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.	Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.
0xB0000094	Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.	Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.
0xB0000095	Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.	Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.
0xB0000096	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.	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.
0xB0000097	Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records.	Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records.
0xB0000098	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.	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.
0xB0000099	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.	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.
0xB000009A	Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.	Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.
0xB000009B	Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.	Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.
0xB000009C	Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.	Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.
0xB000009D	Scope: %1 for IPv6 is Modified by %2.	Scope: %1 for IPv6 is Modified by %2.
0xB000009E	DHCPv6 Stateless client inventory has been enabled for the scope %1.	DHCPv6 Stateless client inventory has been enabled for the scope %1.
0xB000009F	DHCPv6 Stateless client inventory has been disabled for the scope %1.	DHCPv6 Stateless client inventory has been disabled for the scope %1.
0xB00000A0	DHCPv6 Stateless client inventory has been enabled for the server.	DHCPv6 Stateless client inventory has been enabled for the server.
0xB00000A1	DHCPv6 Stateless client inventory has been disabled for the server.	DHCPv6 Stateless client inventory has been disabled for the server.
0xB00000A2	Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours.	Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours.
0xB00000A3	Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.	Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.
0xB00000A4	Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.	Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.
0xB00000A5	Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.	Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.
0xB00000A6	Server level option %1 for IPv6 has been updated by %2.	Server level option %1 for IPv6 has been updated by %2.
0xB00000A7	Server level option %1 for IPv4 has been removed by %2.	Server level option %1 for IPv4 has been removed by %2.
0xB00000A8	Option setting: %2 has been removed from IPv4 scope: %1 by %3.	Option setting: %2 has been removed from IPv4 scope: %1 by %3.
0xB00000A9	Option setting: %3 has been removed from the reservation: %1 in IPv4 scope: %2 by %4.	Option setting: %3 has been removed from the reservation: %1 in IPv4 scope: %2 by %4.
0xB00000AA	Server level option %1 for IPv6 has been removed by %2.	Server level option %1 for IPv6 has been removed by %2.
0xB00000AB	Option setting: %2 has been removed from IPv6 scope: %1 by %3.	Option setting: %2 has been removed from IPv6 scope: %1 by %3.
0xB00000AC	Option setting: %3 has been removed from the reservation: %1 in IPv6 scope: %2 by %4.	Option setting: %3 has been removed from the reservation: %1 in IPv6 scope: %2 by %4.
0xB0004E80	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.	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.
0xB0004E81	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.	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.
0xB0004E83	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.	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.
0xB0004E84	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.	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.
0xB0004EFC	Policy %2 for server is %1.	Policy %2 for server is %1.
0xB0004EFD	Policy %2 for scope %3 is %1.	Policy %2 for scope %3 is %1.
0xB0004EFE	The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.	The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.
0xB0004EFF	The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2.	The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2.
0xB0004F00	A new server wide IPv4 policy %1 was created. The processing order of the policy is %2.	A new server wide IPv4 policy %1 was created. The processing order of the policy is %2.
0xB0004F01	A new scope policy %1 was created in scope %3. The processing order of the policy is %2.	A new scope policy %1 was created in scope %3. The processing order of the policy is %2.
0xB0004F02	Policy %1 was deleted from server.	Policy %1 was deleted from server.
0xB0004F03	Policy %1 was deleted from scope %2.	Policy %1 was deleted from scope %2.
0xB0004F04	The IP address range from %1 was set for the scope %3 policy %2.	The IP address range from %1 was set for the scope %3 policy %2.
0xB0004F05	The IP address range from %1 was removed from the scope %3 policy %2.	The IP address range from %1 was removed from the scope %3 policy %2.
0xB0004F06	The value %2 was set for the option %1 for the server policy %3.	The value %2 was set for the option %1 for the server policy %3.
0xB0004F07	The value %2 was set for the option %1 for the scope %4 policy %3.	The value %2 was set for the option %1 for the scope %4 policy %3.
0xB0004F08	The value %2 was removed from the option %1 for the server policy %3.	The value %2 was removed from the option %1 for the server policy %3.
0xB0004F09	The value %2 was removed from the option %1 for the scope %4 policy %3.	The value %2 was removed from the option %1 for the scope %4 policy %3.
0xB0004F0A	Server policy %2 has been renamed to %1.	Server policy %2 has been renamed to %1.
0xB0004F0B	Scope %3 policy %2 has been renamed to %1.	Scope %3 policy %2 has been renamed to %1.
0xB0004F0C	Description of server policy %2 was set to %1.	Description of server policy %2 was set to %1.
0xB0004F0D	Description of scope %3 policy %2 was set to %1.	Description of scope %3 policy %2 was set to %1.
0xB0004F0E	Processing order of server policy %3 was changed to %1 from %2.	Processing order of server policy %3 was changed to %1 from %2.
0xB0004F0F	Processing order of scope %4 policy %3 was changed to %1 from %2.	Processing order of scope %4 policy %3 was changed to %1 from %2.
0xB0004F10	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.	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.
0xB0004F11	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.	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.
0xB0004F12	Failover relationship %1 between %2 and %3 has been deleted.	Failover relationship %1 between %2 and %3 has been deleted.
0xB0004F13	Scope %1 has been added to the failover relationship %2 with server %3.	Scope %1 has been added to the failover relationship %2 with server %3.
0xB0004F14	Scope %1 has been removed from the failover relationship %2 with server %3.	Scope %1 has been removed from the failover relationship %2 with server %3.
0xB0004F15	The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.	The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.
0xB0004F16	The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.	The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.
0xB0004F17	The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4.	The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4.
0xB0004F18	The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server.	The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server.
0xB0004F19	The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance.	The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance.
0xB0004F1A	The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby.	The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby.
0xB0004F1B	The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.	The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.
0xB0004F1D	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 .	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 .
0xB0004F1E	Server has established contact with failover partner server %1 for relationship %2 .	Server has established contact with failover partner server %1 for relationship %2 .
0xB0004F1F	Server has lost contact with failover partner server %1 for relationship %2 .	Server has lost contact with failover partner server %1 for relationship %2 .
0xB0004F20	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F21	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F22	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F23	The failover state of server: %1 for failover relationship: %2 changed to : %3.	The failover state of server: %1 for failover relationship: %2 changed to : %3.
0xB0004F24	The failover state of server: %1 for failover relationship: %2 changed to: %3.	The failover state of server: %1 for failover relationship: %2 changed to: %3.
0xB0004F25	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F26	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F27	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F28	Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F29	Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F2A	Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F2B	Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F2C	Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F2D	Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F2E	Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F2F	Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F30	Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F31	Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F32	Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F33	Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F34	Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F35	Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F36	Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F37	Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F38	Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F39	Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F3A	Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.	Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.
0xB0004F3B	Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest was not configured.	Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest was not configured.
0xB0004F3C	Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest was not present.	Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest was not present.
0xB0004F3D	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.	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.
0xB0004F3E	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.	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.
0xB0004F3F	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.	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.
0xB0004F40	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.	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.
0xB0004F41	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.	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.
0xB0004F42	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.	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.
0xB0004F43	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.	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.
0xB0004F44	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.	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.
0xB0004F45	A UPDREQ message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.	A UPDREQ message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.
0xB0004F46	A UPDREQ message with transaction id: %1 was received from partner server: %2 for failover relationship: %3	A UPDREQ message with transaction id: %1 was received from partner server: %2 for failover relationship: %3
0xB0004F47	A UPDDONE message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.	A UPDDONE message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.
0xB0004F48	A UPDDONE message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.	A UPDDONE message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.
0xB0004F49	A UPDREQALL message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3	A UPDREQALL message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3
0xB0004F4A	A UPDREQALL message with transaction id: %1 was received from partner server: %2 for failover relationship: %3	A UPDREQALL message with transaction id: %1 was received from partner server: %2 for failover relationship: %3
0xB0004F4B	A CONTACT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.	A CONTACT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.
0xB0004F4C	A CONTACT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.	A CONTACT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.
0xB0004F4D	A CONNECT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.	A CONNECT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.
0xB0004F4E	A CONNECT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.	A CONNECT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.
0xB0004F4F	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.	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.
0xB0004F50	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.	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.
0xB0004F51	A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3.	A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3.
0xB0004F52	A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3.	A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3.
0xB0004F53	A BINDING-ACK message with transaction id: %1 was sent for IP address: %2 to partner server: %3 for failover relationship: %4.	A BINDING-ACK message with transaction id: %1 was sent for IP address: %2 to partner server: %3 for failover relationship: %4.
0xB0004F54	A BINDING-ACK message with transaction id: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4.	A BINDING-ACK message with transaction id: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4.
0xB0004F55	A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3 with reject reason: %4.	A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3 with reject reason: %4.
0xB0004F56	A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3 with reject reason: %4.	A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3 with reject reason: %4.
0xB0004F57	The shared secret for failover relationship %2 with server %1 has been changed.	The shared secret for failover relationship %2 with server %1 has been changed.
0xB0004F58	Message authentication for failover relationship %2 with server %1 has been enabled.	Message authentication for failover relationship %2 with server %1 has been enabled.
0xB0004F59	Message authentication for failover relationship %2 with server %1 has been disabled.	Message authentication for failover relationship %2 with server %1 has been disabled.
0xB0004F5A	%1	%1
0xB0004F5B	DNSSuffix of scope %3 policy %2 was set to %1.	DNSSuffix of scope %3 policy %2 was set to %1.
0xB0004F5C	DNSSuffix of server policy %2 was set to %1.	DNSSuffix of server policy %2 was set to %1.
0xB0004F5D	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.	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.
0xB0004F5E	Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3.	Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3.
0xB0004F5F	Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).	Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).
0xB0004F60	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.	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.
0xB0004F61	PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3.	PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3.
0xB0004F62	PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).	PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).
0xB0004F63	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.	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.
0xB0004F64	Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3.	Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3.
0xB0004F65	Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).	Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).
0xB0004F66	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.	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.
0xB0004F67	PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3.	PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3.
0xB0004F68	PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).	PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).

File Name:	dhcpsapi.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-d..serverapi.resources_31bf3856ad364e35_10.0.15063.0_en-us_02ab3bec40a643b3\
File Size:	130 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	132096
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	DHCP Server API Stub DLL
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	dhcpsapi.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	dhcpsapi.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Directory:	%WINDIR%\WinSxS\x86_microsoft-windows-d..serverapi.resources_31bf3856ad364e35_10.0.15063.0_en-us_a68ca0688848d27d\

dhcpsapi.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file dhcpsapi.dll (DHCP Server API Stub DLL).

File Description:	DHCP Server API Stub DLL
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	dhcpsapi.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	dhcpsapi.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x409, 1200