Saturday, October 22, 2022

A shadowed Windows Server 2008 Terminal Services session is disconnected from a computer that is running Windows Server 2008 R2 SP1 or Windows 7 SP1 [MS]

Symptoms

Consider the following scenario:

  • You install the Terminal Services role on a computer that is running Windows Server 2008.

  • You start a Terminal Services session with the terminal server from a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).

  • You try to shadow another Terminal Services session in the Terminal Services session.

  • Your shadow request is accepted by the user account in the Terminal Services session that you want to shadow.

In this scenario, the remote control operation fails. Additionally, the shadowed Terminal Services session is disconnected, and the user account in the shadowed Terminal Services session receives one of the following error messages:

Error message 1

Your Remote Desktop session has ended. Your network administrator might have ended the connection. Try connecting again, or contact technical support for assistance

Error message 2

The remote session to the remote computer was ended by means of an administration tool. Your administrator might have ended your connection

Additionally, an event that resembles the following is added to the System log on the terminal server:

Cause

The issue occurs because one input buffer size is insufficient.

The RemoteFX feature is introduced in Service Pack 1 for Windows Server 2008 R2 and for Windows 7. This feature causes one input buffer that is used by Windows Server 2008 Terminal Server to be insufficient.

Resolution

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 website:

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, your computer must be running Windows Server 2008 Service Pack 2 (SP2).For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

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

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Server 2008

    SP2

    LDR

  • 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.xxxxxx 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 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated component. 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 name

File version

File size

Date

Time

Platform

Termsrv.dll

6.0.6002.22641

451,584

12-May-2011

15:12

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Termsrv.dll

6.0.6002.22641

550,400

12-May-2011

15:30

x64

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

File name

File version

File size

Date

Time

Platform

Termsrv.dll

6.0.6002.22641

1,055,744

12-May-2011

15:32

IA-64

Workaround

To work around the issue, uninstall Service Pack 1 on the computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1.

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

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

File name

X86_544a98c0ace4031aca4f3ae1a3f8a75e_31bf3856ad364e35_6.0.6002.22641_none_fee9fb278aa97bca.manifest

File version

Not applicable

File size

728

Date (UTC)

12-May-2011

Time (UTC)

17:59

Platform

Not applicable

File name

X86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22641_none_90e520456aa77ea3.manifest

File version

Not applicable

File size

40,075

Date (UTC)

12-May-2011

Time (UTC)

15:28

Platform

Not applicable

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

File name

Amd64_b279f9e6f661266910a7e638504127d4_31bf3856ad364e35_6.0.6002.22641_none_f4e74449648c4006.manifest

File version

Not applicable

File size

1,106

Date (UTC)

12-May-2011

Time (UTC)

17:59

Platform

Not applicable

File name

Amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22641_none_ed03bbc92304efd9.manifest

File version

Not applicable

File size

40,131

Date (UTC)

12-May-2011

Time (UTC)

15:45

Platform

Not applicable

File name

Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22641_none_f758661b5765b1d4.manifest

File version

Not applicable

File size

18,965

Date (UTC)

12-May-2011

Time (UTC)

15:17

Platform

Not applicable

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

File name

Ia64_4527a72a4e67a6011efc1c6b49105919_31bf3856ad364e35_6.0.6002.22641_none_aef1c164f9c9eec8.manifest

File version

Not applicable

File size

1,104

Date (UTC)

12-May-2011

Time (UTC)

17:59

Platform

Not applicable

File name

Ia64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22641_none_90e6c43b6aa5879f.manifest

File version

Not applicable

File size

40,102

Date (UTC)

12-May-2011

Time (UTC)

15:40

Platform

Not applicable

File name

Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22641_none_f758661b5765b1d4.manifest

File version

Not applicable

File size

18,965

Date (UTC)

12-May-2011

Time (UTC)

15:17

Platform

Not applicable

No comments:

Post a Comment

Search This Blog

August 11, 2020—KB4571709 (OS Build 17134.1667) - Microsoft Support [MS]

August 11, 2020—KB4571709 (OS Build 17134.1667) Windows 10, version 1803,...