Symptoms

Consider the following scenario:

  • On a server that is running Windows Server 2008 R2, Remote Desktop Services runs in Remote Administration mode.

  • An administrator creates an administrative session to the server by using Remote Desktop Connection.

  • The administrator is prompted by a dialog box to disconnect a session to run the newly created session.

In this scenario, the dialog box lists both the administrative sessions and the console sessions on the server. Then, Remote Desktop Services does not protect the 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, consider the following specific scenario:

  • The UserA user account logs on to a console session on a Windows Server 2008 R2-based remote desktop server.

  • The UserB user account creates an administrative session to the same remote desktop server.

  • The UserC administrator user account creates a third administrative session.

    UserC is prompted to disconnect a session so that the third session can be created.

In this case, Remote Desktop Services does not protect the console sessions from being disconnected.

Resolution

After you install the following 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:

http://support.microsoft.com/contactus/?ws=supportNote 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 R2.

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 WindowsTo use one of the hotfixes in this package, you must create a registry key.

To have us create the registry key for you, go to the "Fix it for me" section. If you prefer to create the registry key yourself, go to the "Let me fix it myself" section.

Fix it for me



To create the registry key automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.




Notes

  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.

  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.


Then, go to the "Did this fix the problem?" section.



Let me fix it myself

To create the registry key yourself, follow these steps:

  1. Click Start start button , type regedit in the Search programs and files box, and then press ENTER.

    UAC 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.


Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.

  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.

Restart requirement

You must 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 R2 file information notes


  • 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 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very 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 x64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Termsrv.dll

6.1.7600.20621

707,584

19-Jan-2010

10:30

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Termsrv.dll

6.1.7600.20621

1,306,624

19-Jan-2010

09:02

IA-64

Status

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

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 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_301412784bde8dec790d6e856836c7bd_31bf3856ad364e35_6.1.7600.20621_none_a035e2bf674cedac.manifest

File version

Not applicable

File size

1,106

Date (UTC)

20-Jan-2010

Time (UTC)

01:29

Platform

Not applicable

File name

Amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20621_none_eb5ab26686e5ab1f.manifest

File version

Not applicable

File size

29,203

Date (UTC)

19-Jan-2010

Time (UTC)

13:41

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,689

Date (UTC)

20-Jan-2010

Time (UTC)

01:29

Platform

Not applicable

File name

Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20621_none_f5af5cb8bb466d1a.manifest

File version

Not applicable

File size

10,688

Date (UTC)

19-Jan-2010

Time (UTC)

13:27

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_4352441ccd91e9fac200b3878d693e1e_31bf3856ad364e35_6.1.7600.20621_none_452be2f1f4e28b42.manifest

File version

Not applicable

File size

1,104

Date (UTC)

20-Jan-2010

Time (UTC)

01:29

Platform

Not applicable

File name

Ia64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20621_none_8f3dbad8ce8642e5.manifest

File version

Not applicable

File size

29,201

Date (UTC)

19-Jan-2010

Time (UTC)

13:41

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,684

Date (UTC)

20-Jan-2010

Time (UTC)

01:29

Platform

Not applicable

File name

Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20621_none_f5af5cb8bb466d1a.manifest

File version

Not applicable

File size

10,688

Date (UTC)

19-Jan-2010

Time (UTC)

13:27

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×