Win2K SP2 Released
In case you missed the hoopla, last week, Microsoft released Service Pack 2 (SP2) for Windows 2000. Microsoft article Q282522 contains links for the four pages of changes.

The Terminal Services section contains the following articles:

  • Registry Flag fUseDefaultGina Does Not Work
    "http://support.microsoft.com/support/kb/articles/Q214/4/88.asp"


  • Q256843 Access Violation May Occur in Termsrv.exe When You Are Using Time-Outs
    "http://support.microsoft.com/support/kb/articles/Q256/8/43.asp"


  • Terminal Server Ignores NumberOfRings Parameter, Answering on First Ring Only
    "http://support.microsoft.com/support/kb/articles/Q261/2/78.asp"


  • Client Connection Manager for Terminal Services Causes Access Violation in Explorer.exe
    "http://support.microsoft.com/support/kb/articles/Q262/1/37.asp"


  • There Are No Extended Characters When You Use an MS-DOS-Based Program in a Terminal Services Session
    "http://support.microsoft.com/support/kb/articles/Q263/7/49.asp"


  • Kernel Objects May Not Be Shared Across Terminal Services Sessions
    "http://support.microsoft.com/support/kb/articles/Q264/6/51.asp"


  • Terminal Services Server Does Not Restart with Restart Command from a Client Session
    "http://support.microsoft.com/support/kb/articles/Q265/4/19.asp"


  • Terminal Services Server Switches to Install Mode for Users When Running RunOnce Entries
    "http://support.microsoft.com/support/kb/articles/Q266/7/83.asp"


  • Terminal Services License Server Status Appears as UNKNOWN
    "http://support.microsoft.com/support/kb/articles/Q269/3/49.asp"


  • Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server
    "http://support.microsoft.com/support/kb/articles/Q270/5/88.asp"


  • ICA Clients Over Dial-Up Link May Unexpectedly Disconnect
    "http://support.microsoft.com/support/kb/articles/Q274/7/68.asp"


  • Using English Version of Windows 2000, Cannot Dial from Portugal to Activate License Servers
    "http://support.microsoft.com/support/kb/articles/Q289/1/70.asp"

The following articles address terminal services-specific issues:

  • DNS Performance Counters Do Not Show Values When Collected from a Terminal Services Session
    "http://support.microsoft.com/support/kb/articles/Q277/9/32.asp"


  • Terminal Services Session Displays Shutdown Button When Group Policy Is Enabled
    "http://support.microsoft.com/support/kb/articles/Q271/9/77.asp"


  • ATM Virtual Adapter Does Not Appear in Terminal Services Configuration Tool
    "http://support.microsoft.com/support/kb/articles/Q271/9/14.asp"


  • Terminal Window After Dialing Does Not Work in Terminal Services Session
    "http://support.microsoft.com/support/kb/articles/Q277/5/61.asp"


  • Terminal Server Client Licensing Information Is Not Encrypted in the Network Packets
    "http://support.microsoft.com/support/kb/articles/Q295/0/80.asp"


  • "Stop 0x1E" or "Stop 0x50" with Terminal Services Client Print Session
    "http://support.microsoft.com/support/kb/articles/Q279/3/43.asp"


  • Terminal Services Client Is Not Updated When Service Pack 1 Is Installed
    "http://support.microsoft.com/support/kb/articles/Q296/7/21.asp"

Changing the Default Event Viewer Log File Location
The Event Viewer tool maintains three log files that contain system, application, and security event messages. However, if disk space isn't available, the Event Viewer tool might not be able to write event messages to one of these log files. To increase disk space, you can modify the default location by following the instructions in Microsoft article Q216169.

System32 Folder Opens When Logging Into NT
If the registry contains a null, incomplete, or damaged entry, or if the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run is a single quote character ("'"), when you log on, a Windows Explorer window might open that displays the System32 folder's contents. To resolve this problem, follow the instructions in Microsoft article Q170086.

Internet Connector License Types for Win2K
As Microsoft article Q272235 explains, Windows 2000 has two Internet Connector license types that you use for different functions and install in different ways. The article contains links to licensing information, but here's the gist.

The Win2K Server Internet Connector license allows for an unlimited number of authenticated Internet connections and lets a Web server authenticate users without purchasing individual licenses for every user. This license type doesn't contain terminal services client access licenses (TSCALs) and is configured through Internet Information Server. Implement the Internet Connector license in Microsoft IIS 5.0 by changing it from Anonymous connections to Authenticated connections and adding the Win2K Internet Connector licensing.

The Win2K Terminal Services Internet Connector License allows 200 concurrent users to connect anonymously to a Terminal Services server over the Internet. It's available only in the Select Volume Software licensing program. A Win2K-based Terminal Services Licensing server tracks the Internet Connector licenses and installs them instead of TSCALs. Then you can use the Terminal Services Configuration tool on the Terminal Services server to modify the Internet Connector License server settings from Disable to Enable. If you install a Terminal Services Internet Connector license on the License server, then all connections to that Terminal Services server are automatically logged on as the local account TSInternetUser and can't be overridden unless you disable the Internet Connector licensing. Because all connections to a Terminal Services server that uses a Terminal Services Internet Connector license use the same TSUser account, it doesn't let administrators connect and remotely perform administrative tasks on the server.

