Article ID: 942219 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
This problem occurs if the following conditions are true:
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/935791/ )How to obtain the latest Windows Vista service pack
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesThere are no prerequisites for installing this hotfix.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Registry informationTo use one of the hotfixes in this package, you do not have to make any changes to the registry.
File informationThe 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 item in Control Panel.
Windows Vista, 32-bit version
Collapse this tableExpand this table
Windows Vista, 64-bit version
Collapse this tableExpand this table
To work around this problem, turn off UAC, or log on by using an account that is not an Administrator account.
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 Vista Service Pack 1.
This option is not available Windows 2008 R2 and Windows 7 anymore. In this operating system release, restricted tokens are not given the TGT Session keys.
This problem occurs when you try to log on to a business application that uses the Kerberos protocol to authenticate the user.
When the SSO feature in the application is implemented, the client computer uses a service ticket for authentication. To obtain this service ticket, the client computer sends a request to Key Distribution Center (KDC). After KDC provides the service ticket to the client computer, the Kerberos service on the client computer stores the service ticket in the credentials cache.
When an application that does not integrate with SSPI uses the Kerberos protocol to authenticate the user, the application needs the TGT session key to build subsequent Kerberos Ticket requests. However, if the UAC feature is turned on, and if the user account is a member of the local Administrators group, the session key in the service ticket is not given to the application.
This is not allowed anymore in Windows 7 since the session keys allows the application to gain a service ticket that would be the input for a full user token on the machine. That would circumvent the goal of using restricted tokens for the user and there is always an elevation prompt when the full token is used.
Microsoft has originally introduced this option documented in this KB article using the registry entry allowtgtsessionkey: http://support.microsoft.com/kb/308339
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 942219 - Last Review: January 16, 2015 - Revision: 10.0