UNC/RRAS Shortcuts Fail for Servers with More Than 700 Shares
You can use RRAS to create a shortcut on a Windows NT Server 4.0, Terminal Server Edition (TSE) desktop that points to a Uniform Naming Convention (UNC) path on another computer. But when you click the shortcut, the connection could fail. According to Microsoft article Q232937, the WNetGetResourceInformation() function on the client retrieves all share names from the remote computer—not just the one you're trying to connect to—when it accesses a remote share from the shortcut. This function has a built-in timer (NetLinkTimeout) with a default timeout value of 7.5 seconds. Enumerating more than about 700 shares over a slow link takes longer than 7.5 seconds, so the function times out and fails. See the article to learn how to edit the registry and increase the timeout.
Stop Error in Win2K Terminal Server
A heavily loaded Windows 2000-based terminal server might experience a "Stop 0x50" (fffffff0,0,8044d24d,0) error in ObReferenceObjectByPointer. See Microsoft article Q295462 to learn how to get a fix for this problem (not included in Service Pack 1—SP1).
Installing IE on TSE
Microsoft article Q286019 explains how to install Internet Explorer (IE) on TSE. It recommends that you install any service packs for TSE before installing IE. Then (on computers with more than 0.5GB of RAM), edit boot.ini to indicate that the server has only 256MB of RAM. After you've successfully installed IE, edit boot.ini again to remove the MAXMEM statement that limits the terminal server to 256MB of RAM.
Caps Lock Might Not Synchronize in a Client Session Running DOS Programs When you run an MS-DOS-based program in a Win2K or TSE terminal services client session, the Caps Lock status in the session might not be synchronized with the actual Caps Lock status indicator on the keyboard. This can happen if you toggle the Caps Lock key when the current active window isn't the terminal services session. Newly started MS-DOS based programs run as expected. See Microsoft article Q278709 to learn how to get fixes for Win2K and TSE terminal servers.
Message Reads "Floppy" Instead of "CD" if SP1 is Installed From Network-Mapped Drive If you add Terminal Services Licensing to Win2K after installing SP1 from a network-mapped drive, you might see a message that prompts you for a floppy disk, rather than a CD-ROM. According to Microsoft article Q295076, this is a known bug—just provide the CD-ROM.
Win2K Terminal Services Doesn't Support Outlook Offline Storage
When you add a Microsoft Exchange server to a Microsoft Outlook profile published from a terminal services session, the setup process doesn't prompt you about whether you travel with the computer, and the Offline folder settings on the Advanced tab for the Microsoft Exchange Server service don't appear. This happens because TSE doesn't support offline folders. See Microsoft article Q242195 for more information.
Stop Error When Using Remote Command Service
When you use the Remote Command Service utility (rcmdsvc.exe) from the NT 4.0 Resource Kit, you could receive a "Stop 0x0000000A in Ntoskrnl.exe" error message. According to Microsoft article Q245538, the Remote Command Service utility, which has client and server components, doesn't work with TSE. You must uninstall it from the terminal server.
Garbled Text During NTLDR Boot Screen
When you install Win2K or NT on computers that use the Intel 810 or 815 video-adapter chipset, the computer might display garbled text when the NTLDR screen appears. The computer might pause at this screen and won't boot until you press a key. According to Microsoft article Q289155, the garbled text doesn't hurt the computer or signify any other problems.