Kerberos Event ID: 529 is logged when you use a local user account to verify security access or group membership on a Windows Server 2003-based Kerberos client

If you run a program on a Service-for-User (S4U) Kerberos authentication supported Microsoft Windows Server 2003-based Kerberos client that uses WMI scripts and requires security access verification and group membership verification, you may receive Kerberos Event ID: 529 logged in the security event log of the client.

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: UserName
Domain: DomainName
Logon Type: 3
Logon Process: Authz
Authentication Package: Kerberos
Workstation Name: WorkstationName
Status code: 0xC000018B
Substatus code: 0x0
Caller User Name: UserName$
Caller Domain: DomainName
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 936
Transited Services:
Source Network Address: IP Address
Source Port: PortNumber

This problem occurs if you use a local user account to run the program and the WMI scripts that you use in the program require Administrators group membership verification. If you use a local user account, the WMI scripts in the program use that local user account to perform the Administrators group membership verification. The WMI scripts use the S4U Kerberos authentication to perform the verification. The S4U Kerberos authentication cannot be successful because the authentication process cannot find any matching records for the local user account in the domain controller. Therefore, the authentication does not occur, and a Kerberos audit failure event is logged on the client computer.

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 do not have to restart your computer 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 versions

Windows Server 2003 64-bit versions

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

For additional information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: