You install the Remote Desktop Session Host role service on a computer that is running Windows Server 2008 R2.
You delete the default Remote Desktop Protocol (RDP) listener (RDP-Tcp) on the computer.
You create some new customized RDP listeners on the computer.
You try to set the LogonTimeout setting for a specific listener.
In this scenario, you cannot set the LogonTimeout setting for the specific listener. The LogonTimeout registry entry is hard-coded at the location of the default RDP listener and it applies to all RDP listeners on the computer.
This issue occurs because there is no location for the LogonTimeout registry entry to be stored when the default listener is removed.
Note The LogonTimeout registry entry is a subkey of the default RDP listener's registry entry.
To resolve this issue, install this hotfix on the affected Windows Server 2008 R2-based computer.
After you install this hotfix, the Winlogon.exe process first tries to locate the "LogonTimeout" registry subkey under the following location:
When the "LogonTimeout" registry subkey exists in either of these two locations, the Winlogon.exe process will read its value, and then apply the value to all the RDP connections.
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.
To apply this hotfix, you must be running one of the following operating systems:
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, the Remote Desktop Session Host role service must be installed.
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
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 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.
6.1.760 0. 21xxx
Windows Server 2008 R2
6.1.760 1. 21xxx
Windows Server 2008 R2
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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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
The LogonTimeout registry entry is in the following location: