Forum Discussion

Abdul_Asath's avatar
Abdul_Asath
Copper Contributor
Jul 15, 2024

Intune configuration policy

Hello All,

 

Is there Intune configuration policy available for disabling outlook's "Cached exchange mode" for shared PCs? . I know that it is available as user policy but i need this for shared PCs.

  • myboyapkee's avatar
    myboyapkee
    Copper Contributor

    Yes, there is a way to configure Intune policies to manage Outlook settings, including disabling "Cached Exchange Mode" on shared PCs. While the configuration policy to disable "Cached Exchange Mode" is more commonly available as a user policy, you can achieve this for shared PCs using device configuration profiles in Intune.

    Here’s how you can do it:

    Create a Custom Configuration Profile in Intune:

    Sign in to the Microsoft Endpoint Manager admin center.
    Navigate to Devices > Configuration profiles > Create profile.
    Select Windows 10 and later as the platform.
    Choose Custom as the profile type.
    Add the Required OMA-URI Settings:

    In the Custom OMA-URI Settings pane, click Add.
    Enter the following details:
    Name: Disable Cached Exchange Mode
    Description: Disables Cached Exchange Mode for shared PCs.
    OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Office/Outlook/DisableCachedExchangeMode
    Data type: Integer
    Value: 1 (or 0 to enable it)
    Assign the Profile to Shared PCs:

    In the Assignments section, select the device groups that include your shared PCs.
    Review and create the profile.
    Synchronize the Devices:

    Ensure that the devices sync with Intune to apply the new configuration settings.
    By following these steps, you can create a custom configuration profile that applies the desired Outlook setting across shared PCs in your environment. This approach leverages the flexibility of custom OMA-URI settings to configure specific policies that might not be directly available in the standard configuration options.

    Ensure you test this policy on a few devices before rolling it out to your entire environment to confirm it behaves as expected.

    • Abdul_Asath's avatar
      Abdul_Asath
      Copper Contributor
      Hello, This doesn't seems to be working. Getting the error code "-2016281112"
  • chrisslroth's avatar
    chrisslroth
    Brass Contributor
    You can deploy a powershell or remediation script, which sets the followings reg-entries:

    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\outlook\ost]
    “NoOST”=dword:00000002
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\outlook\cached mode]
    “Enable”=dword:00000000

Resources