• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Any failures related to Hotkey UWP service? Click here for tips.
HP Recommended
HP t640 Thin Client (5RL91AV)
Linux

ThinPro 7.2 SP9. AVD client add-on v2202.02.07hp1a. T630 and T640 thin clients. Since upgrading to ThinPro 7.2  the users'  AVD desktop session has the incorrect time in its system clock.  The thin client OS is set for Eastern time and updates normally using time.windows.com time server. But when connected to an AVD desktop session the time is showing 4 hours ahead. Looking in the Windows time settings it actually indicates the correct time zone matching the thin client OS time. As a workaround, user is able to change the time zone in the Windows session, so they change it to any other time zone, then change it back to Eastern time and the time is displayed correctly. But that has to be done after each login. I would blame Microsoft on this, but from our network this problem is only occurring from AVD sessions running on ThinPro thin clients. PC's and laptops work normally. I have checked and tested the time zone setting provided in the AVD client settings, and it behaves the same whether our not you have the "use system time" checked. Also tried this on fresh image using SP6 version of ThinPro.  I tested with same results on the newer version client 2202.03.15 Could this be a problem with the AVD addon?

2 REPLIES 2
HP Recommended

@tkmat 

 

Clients should use time from main server. My old organization (I'm  retiree now) has thousands and thousands of different devices which all link to same NTP server to keep them in sync

 

Hope this makes sense.

 

Regards.

BH
***
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.




HP Recommended

I agree, but there are some changes anticipated with the domain servers so we went with the Microsoft time for now. Tested though, but doesn't make a difference. The thin clients are staying in sync but the problem is yhis Microsoft cloud app client isnt picking up on the thin client system time at all. Might be time to get Microsoft engaged. Yippee.  Again thanks!

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.