Microsoft KB Archive/243656

= Terminal Services Client Does Not Cache User Principal Name (UPN) =

Article ID: 243656

Article Last Modified on 2/27/2007

-

APPLIES TO


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

-



This article was previously published under Q243656



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



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\

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 Principal Name (UPN), only the user name is cached. For example, if you log on as @ .com, only   is listed in the User Name box the next time you attempt to log on.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

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 that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbprb KB243656

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.