This article was previously published under Q281307
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.
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.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
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.
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.