Exchange Server 2019 - How to use new Greenlandic Timezone (UTC-2)

Jesper Rex Andersen 0 Reputation points
2025-02-05T10:28:48.2666667+00:00

We are running Exchange Server 2019 patched to CU14 Nov24SUv2 on Windows Server 2019.

Windows Server has been updated with the patch for the new Greenlandic Timezone UTC-2
https://techcommunity.microsoft.com/blog/dstblog/greenland-2023-time-zone-update-now-available/3937743

But in Exchange Server OWA, it still says (UTC-3) Greenland

User's image

How do We get the new Greenlandic Timezone in Exchange Server 2019?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,433 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Alex Zhang-MSFT 4,580 Reputation points Microsoft Vendor
    2025-02-06T01:52:30.68+00:00

    Hello, @Jesper Rex Andersen,

    Welcome to the Microsoft Q&A platform!

    This issue stems from the fact that Exchange Server (including OWA) doesn’t automatically “pick up” changes made to the Windows time zone definitions. Although your Windows Server 2019 now knows about Greenland’s new offset (UTC‑2), Exchange has its own bundled and cached time zone data that was compiled into your CU (in your case, CU14) and isn’t updated simply by the underlying OS patch.

    In other words, Exchange uses its internal time zone “database” (hard‐coded in files and DLLs) to build the OWA time zone list. That data was set when your CU was released and does not automatically refresh when Microsoft updates the Windows time zones. Microsoft is aware of these kinds of discrepancies—when an OS update modifies a time zone (like Greenland from UTC‑3 to UTC‑2), Exchange’s own definitions remain unchanged until they are updated in a future CU.

    Below is what you can do to try to resolve your issue:

    Officially, Microsoft must ship an updated CU (or a hotfix) for Exchange 2019 that incorporates the new Greenland time zone definitions. In the meantime, you may want to check Microsoft’s release notes and announcements to see when a fix is expected.

    As a workaround, while not supported or recommended for production, some administrators have attempted to manually update the Exchange time zone definitions by modifying the XML/js files or registry settings that OWA uses. However, this is not documented or supported by Microsoft and may cause unforeseen issues.

    The recommended course of action is to monitor Microsoft’s Exchange updates and plan an upgrade (or apply a CU when available) that contains the updated time zone information.

    For information on Exchange updates, please refer to Updates for Exchange Server, Cumulative Updates for Exchange Server, Exchange Server 2016 CU, Cumulative Update Exchange 2016 | Microsoft Learn.

    Should you need more help on this, you can feel free to post back. 


    If the answer is helpful, please click on “Accept answer” as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.

    Thank you for your support and understanding.

    Best Wishes,

    Alex Zhang

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.