Microsoft KB Archive Search

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.

  1. Home
  2. The RemoteApp program is not terminated after the idle session time limit expires on a computer that is running Windows Server 2008

The RemoteApp program is not terminated after the idle session time limit expires on a computer that is running Windows Server 2008

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008.
  • You join the computer to a domain.
  • You install the Remote Desktop Services role on the computer.
  • You enable the following Group Policy settings in the domain:
    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\Set time limit for active but idle Remote Desktop Services sessions

    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\Terminate session when time limits are reached
  • You set the Idle session limit setting to a value that is greater than or equal to five minutes. The Idle session limit setting is in the Set time limit for active but idle Remote Desktop Services session Group Policy setting.
  • You apply the Group Policy settings to the computer.
  • You run a RemoteApp program to start a Remote Desktop Services session on the computer.
  • The session is idle for a time period that is longer than the idle session time limit.
  • You receive the following message in the Remote Desktop Services session after the session is idle for a time period that is longer than the idle session time limit:
    Session has been idle over its time limit. It will be disconnected in 2 minutes. Press any key now to continue session.
In this scenario, the RemoteApp program is not terminated after the session remains idle for an additional two minutes.

↑ Back to the top

Cause

This issue occurs because Remote Desktop Services incorrectly handles some automatically generated events and messages as user input. Therefore, Remote Desktop Services does not terminate the RemoteApp program.

Note These automatically generated events and messages are from the Remote Desktop Connection utility.

↑ 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 that is 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=support
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, the Remote Desktop Services role services 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

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.
    VersionProductSR_levelService branch
    6.0.600
    1.
    22xxx    		Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx    		Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008.
  • 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 very important 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
Termsrv.dll6.0.6001.22801451,58420-Nov-201022:13x86
Termsrv.dll6.0.6002.22515451,58429-Oct-201016:29x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.22801550,40020-Nov-201023:16x64
Termsrv.dll6.0.6002.22515550,40029-Oct-201016:30x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.0.6001.228011,056,76820-Nov-201022:55IA-64
Termsrv.dll6.0.6002.225151,055,74429-Oct-201016:00IA-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, click the following article number to view the article in the Microsoft Knowledge Base:
2287493 The RemoteApp program is not terminated after the idle session time limit expires on a computer that is running Windows Server 2008 R2
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 size32,333
Date (UTC)22-Nov-2010
Time (UTC)08:26
PlatformNot Applicable
File nameX86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22801_none_8f29ec276d60bc94.manifest
File versionNot Applicable
File size40,075
Date (UTC)20-Nov-2010
Time (UTC)22:26
PlatformNot Applicable
File nameX86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22515_none_91098f4b6a8b9305.manifest
File versionNot Applicable
File size40,075
Date (UTC)29-Oct-2010
Time (UTC)16:45
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22801_none_eb4887ab25be2dca.manifest
File versionNot Applicable
File size40,131
Date (UTC)20-Nov-2010
Time (UTC)23:32
PlatformNot Applicable
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22515_none_ed282acf22e9043b.manifest
File versionNot Applicable
File size40,131
Date (UTC)29-Oct-2010
Time (UTC)16:49
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size32,645
Date (UTC)22-Nov-2010
Time (UTC)08:26
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22801_none_f59d31fd5a1eefc5.manifest
File versionNot Applicable
File size18,965
Date (UTC)20-Nov-2010
Time (UTC)22:18
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22515_none_f77cd5215749c636.manifest
File versionNot Applicable
File size18,965
Date (UTC)29-Oct-2010
Time (UTC)16:32
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22801_none_8f2b901d6d5ec590.manifest
File versionNot Applicable
File size40,102
Date (UTC)20-Nov-2010
Time (UTC)23:07
PlatformNot Applicable
File nameIa64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22515_none_910b33416a899c01.manifest
File versionNot Applicable
File size40,102
Date (UTC)29-Oct-2010
Time (UTC)16:13
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size5,323
Date (UTC)22-Nov-2010
Time (UTC)08:26
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6001.22801_none_f59d31fd5a1eefc5.manifest
File versionNot Applicable
File size18,965
Date (UTC)20-Nov-2010
Time (UTC)22:18
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.0.6002.22515_none_f77cd5215749c636.manifest
File versionNot Applicable
File size18,965
Date (UTC)29-Oct-2010
Time (UTC)16:32
PlatformNot Applicable

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2381675
Revision : 1
Created on : 1/7/2017
Published on : 12/16/2010
Exists online : False
Views : 278