The logon and logoff scripts do not run in Windows Server 2008 R2 or Windows Server 2008 if you use the same user account to create another RDC session

Consider the following scenario:

• You install the Remote Desktop Services (RDC) server role on a computer that is running Windows Server 2008 R2, or you install Terminal Services role on a computer that is running Windows Server 2008.
• You disable the "Restrict each user to a single session" option on the computer.
• You configure some logon scripts or some logoff scripts to run when a user creates a session and logs on to the computer.
• You use a user account to create a RDC session to the computer. Then, you use the same user account to create another RDC session to the computer.

In this scenario, the logon scripts or the logoff scripts do not run in the second RDC session.

This problem occurs because of an issue in the Group Policy Client service.

The Group Policy Client service does not support multiple RDC sessions if the same user account is used. When you use the same user account to establish more than one RDC session, an incorrect session ID is assigned to the Gpscript.exe process for the sessions that are created after the first session. Therefore, the Gpscript.exe process cannot be used to run the logon scripts.

Note This issue also affects the logoff scripts.

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, you must be running Windows Server 2008 R2 or Windows Server 2008 on the computer.

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 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 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 x64-based versions of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

For all supported X86-based versions of Windows Server 2008, Service Pack 2

For all supported IA-64-based versions of Windows Server 2008 Service Pack 2

For all supported x64-based versions of Windows Server 2008 Service Pack 2

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:

Additional file information

Additional file information for Windows Server 2008 R2

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

Additional files for all supported IA-64-based versions of Windows Server 2008 R2