Terminal Server and connected Terminal Services clients pause when a Terminal Services client logs on or logs off

Symptoms

When a Terminal Services client logs on or logs off (either in a session or on the console of the Terminal server), the Microsoft Windows Server 2003-based or the Microsoft Windows 2000-based Terminal server together with the connected Terminal Services client computers may stop responding or may pause for several seconds. Users may also experience one or more of the follow symptoms:
  • When a user types in a document, characters do not appear on the screen until this pause has ended.
  • Keyboard input and mouse input are queued, but they are not processed until this pause has ended.
  • Live performance monitoring (Perfmon) graphs have missing data points during this pause.
  • All running programs appear to stop responding, or "hang," during this pause.
  • When Spooler is under a load from a large number of users, a high CPU usage is displayed for it.

Cause

This problem may occur if there is a contention among server resources. The contention causes a delay in processing that appears as a pause or as unresponsiveness.

Resolution

Windows Server 2008

You do not have to apply a hotfix to resolve this issue in Windows Server 2008. However, you must follow the instructions in the "More Information" section.

Windows Server 2003

You do not have to apply a hotfix to resolve this issue in Windows Server 2003. However, you must follow the instructions in the "More Information" section.

Windows 2000

To resolve this issue in Windows 2000 Server, you must install a hotfix, and then follow the instructions in the "More Information" section.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have Windows 2000 Service Pack 3 (SP3) or Windows 2000 Service Pack 4 (SP4) installed. For more information about how to obtain the latest Windows 2000 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to obtain the latest Windows 2000 service pack

Restart requirement
You must restart the computer after you apply this hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
   Date         Time   Version            Size    File name
--------------------------------------------------------------
02-Aug-2004 18:00 5.0.2195.6920 126,736 Adsldp.dll
02-Aug-2004 18:00 5.0.2195.6960 132,880 Adsldpc.dll
02-Aug-2004 18:00 5.0.2195.6896 63,760 Adsmsext.dll
02-Aug-2004 18:00 5.0.2195.6928 381,712 Advapi32.dll
24-Mar-2004 02:17 5.0.2195.6824 42,256 Basesrv.dll
02-Aug-2004 18:00 5.0.2195.6866 69,904 Browser.dll
16-Jan-2004 00:18 5.0.2195.6891 35,632 Classpnp.sys
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
24-Feb-2004 05:10 5.0.2195.6901 30,864 Disk.sys
02-Aug-2004 18:00 5.0.2195.6920 136,464 Dnsapi.dll
02-Aug-2004 18:00 5.0.2195.6876 92,432 Dnsrslvr.dll
02-Aug-2004 18:00 5.0.2195.6920 47,376 Eventlog.dll
15-Apr-2004 22:00 5.0.3900.6920 242,448 Explorer.exe
02-Aug-2004 18:00 0.2.0.1 138,000 Faxui.dll
19-Jun-2003 20:05 5.0.2195.6660 233,744 Gdi32.dll
02-Aug-2004 18:00 5.0.2195.6939 148,752 Kdcsvc.dll
03-May-2004 23:59 5.0.2195.6922 206,096 Kerberos.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
21-Sep-2003 00:32 5.0.2195.6824 71,888 Ksecdd.sys
02-Aug-2004 18:00 5.0.2195.6960 256,784 Localspl.dll
11-Jun-2004 22:18 5.0.2195.6940 512,784 Lsasrv.dll
11-Jun-2004 22:18 5.0.2195.6940 33,552 Lsass.exe
10-Feb-2004 19:47 5.0.2195.6897 30,160 Mountmgr.sys
24-Mar-2004 02:17 5.0.2195.6824 54,544 Mpr.dll
27-Jul-2004 22:03 5.0.2195.6961 409,360 Mrxsmb.sys
02-Aug-2004 18:00 5.0.2195.6958 335,120 Msgina.dll
05-May-2004 01:05 5.0.2195.6926 114,960 Msv1_0.dll
02-Aug-2004 18:00 5.0.2195.6958 309,008 Netapi32.dll
02-Aug-2004 18:00 5.0.2195.6921 361,744 Netlogon.dll
02-Aug-2004 18:00 5.0.2195.6961 933,648 Ntdsa.dll
23-Jul-2004 19:17 5.0.2195.6960 1,704,128 Ntkrnlmp.exe
23-Jul-2004 19:17 5.0.2195.6960 1,703,744 Ntkrnlpa.exe
23-Jul-2004 19:17 5.0.2195.6960 1,725,504 Ntkrpamp.exe
23-Jul-2004 19:17 5.0.2195.6960 1,680,832 Ntoskrnl.exe
19-Jun-2003 20:05 5.0.2195.6702 66,320 Ntprint.dll
02-Aug-2004 18:00 5.0.2195.6960 955,152 Ole32.dll
02-Aug-2004 18:00 5.0.2195.6868 381,712 Printui.dll
27-Jul-2004 22:03 5.0.2195.6961 169,968 Rdbss.sys
24-Mar-2004 02:17 5.0.2195.6892 90,264 Rdpwd.sys
02-Aug-2004 18:00 5.0.2195.6958 435,984 Rpcrt4.dll
02-Aug-2004 18:00 5.0.2195.6935 212,240 Rpcss.dll
02-Aug-2004 18:00 5.0.2195.6944 392,976 Samsrv.dll
02-Aug-2004 18:00 5.0.2195.6939 114,448 Scecli.dll
02-Aug-2004 18:00 5.0.2195.6939 261,392 Scesrv.dll
02-Aug-2004 18:00 5.0.3900.6960 2,358,544 Shell32.dll
04-Jun-2004 23:13 5.0.2195.6935 5,887,488 Sp3res.dll
02-Aug-2004 18:00 5.0.2195.6938 80,144 Spoolss.dll
02-Aug-2004 18:00 5.0.2195.6824 12,560 Usbmon.dll
24-Mar-2004 02:17 5.0.2195.6897 403,216 User32.dll
05-Aug-2003 22:14 5.0.2195.6794 385,808 Userenv.dll
02-Aug-2004 18:00 5.0.2195.6920 48,912 W32time.dll
05-Apr-2004 17:46 5.0.2195.6920 57,104 W32tm.exe
14-Jul-2004 01:52 5.0.2195.6960 1,631,696 Win32k.sys
02-Aug-2004 18:00 5.0.2195.6924 88,336 Win32spl.dll
11-Mar-2004 02:37 5.0.2195.6898 181,520 Winlogon.exe
02-Aug-2004 18:00 5.0.2195.6825 114,960 Winspool.drv
02-Aug-2004 18:00 5.0.2195.6958 244,496 Winsrv.dll
02-Aug-2004 18:00 5.0.2195.6920 127,248 Wldap32.dll
02-Aug-2004 18:00 5.0.2195.6824 57,104 Wlnotify.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
14-Jul-2004 01:52 5.0.2195.6960 1,631,696 Win32k.sys
02-Aug-2004 18:00 5.0.2195.6958 244,496 Winsrv.dll
02-Aug-2004 18:15 25,520 Kb324446.cat

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

