Microsoft KB Archive/281307

= Windows XP and Windows Server 2003 Are Not Advertised as Terminal Services Servers =

Article ID: 281307

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Microsoft Windows XP Tablet PC Edition
 * Microsoft Windows XP Professional for Itanium-based systems
 * Microsoft Windows XP Professional for Itanium-based systems
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q281307



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
When you browse for computers by using the Remote Desktop tool or the Terminal Services Client tool, Windows XP-based and Windows Server 2003-based computers with Remote Desktop enabled may not appear in the list of available computers. Additionally, Windows XP-based and Windows Server 2003-based computers with Remote Desktop enabled may not appear in Microsoft Windows 2000 and Windows Server 2003 Terminal Services Manager.



CAUSE
By default, only Windows Server 2003-based Terminal Services servers and Windows 2000-based servers with Terminal Services installed in either Application Server mode or in Remote Administration mode advertise themselves as Terminal Services servers. This behavior makes the browse list in Remote Desktop and Terminal Services Client more usable, and makes sure that only Terminal Services servers appear in Windows 2000 and Windows Server 2003 Terminal Services Manager.



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 cause a computer that is running Windows XP Professional or Windows Server 2003, but is not configured as a Terminal Services server, to advertise itself as a Terminal Services server:  Start Registry Editor (Regedit.exe). Locate and then click the following registry key:

 Change the value of the  DWORD value from 0 to 1. Quit Registry Editor. Restart the computer.</ol>

Note Windows Server 2003-based computers that are configured as Terminal Services servers, and Windows 2000 Server-based servers or Windows 2000 Advanced Server-based servers with Terminal Services installed in either Application Server mode or in Remote Administration mode already have the  registry value set to 1. Therefore, these servers advertise themselves as Terminal Services servers. <div class="status_section">

STATUS
This behavior is by design.

Keywords: kbenv kbinfo KB281307

-

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

© Microsoft Corporation. All rights reserved.