Event ID 10011 — DHCPv6 Audit Logging
Applies To: Windows Server 2008
Dynamic Host Configuration Protocol version6 (DHCPv6) servers include several logging features and server parameters that provide enhanced auditing capabilities. You might need to configure log settings to prevent the log from filling up or to give the server permissions to write to the log. You can configure the following properties to keep your DHCP server logs healthy:
- The audit log file path
- A maximum size restriction
- An interval for disk checking
- A minimum size requirement
|Product:||Windows Operating System|
|Message:||The DHCPv6 audit log file cannot be appended.|
Remove old audit log files or increase the maximum audit log size
If the disk is full or the maximum log size is reached, the DHCP server closes the current file and ignores further requests to log audit events until either midnight or until disk status is improved and the disk is no longer full. If the disk is full, you can add more physical disk space, increase the maximum audit log size, or delete old log files from the default log directory: %windir%\System32\Dhcp.
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.
To increase the maximum audit log size:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
- Click Start, type regedit in Start Search, click Continue, and then press ENTER.
- In the registry tree, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\DHCPServer\Parameters, and then press ENTER.
- Double click DhcpLogFilesMaxSize, select Decimal, and then type a number greater than the current number in Value data.
To verify that the DHCP audit log is functioning correctly:
- At the DHCP server computer, click Start, type Windows Explorer in Start Search, and then press ENTER.
- Navigate the Windows Explorer tree to %windir%\System32\Dhcp.
- View and record the most recent DHCP log file date stamps. They should be recent. Repeat this process at regular intervals and note whether new events are being logged.