Recently eGroup worked on a project for a large software company that involved creating a XENAPP 6 Farm for several hundred users, including many located in the UK, the Netherlands, and also in Australia. A core requirement of this install was to enable timezone, currency, and date format localization for CRM and Sales Management software utilized by those remote users.
XENAPP 6 requires Windows 2008 Server R2 64-bit to run and many of the policies available through the Citrix Delivery Console require settings in the GPMC. Because the latest version of XENAPP relies heavily on Windows 2008 Server Roles and the client was not running a full 2008 AD many of these policies were not available on their AD server.
One of the desired policy settings, "use local time of client", has the following stipulation as noted in the policy editor: "For this setting to be enforced, enable the “Allow time zone redirection” setting in the Remote Desktop Services node of the Group Policy Management Console." Because the Remote Desktop Services node is not available in 2003 AD installations we had to make a registry change on the local XENAPP Servers. After trying several permutations with the help of the client’s super sharp systems admin lead the following change was discovered as the successful registry entry:
[HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services]
"fEnableTimeZoneRedirection"=dword:00000001
This setting is important because the timezone settings are not available to users without local administrative access. To allow users to select their currency, date format, and other application localization settings the "Regional Settings" control was published as an application using the following command line setting:
control C:WindowsSystem32intl.cpl
Note that environments without some type of roaming or hybrid profiles will need this control panel published separately for every server in the farm as the settings will not follow users.

We recently came across the issue on XenApp6 where the ‘use local client time’ policy wasn’t applying. AD GPO worked for the host OS, but not within published apps.
We managed to discover that the issue could be resolved by assigning the ‘use local client time’ policy through AMC / Delivery Service Console, not just a client policy.