- This topic is empty.
-
Posts
-
Having an issue since DST change Nov 1st.
Current settings wnos.ini-TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=110107 End=030207 TimeZoneName=”Central Standard Time” DayLightName=”Central Daylight Time”
Problem- Time is off at the actual unit but the time within citrix outlook sessions is correct. If I change the start and end parameters I can can get the device time to be correct but then the calendars are off (ahead) one hour in citrix outlook!
I know I have dealt wit this issue before but don’t remember what was done to get both the time shown at the device and the outlook current time settings in sync. I thought it was something like set the start parameter to be one day before DST actually starts but I am grasping here.
I have tried turning the dst setting off as we are actually out of dst but getting nowhere fast.
Any suggestions welcome…
this is the original version of this parameter before all the DST changes…
TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=030107 End=110107 TimeZoneName=”Central Standard Time” DayLightName=”Central Daylight Time”
these are the current settings in the wnos.ini… whcih is a convuluted mixture of start and end from the original
TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=110107 End=030207 TimeZoneName=”Central Standard Time” DayLightName=”Central Daylight Time”
But why do you change start and end time? You should leave it as it was.
CG
But these 1200LE’s have had an issue from the start with this dst issue. The only way I was able to get the on screen device time AND the outlook calaendar time to be accurate was to make the strat/end string as shown.
TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=030207 End=030307 TimeZoneName=”Central Standard Time” DayLightName=”Central Daylight Time”
Yes I know it doesn’t make sense to have to change it at all be we have always had to mess with it. The settings shown work but I would like to know why!
thanks in adance for your time.
- You must be logged in to reply to this topic.