Sep 13 2021 05:11 PM
Anyone having issues with time settings in Teams running on a Windows 365 Cloud PC using anything other than the Microsoft Remote Desktop Application? From a Chromebook with the correct time zone set, the Cloud PC reverts to a GMT -12 setting every time I reconnect. I have tried setting the time zone via GPO and Intune, but nothing "sticks" (also have users with MAC clients experiencing the same issue).
Sep 14 2021 10:27 AM
Sep 22 2021 10:11 PM
@JimK1 I have the same problem. However, I only use the Remote Desktop. The location of the Windows 365 is Dublin and so the time zone is set GMT 00:00 but I am sitting in GMT 01:00 . When I manually change the time zone on the Windows 365 PC, it always overwrites it back to GMT 00:00. Microsoft support is not really responding to my probelm....
Sep 23 2021 09:09 AM
Oct 05 2021 06:52 PM
Oct 06 2021 09:39 AM
Oct 15 2021 04:14 AM
@JustinA1125 The time zone issue should be resolved with the latest version of the RDP client app for Mac devices. Latest version is 10.7.0 (1933). Please check and give us feedback. Thank you.
Mar 03 2022 10:10 AM
Mar 03 2022 10:16 AM
@JTurnCap15 - MAC devices seem to be good now but Android devices are still not working...
Mar 04 2022 11:48 PM
Mar 28 2022 05:25 PM
May 05 2022 08:30 PM
@Nirolf - I am running Mac client 10.7.6 (1972) and have this problem. The Windows 365 PC resets to PST everytime I connect and I want it to run in EST.
Jun 07 2022 02:29 AM
@texol Could you find any solution ?.. I have same issue with windows 365 and observed same with AWS workspace
Jun 07 2022 02:20 PM
@RajKanth, sadly, my solution is to use Chrome Remote Desktop. I lose sound and some screen resolution options, but it does not change the time when I connect, which is more important to me than what I give up.
Nov 09 2023 02:00 AM - edited Nov 09 2023 02:00 AM
Nov 09 2023 06:47 AM
Nov 09 2023 06:49 AM
Unfortunately for iOS or iPadOS there is no updated client yet
Nov 09 2023 07:02 AM
Nov 21 2023 08:24 AM
I raised a support case with Microsoft on this and thankfully a short time later the fix came out.
Sadly the new Windows App (TestFlight) has the exact same issue so the code base clearly branched from before the fix.