Microsoft has discovered once again that few things strike fear into the heart of a software engineer quite like a government deciding to fiddle with the clocks.
Parts of Canada stopped observing seasonal clock changes on November 1, leaving affected areas of British Columbia, Alberta, and Manitoba permanently on UTC-07:00, UTC-06:00 and UTC-05:00 respectively. Unfortunately, Microsoft’s sprawling software empire hasn’t entirely caught up.
The company has confirmed problems across a chunk of its software estate, leaving some customers facing incorrect times, broken schedules and a collection of workarounds while Redmond catches up.
Outlook users have been left with the most homework. Switching to the new Canadian time zones won’t automatically update existing calendar entries, meaning that meetings scheduled after November 1 are potentially an hour out of whack.
Microsoft advises users to change their Outlook calendar time zone, then update upcoming events and meetings to use it. For meetings involving other people, only the organizer can make the change.
Posted smugly from Arizona, where Sunday lasted 24 hours.
Microsoft releases patches every month, and often patches for the patches, and still they can’t have their software ready for a change they know is coming.
Posted smugly from Arizona, where Sunday lasted 24 hours.
Yeah, but…aren’t you guys the state that partly does and partly doesn’t do daylight savings time, though?
searches
Sounds like it.
https://www.timeanddate.com/time/zone/usa/arizona
How Many AZ Time Zones Are There?
Most of Arizona observes Mountain Standard Time (MST) all year. However, because the Navajo Nation observes Daylight Saving Time (DST), the corresponding DST designation, Mountain Daylight Time (MDT) is also listed here.
It’s actually a bit more absurd than that. The Hopi reservation, which is completely surrounded by the Navajo Nation, does not observe DST. But the rest of the state is on MST year-round.
Yup. Spend a good 15 minutes figuring out what the hell was going on with my system clock and why no amount of syncing would fix it. Had to manually change the timezone.
