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.

You are not redirected to the previously-disconnected terminal server session through the TS Session Broker service in a Windows Server 2008-based farm in TS Session Broker


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You build a Windows Server 2008-based farm in Terminal Services Session Broker (TS Session Broker). In this farm, some terminal servers that are running Windows Server 2008 are joined.
  • You clear the following options on the terminal servers that are running Windows Server 2008:
    • Use IP address redirection (recommended)
    • Participate in Session Broker Load-Balancing
  • You use a user account to create a terminal server session through the TS Session Broker service to these terminal servers. This user account receives a "start a program on connection" policy that starts a program when a connection is created.
  • You create a terminal server session to a terminal server by using this user account, and then you disconnect the session.
  • You create a terminal server session to another terminal server by using the same user account.
In this scenario, you are not redirected to the previously-disconnected terminal server session. Instead, a new terminal server session is created.

↑ Back to the top


Cause

This issue occurs because the TS Session Broker service does not detect a disconnected terminal server session on another terminal server for this user. Therefore, the Session Broker cookie cannot be sent. This behavior causes a new terminal server session to be created. However, the expected behavior is that the user is redirected to the previously-disconnected terminal server session.

↑ Back to the top


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 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, your computer must be running Windows Server 2008 or Windows Server 2008 Service Pack 2 (SP2). Additionally, TS Session Broker role service must be installed.

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

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 English (United States) 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.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 and MANIFEST files, and the associated security catalog (.cat) files, are critical to 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 nameFile versionFile sizeDateTimePlatform
Sdclient.dll6.0.6001.22565157,18417-Nov-200912:26x86
Tssdjet.dll6.0.6001.2256538,40017-Nov-200912:26x86
Sdclient.dll6.0.6002.22269157,18417-Nov-200912:29x86
Tssdjet.dll6.0.6002.2226938,40017-Nov-200912:30x86
Termsrv.dll6.0.6001.22565449,53617-Nov-200912:26x86
Termsrv.dll6.0.6002.22269449,53617-Nov-200912:30x86
For all supported x64-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Sdclient.dll6.0.6001.22565204,28817-Nov-200912:49x64
Tssdjet.dll6.0.6001.2256552,22417-Nov-200912:49x64
Sdclient.dll6.0.6002.22269204,28817-Nov-200912:23x64
Tssdjet.dll6.0.6002.2226952,22417-Nov-200912:24x64
Termsrv.dll6.0.6001.22565548,35217-Nov-200912:49x64
Termsrv.dll6.0.6002.22269548,35217-Nov-200912:23x64
For all supported IA-64-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.225651,051,13617-Nov-200912:31IA-64
Termsrv.dll6.0.6002.222691,051,13617-Nov-200912:10IA-64

↑ Back to the top


Workaround

Workaround for Windows Server 2008

To work around the issue, use one of the following methods:
  • Use the TS RemoteAPP program in the terminal server sessions.
  • Change the user account properties to configure the initial program.
  • Configure the initial program setting on the Remote Desktop Connection client (mstsc.exe).

↑ 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
For more information about the Windows Server 2008-based TS Session Broker, visit the following Microsoft Web site:

Additional file information

Additional file information for Windows Server 2008

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

File nameFile versionFile sizeDateTimePlatform
X86_0938b0fb44e98b4550734ac34180a2a3_31bf3856ad364e35_6.0.6002.22269_none_597ab2373d95b4e9.manifestNot Applicable72818-Nov-200905:58Not Applicable
X86_0d4ecd9a8bb51462ff2b17819a6cc6a0_31bf3856ad364e35_6.0.6001.22565_none_b8df48a81a6a5db4.manifestNot Applicable72818-Nov-200905:58Not Applicable
X86_31f91d89b3f409df77fcd0dd4c1b9897_31bf3856ad364e35_6.0.6001.22565_none_1a416e5e8e27cd85.manifestNot Applicable72818-Nov-200905:58Not Applicable
X86_7af32422fcf0fcb9051d0df4629b17ff_31bf3856ad364e35_6.0.6002.22269_none_d5856f3983456dad.manifestNot Applicable72818-Nov-200905:58Not Applicable
X86_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.0.6001.22565_none_03b267b49270d71d.manifestNot Applicable44,54017-Nov-200915:39Not Applicable
X86_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.0.6002.22269_none_059cdac48f93919d.manifestNot Applicable44,54017-Nov-200915:57Not Applicable
X86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22565_none_8eed08156d8dd221.manifestNot Applicable40,07517-Nov-200915:38Not Applicable
X86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22269_none_90d77b256ab08ca1.manifestNot Applicable40,07517-Nov-200915:56Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Amd64_134e08eabdf67f5a7c82b6f01f5ec613_31bf3856ad364e35_6.0.6001.22565_none_8565aaa96dcc65aa.manifestNot Applicable1,10618-Nov-200905:58Not Applicable
Amd64_59e8c8bbcf0878f3e639692b38e7e0c7_31bf3856ad364e35_6.0.6001.22565_none_255fa43fb4b7cb3d.manifestNot Applicable73218-Nov-200905:58Not Applicable
Amd64_dafc7698fe8c923fbe8395162dd6407e_31bf3856ad364e35_6.0.6002.22269_none_47b9d57030c7a7a7.manifestNot Applicable73218-Nov-200905:58Not Applicable
Amd64_fefd34f9654bf14460bd304e060b234b_31bf3856ad364e35_6.0.6002.22269_none_aa23ae647f9b943e.manifestNot Applicable1,10618-Nov-200905:58Not Applicable
Amd64_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.0.6001.22565_none_5fd103384ace4853.manifestNot Applicable44,61217-Nov-200915:01Not Applicable
Amd64_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.0.6002.22269_none_61bb764847f102d3.manifestNot Applicable44,61217-Nov-200914:18Not Applicable
Amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22565_none_eb0ba39925eb4357.manifestNot Applicable40,13117-Nov-200915:00Not Applicable
Amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22269_none_ecf616a9230dfdd7.manifestNot Applicable40,13117-Nov-200914:17Not Applicable
Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22565_none_f5604deb5a4c0552.manifestNot Applicable18,96517-Nov-200915:31Not Applicable
Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22269_none_f74ac0fb576ebfd2.manifestNot Applicable18,96517-Nov-200915:46Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Ia64_1561deca437c35a36f5cc444935a217d_31bf3856ad364e35_6.0.6001.22565_none_2fef994e7af3b1b8.manifestNot Applicable1,10418-Nov-200905:58Not Applicable
Ia64_bbcf481220899faebe1dd90e4d0381c0_31bf3856ad364e35_6.0.6002.22269_none_175e7aff7626e251.manifestNot Applicable1,10418-Nov-200905:58Not Applicable
Ia64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22565_none_8eeeac0b6d8bdb1d.manifestNot Applicable40,10217-Nov-200914:06Not Applicable
Ia64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22269_none_90d91f1b6aae959d.manifestNot Applicable40,10217-Nov-200918:30Not Applicable
Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22565_none_f5604deb5a4c0552.manifestNot Applicable18,96517-Nov-200915:31Not Applicable
Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22269_none_f74ac0fb576ebfd2.manifestNot Applicable18,96517-Nov-200915:46Not Applicable

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, KB977541

↑ Back to the top

Article Info
Article ID : 977541
Revision : 1
Created on : 12/16/2009
Published on : 12/16/2009
Exists online : False
Views : 224