Symptoms

Consider the following scenario:

  • You install the Remote Desktop Session Host role service on a computer that is running Windows Server 2008 R2.

  • You enable and then apply the Configure keep-alive connection interval Group Policy setting in the following path in a Group Policy Object (GPO):

    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Configure keep-alive connection interval

  • You create a Remote Desktop Services session to the Remote Desktop Session Host server from a client computer.

In this scenario, the Remote Desktop Services sessions are not kept alive as expected. This behavior may cause the Remote Desktop Services sessions to be disconnected.

Cause

This issue occurs because the Remote Desktop Services service does not apply the keep-alive setting successfully in some specific situations. This behavior can be triggered by a Group Policy refresh on the Remote Desktop Services session host.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, you must be running one of the following operating system:

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply 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 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

File name

File version

File size

Date

Time

Platform

Agp440.sys

6.1.7600.16385

61,008

14-Jul-2009

01:52

x64

Isapnp.sys

6.1.7600.16385

20,544

14-Jul-2009

01:48

x64

Msisadrv.sys

6.1.7600.16385

15,424

14-Jul-2009

01:48

x64

Mssmbios.sys

6.1.7600.16385

32,320

14-Jul-2009

01:48

x64

Nv_agp.sys

6.1.7600.16385

122,960

14-Jul-2009

01:48

x64

Pci.sys

6.1.7601.21866

185,200

24-Nov-2011

07:22

x64

Streamci.dll

6.1.7600.16385

24,144

14-Jul-2009

01:45

x64

Swenum.sys

6.1.7600.16385

12,496

14-Jul-2009

01:45

x64

Termdd.sys

6.1.7601.21866

63,344

24-Nov-2011

07:22

x64

Uliagpkx.sys

6.1.7600.16385

64,592

14-Jul-2009

01:45

x64

Vdrvroot.sys

6.1.7600.16385

36,432

14-Jul-2009

01:45

x64

Volmgr.sys

6.1.7601.21866

70,512

24-Nov-2011

07:22

x64

Termsrv.dll

6.1.7601.21866

680,960

24-Nov-2011

07:12

x64

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_ec3962d4084d062b03c9f2adbe003fb1_31bf3856ad364e35_6.1.7601.21866_none_12f5a5b0e4d6c16a.manifest

File version

Not applicable

File size

1,106

Date (UTC)

24-Nov-2011

Time (UTC)

12:28

Platform

Not applicable

File name

Amd64_machine.inf_31bf3856ad364e35_6.1.7601.21866_none_188e8439ee94bc36.manifest

File version

Not applicable

File size

7,894

Date (UTC)

24-Nov-2011

Time (UTC)

13:41

Platform

Not applicable

File name

Amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.21866_none_ed1ad8c68427fa1e.manifest

File version

Not applicable

File size

29,749

Date (UTC)

24-Nov-2011

Time (UTC)

08:02

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,533

Date (UTC)

24-Nov-2011

Time (UTC)

12:28

Platform

Not applicable

File name

Wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.21866_none_f76f8318b888bc19.manifest

File version

Not applicable

File size

11,234

Date (UTC)

24-Nov-2011

Time (UTC)

06:51

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?

Any additional feedback? (Optional)

Thank you for your feedback!

×