What’s Up With Windows Automatic Time Zone Changes in Brisbane?

You're right about the Wi-Fi factor. In my experience, Microsoft’s geolocation can sometimes get really muddled if you're on a shared network or if the ISP has issues. When I’m in Sydney, my laptop often thinks I’m in Adelaide too, thanks to faulty IP-based location data. It’s especially bad if the ISP is using CGNAT and hasn’t updated their systems. That might explain why your client is getting these weird changes too.

That sounds like a classic case of location confusion! If users are being identified as coming from a different city, it might be due to local networks acting up or sending incorrect signals. You could send Microsoft a list of those SSIDs your script captured to confirm they're actually in Brisbane. They might not have the best responsiveness, but it’s worth a shot.

I hear you! I’ve had to manually set time zones for my setups in the past too. Microsoft’s automatic detection seems to have a blind spot for locations other than major cities like Sydney. Honestly, if it keeps malfunctioning, maybe reverting to user-managed time zones temporarily isn’t the worst idea until they sort it out.

We've dealt with similar issues in the past, especially with Zscaler in place. When you’re behind a proxy, the system sometimes defaults to the wrong time zone based on the proxy’s location. It's tough since your client wants automation. You could test disabling Wi-Fi briefly to see if it fixes the issue—might eliminate that source.

Interesting approach with the script! I do think it could help reveal what's going wrong. As for your concerns about needing automatic updates, have you considered logging every time a change occurs and sending that data to Microsoft? They might be more inclined to fix the database issue with enough evidence.