Background:

I am based in the UK and the company I work for bought HP t410 Smart Zero Clients to be used in a Windows Server R2 remote desktop environment as terminal services sessions. We out source our exchange services The company also owns Wyse terminals which the HP t410's are to replace and the employees can use the terminal services on their desktops and laptops. This issue I am experiencing is localised to the new HP T410 smart zero clients.

Problem:

When logged into the remote session the HP T410's clock shows the correct time however when loading outlook 2013 it shows the time as 1 hour behind both in mail and on the calendar. This is because Outlook isnt factoring in DLT (Day Light Saving Time).

I have spoken to HP directly and update the bios on the HP t410's and the problem still persisted.

I have gone through the options menu within outlook and tried fooling outlook with adding a second time zone and switching the times and then switching them back which works for that session, but as soon as the machine is restarted the settings go and then time stamp is again an hour behind.

I have checked with our exchange provider and went through several tests with them and it is not down to the exchange server.

The last test that I have done was to start a remote session to a colleagues machine through the HP t410 and outlook showed the correct time, I then started another remote session into one of our meeting rooms and outlook again showed the incorrect time, even though when logged directly into the meeting room machine the correct time was displayed. 

I'm not sure how to proceed from here as all the tests I have done show that the issue lies between the HPt410's and the servers that are running the terminal service sessions. I was wondering if anyone else has had this issue with a similar setup and can point me in the right direction.

All of accounts occur the same problem, right?  

Most of this case, it can occur if the following conditions are true:
1. You are in a region that does not follow daylight saving time (DST).
2. The server that is running Microsoft Exchange Server where the mailbox is hosted is located in a region that follows DST.

Verify your time zone is correct on RDS machine.

Set the time zone on the Exchange Server to a region that matches the Coordinated Universal Time (UTC) zone of the country where the server is located. Make sure that the UTC zone for that country does not follow DST.

Cheers,
Tony Chen
Forum Support
________________________________________
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact tnmff@microsoft.com.

Hi,

Just checking in to see if the information was helpful. Please let us know if you would like further assistance.

Cheers,
Tony Chen
Forum Support
________________________________________
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact tnmff@microsoft.com.

Hi,

I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.

Cheers,
Tony Chen
Forum Support
________________________________________
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact tnmff@microsoft.com.