Logoff Process Terminates Because Time-Out Is Too Slow
If you configure your Windows 2000 Server Terminal Services servers so that the system ends (resets) idle or disconnected sessions after a certain amount of time, you might not be able to map DFS drives or unload roaming profiles. According to Microsoft article Q299386, an external event resets a session and gives it 3 minutes to end all processes and perform a "graceful" logoff process. If the logoff takes longer than the allotted grace period, the system terminates all processes. Microsoft has a hotfix for this problem; the article also describes a registry edit that increases the logoff timeout.

Stop 1E Error When a Terminal Services Client Logs Off
When a Terminal Services client logs off of a Terminal Services server (with or without Service Pack 2—SP2), the server might blue-screen with a Stop 1E error message. According to Microsoft article Q301376, the system attempts to set the Last Error value, which destroys a process and causes an access violation. If you have this problem, see the article to learn how to get a fix.

Another Stop IE error could happen on a Windows NT Server 4.0, Terminal Server Edition (TSE) terminal server when a timing problem causes the OS to dereference a pointer before it's initialized. See Microsoft article Q294196 to learn how to get a fix for this problem.

Minimizing Graphics Use with Terminal Services
As anyone who works with Terminal Services knows, a key part of improving performance lies in minimizing the number of extraneous graphical updates. Microsoft article Q226931 describes one way to amend this problem and explains how to edit the terminal server's registry to eliminate animation effects and override user desktop settings.

Terminal Services Stores Temporary Folder Configuration in Multiple Registry Locations
By default, a Terminal Services server creates a temporary folder under the %TEMP% folder for each client session. The temporary folder's name is based on the hexadecimal representation of the session ID. You can control the creation of this temporary folder with the flattemp.exe or the Terminal Services Configuration tools using the techniques that Microsoft article Q243555 describes.

Kerberos Realm Ignores Terminal Server Profile Path and Home Directory When You Log On
When you log on to a Kerberos realm, the system might ignore the terminal server profile path and home directory. Instead, the terminal server logon might use the regular roaming profile and cause problems with profile consistency. This error happens if the Graphical Identification and Authentication file (msgina.dll) doesn't retrieve the user name before it retrieves the terminal server user properties. Microsoft article Q299968 explains how to get a fix for this problem.

Users Access a DFS Root Replica On a Remote Site
Even if you've already taken steps to make terminal server clients use the correct DFS share (as Microsoft article Q274411 describes), you might still find that people are using a DFS root replica on a remote site. See Microsoft article Q282071 to learn how to use DFSUTIL to reset site preferences.

Configure RRAS DoD to Interoperate with Third-Party Unnumbered Connections
When you use Dial-on-Demand (DoD) in RRAS to connect to a terminal server, the terminal server might supply an IP address on the same subnet as the LAN that the RRAS server is connected to, making clients on the local LAN and the remote side of RRAS server fall within the same IP network. See Microsoft article Q226322 to learn how to configure RRAS to use "unnumbered connections" so you won't have to subnet the range of IP addresses your ISP gives you.

Terminal Server Profile Path Changes to Windows NT Profile
After you install a TSE terminal server on a domain where the PDC is running File and Printer Sharing for NetWare, the terminal server profile path in User Manager might appear to change to NT Profile. According to Microsoft article Q226480, the profile path changes because of a problem in User Manager for Domains; you can ignore it.

Win2K Hotfixes Repackaged to Verify Previous Fixes
Installing the preliminary (pre-May 16) version of any of the Win2K hotfixes listed in Microsoft article Q299549 might cause you to lose the real fixes included in the service pack. See the article for a list of the affected hotfixes and a fuller explanation of the problem.

Access Violation Occurs in Termsrv.exe on Win2K Server with Citrix MetaFrame 1.8
According to Microsoft article Q297940, an access violation might occur in termsrv.exe on a Terminal Services server running Citrix MetaFrame version 1.8. As a result, users can't create a connection to the terminal server computer. An error might tell you that the instruction at 0x77f82460 referenced memory at 0x003f2801 and that the system couldn't write the memory. To resolve this issue, contact Citrix to obtain MetaFrame 1.8 SP2 for Win2K. See the article for more background information.

Terminal Server Clients Can't Install Mail Certificates
When you attempt to install mail certificates from TSE clients, you might not be able to complete the installation process. The client terminal session might not display the final dialog box that prompts you to confirm the installation; instead, the system might display the dialog box on the server console (session 0). According to Microsoft article Q290605, this error is a known issue with TSE SP6; the only fix at this time is to install the certificates from the console.

Error Message Stop 0XA Occurs When Using NetWare Client Version 4.7
When you use a TSE server running Novell NetWare client version 4.7, you might get this error: STOP 0x0000000A (0x00000063, 0x0000001c, 0x00000000, 0x8011B868). According to Microsoft article Q281381, this error can occur if you use version 4.7. Either uninstall the client or get a new version of the client from Novell.