Article ID: 2573406 - View products that this article applies to.
After your administrator removes Group Policy settings that control some Microsoft Outlook 2013, Microsoft Outlook 2010 or Microsoft Office Outlook 2007 features, your Outlook settings may unexpectedly change. The affected Outlook settings include the following. However, the affected settings are not limited to these settings.
Outlook reads the settings that are described in the "Symptoms" section from different locations. One location is the user settings area of the Windows registry. When Office is deployed by using the Office Customization Tool (OCT), an administrator can decide to configure initial settings. These settings are written into the registry. These registry values are considered "seed" values. This means that when Outlook is first run, it reads the values from this "seed" location and then writes them into your Exchange mailbox as roaming settings. From this point forward, Outlook uses only the roaming settings. Because the user settings that are stored in the registry act as initial seed values, Outlook does not read them again. When you use the Outlook user interface to change your Outlook options, these changes are written directly into the roaming settings in your mailbox.
There is no option to globally set or to globally configure the roaming settings by using Group Policy or registry values.
To work around this issue, you must use the Outlook user interface to configure the settings as you want. This is necessary only if you notice a change in the expected behavior of the Outlook features that described in the "Symptoms" section after Group Policy objects that control those same features are removed.
Outlook uses the following order of preference when it reads the settings that are described in the "Symptoms" section:
If the user registry values exist, they are stored in the following locations for Outlook 2013:
Note For Outlook 2010, the registry key path begins as follows:
For Outlook 2007, the registry key path begins as follows:
You can view the roaming preferences by running MFCMAPI and then viewing the Associated Contents Folder of the Calendar. Sort by Subject, and select IPM.Configuration.Calendar. Then, double-click PR_ROAMING_DICTIONARY. The Property Editor window that opens shows some of the values. (Notice the right side of the screen shot that follows.)
The roaming preferences map to the registry values as follows:
Roaming Preference Registry Value piFBUserPublishRange FBPublishRange piFBUpdateSecs FBUpdateSecs piAutoProcess AutoProcReq piRemindDefault RemindDefault piAutoDeleteReceipts AutoDelRcpts piCalDefStart CalDefStart piCalDefEnd CalDefEnd piWorkday WorkDay