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

Article translations Article translations
Article ID: 2287493 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2.
  • You join the computer to a domain.
  • You install the Remote Desktop Services role services 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 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 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.

CAUSE

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

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

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:
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, you must be running Windows Server 2008 R2. Additionally, the Remote Desktop Services role services must be installed. 

Registry information

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

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 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 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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 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 x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Termsrv.dll6.1.7600.20757711,68017-Jul-201008:06x64

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
Collapse this tableExpand this table
File nameAmd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20757_none_eb40464486f89423.manifest
File versionNot Applicable
File size29,203
Date (UTC)17-Jul-2010
Time (UTC)08:52
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size24,725
Date (UTC)17-Jul-2010
Time (UTC)14:45
PlatformNot Applicable
File nameWow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.20757_none_f594f096bb59561e.manifest
File versionNot Applicable
File size10,688
Date (UTC)17-Jul-2010
Time (UTC)07:59
PlatformNot Applicable

Properties

Article ID: 2287493 - Last Review: August 12, 2010 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2287493

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com