Since the clock change on the 29th the RD iOS app is not redirecting the correct time on the server. I can see this was fixed over summer in the macOS RD app, but it’s still in an issue on iOS.
Hi,
I understand the issue is relating to the RD client not able to pick up the boundaries of daylight saving and standard time. You can check this in Command Prompt using the command 'w32tm /tz'.
Here is output taken while using the RD Client (10.5.0) on iOS 16.7.2. The time zone ID is unknown, the bias is incorrect, and the date boundaries are unspecified.
H:\>w32tm /tz
Time zone: Current:TIME_ZONE_ID_UNKNOWN Bias: -630min (UTC=LocalTime+Bias)
[Standard Name:"Cen. Australia Standard Time" Bias:0min Date:(unspecified)]
[Daylight Name:"Cen. Australia Daylight Time" Bias:0min Date:(unspecified)]
Following is output taken from the RDP client on a Windows local machine. All information is set correctly.
H:\>w32tm /tz
Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: -570min (UTC=LocalTime+Bias)
[Standard Name:"Cen. Australia Standard Time" Bias:0min Date:(M:4 D:1 DoW:0)]
[Daylight Name:"Cen. Australia Daylight Time" Bias:-60min Date:(M:10 D:1 DoW:0)]
Can this be corrected in the next RD Client release for iOS?