VMware Horizon Community
Borat_Sagdiev
Enthusiast
Enthusiast

WYSE (V10L) Keeps Resetting Time

Hello all,

I have this nagging problem with one of my clients: On a WYSE terminal, mostly V10Ls, the time keeps shifting back to Central America from Central Time.  Here is the environment:

- View 4.6 broker, 4.6 agent, connecting to several types of endpoitns including the WYSE terminals.  We are in Central US Time and the WYSE terminals are set to Central US time. The user logs on, the time is set to Central America, not Central US. You change the time to Central US, log off and the next time, guess what? Central America.  Everyone uses linked clones via Composer 2.6. The base image is of course set to Central US time and it's only those sessions that are run on the WYSE terminals that experience this problem.  WIndows PC client users running View sessions do not have the problem and everyone uses the same base image.  Odd?

I'll open a case with WYSE, but in the meantime I'm just wondering if any of you have experienced this.  Thanks in advance!

Reply
0 Kudos
3 Replies
mpryor
Commander
Commander

What is the raw timezone ID set up in the Wyse client device? The View connection server will convert it to a Windows timezone using a mapping file, it's possible this map has an incorrect entry. You should be able to see the timezone information passed over in the agent logs on the VM, go to c:\docuemtns and settings\all users\application data\vmware\vdm\logs and open the latest debug log file, then find an entry that looks like this:

2011-04-01 11:14:32,795 DEBUG <MessageFrameWorkDispatch> [wssm] gotClientInfo ClientInfo =
Machine_Name = "mpryor-ubuvm"
Type = "Linux"
...
TZID = "Europe/London"
Windows_Timezone = "GMT Standard Time"
...

2011-04-01 11:14:32,795 TRACE <MessageFrameWorkDispatch> [wssm] Got Windows_Timezone from client in ClientInfo. timezone = GMT Standard Time

Reply
0 Kudos
Borat_Sagdiev
Enthusiast
Enthusiast

Mike, thank you for the response.  Unfortunately I was unable to locate any of the entries (less your custom names) in several debug files. The terminals themselves are set to Central US time zone, but the sessions keep getting pushed to Central America even though we set the Windows session to Central US as well.  Perhaps some config file is incorrectly set.  I am researching....

Reply
0 Kudos
mpryor
Commander
Commander

Re-reading my post, I'm not explicitly clear - I meant to say the _desktop_ VM, in case you interpretted VM as the connection server instead and were looking at those logs (which are in the same location)?

Reply
0 Kudos