Today we are re-releasing the November 2024 SUs for Exchange Server. The original release of these SUs (released on 11/12/2024) introduced an issue with Exchange Server transport rules stopping after...
Updated Jan 28, 2025
Version 11.0
Blog Post
Hi Nino_Bilic
We plan to rollout v2 in the next days. We have some Exchange environments still with Exchange 2016 and some others with Exchange 2019. I´ve just installed v2 on the 2016 nodes in our test environment, without any issues.
But running the fix IANA timezone script tells me there are no duplicates. When I search the xml files manually I can confirm that (also before running the fix script - and of course after applying the SU).
Does the timezone issue only apply to Exchange 2019?
Or does it only occur in special circumstances?
These 2016 nodes already had v1 installed, have current Windows Updates (from Nov patchday), and both the OS and Exchange are installed in German.
I will apply in 2019 test environment later that day and will update if the the timezone issue hits these installations.
Thanks and best regards,
Stefan
ah sorry, I missed that there´s a typo in the fix script.
There was:
$xPathFilter = "//Map[@IANA='Asia/Bihkek' and win='Central Asia Standard Time']"
with Bihkek wissing an 's' -> Bishkek.
With the correct line I can find the duplicate both manually and with the script.
- LukasSMSFT
Microsoft
This is caused by the automatic translation of the KB (we're working on fixing this translation issue). Make sure to use the en-us version of the KB: Time zone exception occurs after installing Exchange Server November 2024 SU (Version 1 or Version 2) - Microsoft Support
You likely know that already, but again: You guys reeeealy need to put some more effort in your QA. Currently feels like everything you publish is buggy :/
But thanks for the clarification.