Minimized Terminal Services Manager Won't Maximize
When you start the Terminal Services Manager tool in minimized mode from the Win2K-based Terminal Server console, Terminal Services Manager might blink on the taskbar, and you won't able to switch back and use Terminal Services Manager. To learn how to edit the window properties, see Microsoft article Q277689.

Unattended Installation File Isn't Deleted After Setup Finishes
When an unattended Windows NT 4.0 installation process finishes, a copy of the unattend.txt file that contains installation parameters can remain on the hard disk. Depending on the installation method you use, the file could contain sensitive information, possibly including the local administrator's username and password. Microsoft article Q241219 suggests a couple of workarounds, including using RunOnce to delete the .inf file that contains the setup information. This problem doesn't affect Win2K unattended installations.

DNS Server Logs Event 453 or 7053 (Sendto Function Failed)
According to Microsoft article Q244132, after you upgrade a DNS-based server from NT 4.0 Service Pack 3 (SP3) to SP4, SP5, or SP6, the System event log could record errors for the DNS server. This problem occurs because DNS encounters a referral to an invalid address for a name server. The referral resource record lists the IP address of the name server as 0.0.0.0. DNS can't send a query to an invalid address and logs the error against the sendto function. SP6 doesn't seem to address this problem, but the article does tell you how to get a fix.

Nonpaged Pool Memory Leak Might Occur When Reading Partition Table
In NT Server 4.0, Terminal Server Edition (TSE), a nonpaged pool memory leak might occur when functions such as IoReadPartitionTable() or DeviceIoControl() attempt to read a partition table. According to Microsoft article Q244509, this problem occurs because memory allocated when reading the partition table might not be freed when the system returns an error, such as STATUS_DEVICE_BUSY. See the article to learn how to get a fix.

Win2K Terminal Services Might Not Display 256-Color Image Properly
Some programs might not display 256-color pictures properly in a Terminal Services session because of video corruption. Microsoft article Q272311 lists this fix as a post-SP1 fix, but I don't see it in the list of fixes in SP2. See the article to learn how to get a fix.

VBScript Error Message Occurs When You Use TSAC
When you use Terminal Services Advanced Client (TSAC) to connect to a Terminal Services server, a VBScript error tells you that the client can't connect to the named terminal server. Microsoft article Q282128 contains suggestions for troubleshooting this problem, including the use of ping and telnet, and a link to an article about troubleshooting TCP/IP problems.

Printer Redirection Architecture in Win2K Terminal Services
If you're interested in how automatic printer redirection works, check out Microsoft article Q294429, which explains the process.

Number Lock Status Not Synchronized During Terminal Services Session
The number lock indicator on TSE or Terminal Services clients running Windows Me or Windows 9x might not be synchronized with the Terminal Services client session. On these clients, if you press the Ctrl+Alt+Num Lock keys when the Terminal Services client window is active, the number-lock status changes inside that Terminal Services session. The problem is that the status changes only in the Terminal Services session; the keyboard indicator light and the OS don't change the number-lock status. Microsoft has a post-SP1 (and post-SP6) fix for this problem, but I don't see any evidence that the fix is in SP2. See Microsoft article Q295951 to learn how to get a fix for this problem.

Use QChain.exe to Install Multiple Hotfixes with Only One Reboot
Microsoft has released a command-line tool named QChain.exe that lets system administrators safely chain hotfixes together. Hotfix chaining involves installing multiple hotfixes without rebooting between each installation. Without this tool, the only supported chaining method is to reboot after each hotfix installation. If the tool works as promised, Qchain should reduce the amount of time required to install hotfixes on TSE and Terminal Services. See Microsoft article Q296861 to learn how to get the tool and use it.

Win2K Upgrade Paths
If you've ever tried to sort out which OSs have upgrade paths to Win2K, see Microsoft article Q232039, which lists the paths for both single-user machines and terminal servers.

Initial Program List Determines When the Terminal Server Session Ends As Microsoft article Q274740 explains, when you set the "Initial program" on a Win2K terminal server, the server monitors the processes running in your session. After you quit all nonsystem processes in that session, the session ends and logs you off. This occurs only if you specified the "Initial program" (as opposed to a desktop) on either the terminal server client or in the terminal server's configuration. See the article for the list of processes the terminal server doesn't monitor.

Slow Performance When Lotus Notes Runs on a Terminal Server
On a terminal server running Lotus Notes 5.0, up to 10 words of typed data could be delayed before they appear on the screen. According to Microsoft article Q276415, you can resolve this problem by upgrading to Notes 5.02, which terminal servers support. The article also contains a link to Lotus Notes' official support policy for terminal servers.