Terminal Services Client Does Not Cache User Principle Name (UPN)

ID: Q243656

The information in this article applies to:

Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Server

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

By default, a Terminal Services client caches the last logged-on user name locally in the registry on the client computer under the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Username

Each time you start the Terminal Services Client software, the Log On dialog box is populated with the value from this registry key. However, when you log on using a User Principle Name (UPN), only the user name is cached. For example, if you log on as username@domainname.com, only username is listed in the User Name box the next time you attempt to log on.

RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

To work around this behavior, you can add a registry value to the Windows 2000-based server that is running Terminal Services to automatically convert the user logon name to a UPN. To do so, use Registry Editor to locate the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\WinLogon

Add a value named TSForceUPN with a data type of REG_SZ. If you set the data value of the TSForceUPN value to 1, the policy is enabled. If you set it to 0, the policy is disabled. When the policy is enabled, the server attempts to resolve all user logon names to a UPN. If a user logon name cannot be resolved, no cached user logon name is displayed.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

Additional query words:

Keywords : kbtool
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb