Unknown time zone information in a remote desktop session when you try to query the time zone information from a Windows 7 SP1-based client computer to a Windows Server 2008 R2-based RDS server

Consider the following scenario:

• You have a Windows Server 2008 R2 Service Pack 1 (SP1)-based Remote Desktop Services (RDS) server.
• The Time Zone Redirection Group Policy setting is enabled on the server.
• On a Windows 7 SP1-based client computer that is running a different-language version of Windows than the server, you use a remote desktop connection to connect the client computer to the server.
• You try to query the time zone information by using the TimeDate.cpl Control Panel item in the remote desktop session.

In this scenario, the correct date and time are displayed in the remote desktop session. However, the Control Panel item cannot retrieve the client session's time zone information. Therefore, the time zone information is set to "unknown" in the remote desktop session. Additionally, the applications (for example, Microsoft Dynamics NAV or an application that is built based on the Java rt.jar source) that rely on the GetDynamicTimeZoneInformation API stop working.

This issue occurs because the GetDynamicTimeZoneInformation API does not redirect time zone information. In a remote desktop session, when time zone information is requested to be redirected, the system calls the older GetTimeZoneInformation API. The GetDynamicTimeZoneInformation API cannot return the time zone information in the remote desktop session. Therefore, the applications that use the GetDynamicTimeZoneInformation API may fail.

Note The GetDynamicTimeZoneInformation API is introduced in Windows Vista. It is available in Windows Vista, Windows Server 2008, or a later version of Windows.

For more information about the GetDynamicTimeZoneInformation API, go to the following Microsoft website:For more information about the GetTimeZoneInformation API, go to the following Microsoft website:

Hotfix information

To resolve this issue, install this hotfix on the Windows 7 SP1-based client computer and the Windows Server 2008 R2-based server.

Note If you have update 2592687 installed on the Windows 7 SP1-based client computer, you do not have to install this hotfix on the client computer. For more information about update 2592687, click the following article number to view the article in the Microsoft Knowledge Base:
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 website: 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 7 SP1 or Windows Server 2008 R2 SP1.

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

Registry information

To apply this hotfix, 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 7 and 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:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.1.760 1.22xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

• 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 7 and 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 x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

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