On 2026-09-24 06:48, james.epp--- via tz wrote:
Hi, folks
First time IANA list user. Apologies if I get the netiquette wrong (gentle
corrections welcome).
I assume there are employees of Microsoft on the mailing list, who are the
audience of my message.
I'm not placing fault with Microsoft as the MB government didn't provide ample
notice that this change would take effect for 2026-11-01, but I'm wondering if
someone from Microsoft come indicate how long of a wait there'll be until we
have interim guidance from them on their timezone blog
(https://techcommunity.microsoft.com/category/windows/blog/dstblog)?
For BC from Mar it took 5 months for guidance in Aug, update in Sep;
for AB from Jun, 2 months for guidance, update for recent W11 24H2-26H2 in Sep
Tue patch slot D, 2 weeks after slot B Patch Tue, other Windows on Oct slot B
Patch Tue;
MB still has not made an official proclamation with details, so nothing is
offical, and assumptions may be wrong, with some areas linked to ON;
ON is waiting for QC and NY: what happens if QC decides, and NY like DC is still
undecided?
Not hearing much from our our Atlantic Maritime folks on A[DS]T and those 30
minutes later on the Rock; not sure how much interaction with NE states, or
coordination required?
The feds have woken up and noticed that BC and AB have stopped switching in the
table on page:
https://nrc.canada.ca/en/node/1325
but the maps and text have not yet been updated since 2020, and no mention of
the change (or lack thereof in November) nor zone or naming.
Ironic comment on that page:
"A major change in official time practice will be given a new serial number and
documented here."
for which we are still waiting, and they too may also be waiting for MB to
decide, before updating the maps, text, and practices, as they probably would
not to waste money updating serial numbers too often or too many times. ;^>
[OTOH 7 years for the feds to produce a document update has been noted!]
Also .MA in late Jun announced changing back to UTC in Sep, nearly 3 months
notice, interim guidance also came late Aug, 3 weeks before the change, with Sep
Patch Tue updates, less than 2 weeks before the change.
It's unreasonable to expect a full timezone update to be in place for the
October Patch Tuesday LCU but some kind of interim guidance would be welcomed.
From my look through the available timezones on my Windows machine, it appears "SA Pacific
Standard Time" or "Eastern Standard Time (Mexico)" are the best (least worst?)
options for an interim timezone because they (A) are permanent UTC-5 and (B) will be easy to detect
and set to Manitoba Time (MBT) when that update finally arrives (we don't have users permanently in
those regions). However, short of guidance from MSFT, I'm hesitant to commit to any path today.
Because most other Microsoft services are web-based or entirely in the web
browser these days, I'd assume Windows timezone is the main concern and
customers don't need to take specific action for MS365/Azure/etc services. That
said, I was looking at (new) Outlook and Outlook on the web yesterday and the
timezone configuration for calendaring within Outlook don't honor system time,
but instead are saved/stored in the cloud service, so this is something I need
Microsoft guidance on.
Thanks in advance!
You could try commenting on the latest .CA guidance in the blog, but you will
probably get non-committal responses until MB proclaims officially, and perhaps
also after.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
