With XenApp 6.0 and later, and XenDesktop 5.0 and later, non-Windows Receivers are unable to properly detect and obtain the Time Zone Name of the client though the Time Offset from UTC (which is UTC-05:00) is correct.
The mechanism selects the last Time Zone Name in the list of the detected Time Zone. So in some circumstances, it appears to work properly. This issue can become problematic for certain Java based applications that rely on the Time Zone Name. Most applications can detect and use the Time Zone information without an issue. If there is a policy to use the Time Zone information of the server, then this issue does not exist.
Citrix has created a client-side patch that resolves the problem. This fix will be created for each of the following non-windows platform in the upcoming releases.
The fix is included in the latest Citrix Receiver for iOS release (since version 5.7.2). Find it here.
The fix is included in the latest Citrix Receiver for Linux release (since version 13.0). Find it here.
The fix is included in the latest Citrix Receiver for Android release (since version 3.4). Find it here.
The fix is included in the latest Citrix Receiver for Mac release (since version 11.8). Find it here.
The cause of this issue is because of the removal of Citrix Time Zone hooking mechanism tzhook from Citrix XenApp and XenDesktop in compliance with the newer Windows operating systems standards.