I'm facing a frustrating issue with a user's device automatically setting the wrong time zone. This started after they moved within the same town and switched their internet from a cable provider to Starlink. Although I have an auto time zone setting configured for our organization (helpful for our many remote workers), their device is now incorrectly set to an African time zone instead of US Eastern Time.
We've been troubleshooting this problem with the VPN on and off. Interestingly, Google Maps correctly recognizes the user's location, while various geo IP locators identify the Starlink IPv6 address as being around Atlanta, GA. However, Microsoft Maps seems to still register the old African location, even after I changed the default location settings, rebooted, and cleared caches.
I also submitted the BSSID data from their router to Microsoft for database updates, but weeks later, nothing has changed. I've reached out to multiple geo IP sites to update the information linked to the user's IPv6 address, but I'm still stuck. I'd like to avoid making an exception in our configurations as that could lead to further complications when this user travels. Any suggestions for what I could do next to resolve this?
1 Answer
We had a similar issue with our team. We ended up enabling location services on the laptops and created a registry key to set the automatic time. However, we had to establish a secondary group for users who kept encountering time zone problems, allowing them to set it manually. It just wasn’t worth the hassle of wrong geo location data causing constant conflicts.
I’m thinking of doing the same! I’ve created a workflow in my RMM tool that monitors for System Event 35. When it detects that, it runs a script to change the timezone back to the correct one. This way, it only impacts those users who are having issues and doesn’t mess with others.