You experience problems when you upgrade a Windows 2000-based server that has Terminal Server enabled to Windows Server 2003

Article translations Article translations
Article ID: 939087 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
Expand all | Collapse all

SYMPTOMS

You upgrade a Microsoft Windows 2000-based member server to Microsoft Windows Server 2003. The member server has Terminal Server enabled in Remote Administration mode.

In this scenario, you experience the following problems:
  • In the System Properties dialog box, the Remote tab is missing.
  • When you view the properties of the Terminal Services service, the path of the program file is set to "Winnt\System32\Termserv.exe" and not to "Windows\System32\Svchost.exe -k termsvcs." Additionally, the Terminal Services service is disabled.
  • In the
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\ProductVersion
    registry subkey, the registry entry value is set to 5.0.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type cd %windir%\system32, and then press ENTER.
  3. Type regsvr32 remotepg.dll, and then press ENTER.
  4. Type exit, and then press ENTER to close the Command Prompt window.
  5. On the Windows Server 2003-based terminal server, export the following registry keys to back them up:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermDD
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SvcHost\Termsvcs
  6. On a Windows Server 2003-based terminal server that is working correctly, export the following registry subkeys:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermDD
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SvcHost\termsvcs
  7. On the terminal server that is experiencing the problems that are described in the "Symptoms" section, import the registry subkeys that you exported in step 6.
  8. Restart the terminal server.

Properties

Article ID: 939087 - Last Review: July 28, 2007 - Revision: 1.2
APPLIES TO
  • 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
Keywords: 
kbexpertiseadvanced kbtshoot KB939087

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com