Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The "Terminal Services" service cannot protect a console session from being disconnected in Windows Server 2008


View products that this article applies to.

Symptoms

Consider the following scenario:
  • On a server that is running Windows Server 2008, the "Terminal Services" service runs in the "Remote Administration" mode.
  • An administrator makes an administrative session to this server by using Remote Desktop Connection.
  • The administrator is prompted by a dialog box to disconnect a session to run the newly made session.
In this scenario, the dialog box lists both the administrative sessions and the console sessions on the server. Then, the "Terminal Services" service cannot protect console sessions from being disconnected. If the administrator disconnects the console session, applications that are running in the console session may not function correctly.

For example:
  • User account "usera" logs on to a console session on a Windows Server 2008-based terminal server.
  • User account "userb" makes an administrative session to the same terminal server.
  • Administrator user account "userc" makes a third administrative session.

    A dialog box appears that prompts "userc" to disconnect a session so that the third session can be made.
In this case, the "Terminal Services" service cannot protect console sessions from being disconnected.

↑ Back to the top


Resolution

After you install the hotfix, the console session is not listed in the dialog box when you are prompted to disconnect a session.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 be running Windows Server 2008 or Windows Server 2008 Service Pack 2 (SP2).

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To use one of the hotfixes in this package, you must create a registry key. To do this, follow these steps:
  1. Click Start
    , type regedit in the Search programs and files box, and then press ENTER.
    If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
  2. Locate and then click the following registry subkey:
    HEKY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Winstations
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type DenyConsoleDisconnect, and then press ENTER.
  5. Right-click DenyConsoleDisconnect, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600 1 . 22xxxWindows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.22635450,04816-Feb-201015:56x86
Termsrv.dll6.0.6002.22340450,04816-Feb-201015:47x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.22635548,86416-Feb-201017:13x64
Termsrv.dll6.0.6002.22340548,86416-Feb-201015:39x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.226351,052,16016-Feb-201016:04IA-64
Termsrv.dll6.0.6002.223401,051,64816-Feb-201015:33IA-64

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size3,068
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameX86_120b4d09586a16f727333238f2671d57_31bf3856ad364e35_6.0.6002.22340_none_78be0e22feed0d75.manifest
File versionNot applicable
File size728
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameX86_70191ad395d479ea90e6963141360bcc_31bf3856ad364e35_6.0.6001.22635_none_2dacd1b793774613.manifest
File versionNot applicable
File size728
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameX86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22635_none_8f0d79bf6d757b75.manifest
File versionNot applicable
File size40,350
Date (UTC)16-Feb-2010
Time (UTC)21:51
PlatformNot applicable
File nameX86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22340_none_90e41a496aa86dd7.manifest
File versionNot applicable
File size40,350
Date (UTC)16-Feb-2010
Time (UTC)21:12
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_06a514c29e9a7362b5f507e2565bb0d2_31bf3856ad364e35_6.0.6001.22635_none_a8def52c2576b3e8.manifest
File versionNot applicable
File size1,106
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameAmd64_9f3a5499fb06953ccd80374ee9081ebd_31bf3856ad364e35_6.0.6002.22340_none_f7673fb83a850f4a.manifest
File versionNot applicable
File size1,106
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22635_none_eb2c154325d2ecab.manifest
File versionNot applicable
File size40,406
Date (UTC)17-Feb-2010
Time (UTC)03:01
PlatformNot applicable
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22340_none_ed02b5cd2305df0d.manifest
File versionNot applicable
File size40,406
Date (UTC)17-Feb-2010
Time (UTC)03:00
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,092
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22635_none_f580bf955a33aea6.manifest
File versionNot applicable
File size19,240
Date (UTC)16-Feb-2010
Time (UTC)21:43
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22340_none_f757601f5766a108.manifest
File versionNot applicable
File size19,240
Date (UTC)16-Feb-2010
Time (UTC)21:05
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_76834259767d33cd3a659d36ef383681_31bf3856ad364e35_6.0.6001.22635_none_29b0158225893dce.manifest
File versionNot applicable
File size1,104
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameIa64_ea2ff42fb83c490c442f95a16d83f8a3_31bf3856ad364e35_6.0.6002.22340_none_ab84d767d800324b.manifest
File versionNot applicable
File size1,104
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameIa64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22635_none_8f0f1db56d738471.manifest
File versionNot applicable
File size40,377
Date (UTC)17-Feb-2010
Time (UTC)02:48
PlatformNot applicable
File nameIa64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22340_none_90e5be3f6aa676d3.manifest
File versionNot applicable
File size40,377
Date (UTC)17-Feb-2010
Time (UTC)02:27
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,249
Date (UTC)24-Feb-2010
Time (UTC)08:17
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22635_none_f580bf955a33aea6.manifest
File versionNot applicable
File size19,240
Date (UTC)16-Feb-2010
Time (UTC)21:43
PlatformNot applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22340_none_f757601f5766a108.manifest
File versionNot applicable
File size19,240
Date (UTC)16-Feb-2010
Time (UTC)21:05
PlatformNot applicable

↑ Back to the top


Keywords: kbfix, kbexpertiseinter, kbqfe, kbautohotfix, kbhotfixserver, kbsurveynew, kbprb, KB970911

↑ Back to the top

Article Info
Article ID : 970911
Revision : 2
Created on : 4/22/2010
Published on : 4/22/2010
Exists online : False
Views : 483