Net Logon policies are not applied on a high-speed computer that is a Windows Server 2003-based domain controller

When Group Policy objects that contain defined Net Logon policies are refreshed on a high-speed computer that is a Microsoft Windows Server 2003-based domain controller, you may receive more than one Net Logon event with the same event ID. These events are similar to the following:

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5803
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The following error occurred while reading a parameter 'DnsAvoidRegisterRecords' in the Netlogon Group Policy registry section: Illegal operation attempted on a registry key that has been marked for deletion.

For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: fa 03 00 00

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5803
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The following error occurred while reading a parameter 'NdncSiteCoverage' in the Netlogon Group Policy registry section: Illegal operation attempted on a registry key that has been marked for deletion.

For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: 000003fa

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5803
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The following error occurred while reading a parameter 'GcSiteCoverage' in the Netlogon Group Policy registry section: Illegal operation attempted on a registry key that has been marked for deletion.

For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: 000003fa

When a Group Policy object that contains defined Net Logon policies is refreshed, the Group Policy object searches for certain registry entries that correspond to Net Logon policies in the registry subkey. If the Group Policy object cannot find the registry entries, the Group Policy setting is not applied, and Net Logon events are generated.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You have to restart the Net Logon service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 32-bit editions

Windows Server 2003, 64-bit edition

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base: