The Terminal Server Licensing MMC snap-in or the TS Licensing Manager MMC snap-in uses NT LAN Manager instead of the Kerberos protocol to pass authentication, respectively, in Windows Server 2003 or in Windows Vista and Windows Server 2008

Consider the following scenario:

1. The Terminal Server Licensing Microsoft Management Console (MMC) snap-in is installed on a computer that is running Windows Server 2003 or the TS Licensing Manager MMC snap-in is installed on a computer that is running Windows Server 2008 or Windows Vista.
2. You use the TS Licensing Manager MMC snap-in or the Terminal Server Licensing MMC snap-in to connect to a remote terminal licensing server.
3. Only Kerberos authentication is enabled in the network environment, such as smartcard only logon.

In this scenario, you cannot connect to the remote terminal licensing server in the TS Licensing MMC snap-in or the TS Licensing Manager MMC snap-in.

This is because the TS licensing Manager MMC snap-in or TS Licensing MMC snap-in uses NT LAN Manager (NTLM) instead of the Kerberos protocol to pass authentication.

This problem occurs because an incorrect service principal name (SPN) format is used when the TS Licensing Manager MMC snap-in or the Terminal Server Licensing MMC snap-in sends Kerberos authentication requests. Therefore, Kerberos authentication fails and the TS Licensing Manager MMC snap-in or the Terminal Server Licensing MMC snap-in uses NTLM to pass authentication.

To resolve this problem, apply the following hotfix on a computer that has either the TS Licensing Manager MMC snap-in or the Terminal Server Licensing MMC snap-in installed.

Hotfix information for Windows Vista and Windows Server 2008

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 the problem described in this article. 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

To apply this hotfix on a computer that is running Windows Vista, you must have Windows Vista Service Pack 1 (SP1) or Windows Vista Service Pack 2 (SP2) installed.

No prerequisites are required for computers that are running Windows Server 2008.

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 item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista SP1

For all supported x86-based versions of Windows Server 2008 SP2 and Windows Vista SP2

For all supported x64-based versions of Windows Server 2008 and Windows Vista SP1

For all supported x64-based versions of Windows Server 2008 SP2 and Windows Vista SP2

For all supported IA-64-based versions of Windows Server 2008

For all supported IA-64-based versions of Windows Server 2008 SP2

Hotfix information for Windows Server 2003

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 the problem described in this article. 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

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 (SP2) installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 item in Control Panel.

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

To work around this problem, create a user account and use the RunAs command to open the Terminal Server Licensing MMC snap-in or the TS Licensing Manager MMC snap-in by using the created user account.

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