Bug in Office 2016-2019 Adm files, Setting jumps back to three days in stead of 1 week/2weeks

Jacco Dominicus 21 Reputation points


I have got a strange thing.
Created a GPO with outlook settings, so that it should use cached mode , and cache 2 weeks. When i close the GPO i check the right pane in Group policy editor and see that it states: Select Cached Exchange Mode sync settings for profiles Two Weeks.
But when i run RSOP on the client , i see that the sync mode is Three Days ?
When i edit the created GPO, and go to the specified setting, i see that it is Three Days, but in the right pane it stated Two weeks.
Is there a bug in the ADM files ( already updated to version 5146 )


Outlook Management
Outlook Management
Outlook: A family of Microsoft email and calendar products.Management: The act or process of organizing, handling, directing or controlling something.
4,714 questions
{count} votes

Accepted answer
  1. JeffYang-MSFT 6,231 Reputation points

    Hi @Jacco Dominicus

    Welcome and thanks for your feedback.

    I did some research about the situation you mentioned and it seems that Microsoft already has a KB for it, in which it says this only affects the way that the setting is displayed in GPMC. Actually, the Cached Exchange Mode Sync Setting policy works correctly as it's configured.

    It also provides an workaround that you could configure the cache mode setting by using the SyncWindowSetting and the SyncWindowSettingDays registry keys.

    For more specific information, please check: Outlook Cached Exchange Mode Sync Setting is displayed incorrectly in GPMC.

    Hope this can be helpful.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Jacco Dominicus 21 Reputation points

    Hello JeffYang

    Thanks for your comment, i also bumped on that, in the new ADMX files the problem still exists ( in de edit mode, overview states the correct value )

    Jacco Dominicus

    0 comments No comments