On a Windows Server 2003-based computer, you must turn on the Enable advanced performance feature for each hard disk that has write caching enabled and that has its write cache protected against accidental loss of power. Additionally, you must configure several registry subkeys.

On a Windows 2000-based computer, after you install the hotfix and then restart the computer, you must turn on the Power Protect write cache option for each hard disk that has write caching enabled and that has its write cache protected against accidental loss of power. Additionally, you must configure several registry subkeys.

Step 1. Turn on the "Enable advanced performance" feature in Windows Server 2003 or the Power Protect option in Windows 2000

Windows Server 2003

To turn on the Enable advanced performance feature on a Windows Server 2003-based computer, follow these steps:

Warning We recommend that you only enable the Enable advanced performance feature for disks that have a backup power supply. This setting improves disk performance, but it also increases the risk of data loss if the disk loses power.
  1. Click Start, right-click My Computer, and then click Manage.
  2. Under System Tools, click Device Manager.
  3. In the right pane, expand Disk drives.
  4. Right-click the disk drive that you want to configure, and then click Properties.
  5. Click the Policies tab.
  6. If the Enable write caching on the disk check box is selected, click to select the Enable advanced performance check box.
  7. Click OK.

Windows 2000

To configure the Power Protect option in Windows 2000, use the Dskcache.exe tool. For more information about how to obtain the Dskcache.exe tool and how to use it to configure the Power Protect write cache option, click the following article number to view the article in the Microsoft Knowledge Base:

811392 Obtain the Dskcache.exe tool to configure the "Power Protected" write cache option

When you run Dskcache.exe without any parameters, the current write cache settings for all hard disks are displayed. For each hard disk that is currently installed on your computer, the following information is displayed:
Disk device :

\\?\\ <SCSI DEVICE ID>


Current Settings :
Write Cache is [ enabled | disabled ]
Power Protect is [ enabled | disabled ]
To turn on the Power Protect option on a hard disk, use the pcommand-line switch.

For example, to turn on the Power Protect option on drive C, type the following line at the command prompt, and then press ENTER:
dskcache +p c:
The following information is displayed for drive C:
Disk device :

\\?\\ <SCSI DEVICE ID>


Current Settings :
Write Cache is enabled
Power Protect is disabled
New Settings :
Write Cache is enabled
Power Protect is enabled
NoteYou can turn on the Power Protect write cache option only for disks that are currently present on your computer. By default, the Power Protect option is turned off. As a result, this option is turned off for any hard disks that are added to the computer after you apply this setting. When you add additional hard disks, you must turn on the Power Protect option for those disks if you want the setting to apply to those disks.

Step 2. Configure registry subkeys

You must also configure the following registry subkeys on the Terminal server and on all file servers:

Note  This section applies to Windows Server 2008, Windows Server 2003 and to Windows 2000.
  • In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameterssubkey, configure the following entries:
    • Name: MaxWorkItems
      Data Type: REG_DWORD
      Value data: 8192 (decimal)
    • Name: MaxMpxCt
      Data Type: REG_DWORD
      Value data: 2048 (decimal)
    • Name: MaxRawWorkItems
      Data Type: REG_DWORD
      Value data: 512 (decimal)
    • Name: MaxFreeConnections
      Data Type: REG_DWORD
      Value data: 100 (decimal)
    • Name: MinFreeConnections
      Data Type: REG_DWORD
      Value data: 32 (decimal)
  • In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\Parameterssubkey, configure the following entry:
    • Name: MaxCmds
      Data Type: REG_DWORD
      Value data: 2048 (decimal)
  • By default, your registry does not have a Configuration Managersubkey. To create the key, locate and then right-click the following subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager
    Point to New, and then click Key. Type Configuration Manager, and then press ENTER.

    In the new HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Configuration Managersubkey, configure the following entry:
    • Name: RegistryLazyFlushInterval
      Data Type: REG_DWORD
      Value data: 60 (decimal)
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file-naming schema for Microsoft Windows software update packages

Propriétés

ID d'article : 324446 - Dernière mise à jour : 10 déc. 2010 - Révision : 1

Commentaires