We have several thin clients that access 2 servers via RDP. Our server in located in Mountain Time Zone and changed the time as it should. But when someone on a thin client accesses one of these servers with a thin client the time does not adjust. I tried setting it in the configuration on the thin client. Looks ok until I log out and back in and it reverts back to incorrect time. What controls the thin client actually getting the correct time from the server? The branch in question is in another time zone also, to make it more interesting.
Remote AccessWindows Server 2008
Last Comment
bankwest
8/22/2022 - Mon
David Johnson, CD
What time is shown on the thin client when it starts up? the local time? The Server's time?
What is the TZ setting for the thin client? (local time) or mountain time?
The timezone settings on the client are most important. Are they using remote desktop to connect to the server?
bankwest
ASKER
The time zone on the thin client says Mountain Time on the one I am testing, with the Adjust for Daylight Savings checked. When I start up, (for example) in the lower right of the screen it says 10:15 a.m. (should read 11:15 a.m.) The server says 11:15 a.m.
If I go into configuration, Control Panel, Date and Time, it shows the correct time there as 11:15 a.m. If I go back to the lower right time shown as 10:15, and click on it, I can get a window that says change date and time. I correct the time here to 11:15 and apply. After I log out and back in, it reverts back to the 10:15.
bankwest
ASKER
Forgot to answer this part for you....Yes, they are connecting thru RDP.
What is the TZ setting for the thin client? (local time) or mountain time?
The timezone settings on the client are most important. Are they using remote desktop to connect to the server?