An update is available that introduces the NO_AUTH_REQUIRED flag to the UserAccountControl property in Windows Server 2003 and in Windows 2000

This article describes an update to the UserAccountControl property in Microsoft Windows Server 2003 and in Microsoft Windows 2000. This update introduces the following new flag to the property:When you use Windows Server 2003 or Windows 2000 as a Kerberos Key Distribution Center (KDC) in a mixed environment, such as an environment that has Windows and Unix servers, the KDC adds Privilege Attribute Certificate (PAC) information to a service ticket. If you do not want to add PAC information to a service ticket for a user who is in Active Directory, you can set the NO_AUTH_DATA_REQUIRED flag for the user account after you install the update.

You may want to prevent PAC information from being added to service tickets in situations where the increased size of the service ticket causes issues with programs that use either the User Datagram Protocol (UDP) or remote procedure call (RPC) functionality. A PAC is large, and can increase the size of a ticket more than 500 percent. Tickets that do not have a PAC are approximately 240 bytes. Tickets that have a simple PAC may be approximately 1,200 bytes. Additionally, some services do not understand PAC information. If a PAC is present, services that do not understand the PAC information ignore it.

In a mixed Unix and Windows environment that uses a version of Kerberos that is one or two versions earlier than the current version, ticket requests may not work when a user is a member of many groups in Active Directory. This issue occurs if the PAC information that is added to the ticket increases the size of the ticket to more than the UDP limit of 2,000 bytes. In this situation, ticket requests fail for earlier Unix clients that cannot use TCP.

Because this update applies to Active Directory account properties, install this update on domain controllers. You do not have to install this update on workstations or member servers.

Windows Server 2003

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Windows Server 2003 and Windows 2000

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.

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, submit a request to 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

You must have Windows Server 2003 or Windows 2000 Service Pack 4 (SP4) installed.

Restart requirement

You must restart the 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, x86-based versions

Windows Server 2003, x64-based versions

Windows 2000

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 1.

For more information about the UserAccountControl attribute, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information about the new file naming schema for Microsoft Windows software update packages, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base: