So there are no Terminal Server policies overridding your CMC settings? Also, might look at CTX303498. -Mike Original Message: ----------------- From: Jeremy Thomas jeremy.thomas@xxxxxxxxx Date: Thu, 12 Aug 2004 22:28:32 +0200 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Time zone issue No - not used policies. Came accross them when researching the dark art of Citrix Timezone interpretation. IIRC, this is a new FR3 feature, but I'd have to check on that to be sure. What I was able to determine is that the Citrix server seems to want an EXACT match on the client timezone, so if it's one character out, it takes the shift from GMT and applies the first timezone with that shift alphabetically. And there's a good chance that it does not have a daylight saving setting in it. This was a *$#@ to get right on our Wyse LE1200s - the original firmware only allowed you to specify the shift and a date when daylight saving kicked in and out. That wasn't good enough, and it took a new firmware version from Wyse to allow us to have the right string on the client. Possible workarounds were to use TZEDIT to edit the possible timezones on the servers - you could fox it that way if you have limited timezones, or use a 3rd party tool - I think that AppServe has a feature in that works. IIRC, you can do it through scripting as well but it involves loading up a registry key in quite a messy way. We didn't need to go down either of these routes, or the CMC route - barking at Wyse eventually got us our preferred solution. Good luck - that's a summary of about 3 weeks work. I seem to remember that Tokeshi (?) was the most helpful internet resource in resolving this. _____ From: Rob Slayden [mailto:rslayden@xxxxxxxxxxxxx] Sent: Thursday, August 12, 2004 9:27 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Time zone issue Jeremy, Have you used the CMC policies successfully? We use Wyse Winterms (3350, 3360, 3125) and we implemented a policy to ignore the ICA client time zone for users in the Pacific time zone region and it does not seem to work. The only property is DO NOT USE LOCAL TIME OF ICA CLIENTS; rule is enabled, tried a global group membership and individual user membership but both fail. I've also tested across 3 different ICA clients (6.0, 7.1, 8.0) and two different platforms; PC and Wyse Winterm 3360, and it defaults to the local ICA client time zone. Anyone used this policy property with any success or am I wasting my time? Thanks! rob 24 Hour Fitness _____ From: Jeremy Thomas [mailto:jeremy.thomas@xxxxxxxxx] Sent: Thursday, August 12, 2004 7:36 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Time zone issue Try setting up a policy through CMC and see if the timezone settings make any difference. Have your local PCs got the correct timezones? Are the server and PCs using the same language? You may have a problem estimating the timezone correctly if you have say a polish XP install connecting to a US language server. Have the PCs got the same list of possible timezones as the servers? See language. Is Daylight Saving turned off on either the client of server? Is the problem consistant through timezones? Like do some work and some not? _____ From: Jeff Matheis [mailto:jmathei@xxxxxxxxxxx] Sent: Thursday, August 12, 2004 4:21 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Time zone issue This happens on both Wyse devices and pc's. The pc's are running Citrix ICA client 8.0 It picks up the time zone and the time it just doesn't recognize the check box for Daylight Savings on the client. Thanks Jeff Matheis Kimball International, Inc. 812-482-8302 jmathei@xxxxxxxxxxx -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeremy Thomas Sent: Thursday, August 12, 2004 9:15 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Time zone issue The timezone should be held on the client, and this is "interpreted" by Citrix (though you can turn this off through a Citrix policy). I had an issue with certain Wyse thin clients whereby it could hold a shift from GMT (like GMT-5), but it did not match up exactly to the server timezones, so the server just assumed it was the first timezone alphabetically. So instead of "US Central Time" (with daylight savings), we got "Central America Time" (without daylight savings). The fix was a firmware upgrade from Wyse. So the first question would be what clients are you using and do they display the correct timezone? I don't think it will be a profile or a server issue. Regards, Jez. _____ From: Jeff Matheis [mailto:jmathei@xxxxxxxxxxx] Sent: Thursday, August 12, 2004 3:43 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Time zone issue We are running W2K3 with Citrix XP FR3 and we are using flex profiles. When users login from a time zone that is different then what the servers are using the clients time is adjusting but its not picking up whether or not the "Automatically Adjust for Daylight Savings" box is checked or not. Citrix support is working on it but if you are familiar with Citrix support you know I have a better chance of someone on this list fixing it before Citrix does. Any help would be appreciated. Thanks Jeff Matheis Kimball International, Inc. 812-482-8302 jmathei@xxxxxxxxxxx -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ******************************************************** This Weeks Sponsor RTO Software Do you know which applications are abusing your CPU and memory? Would you like to learn? -- Free for a limited time! Get the RTO Performance Analyzer to quickly learn the applications, users, and time of day possible problems exist. http://www.rtosoft.com/enter.asp?id20 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm