
Specify the major version, such as 86., to let computers update to the highest available version of 86.Unless you specify the exact version, include a period (.) after the version number to pin updates to the highest available version. You can use version numbers with up to 4 parts, such as. For Target version prefix, enter the version number of the Chrome browser version that you want computers to update to.Next to Chrome browser updates, select Allow updates.

Otherwise, select a child organizational unit. Here we also see some sub categories, like Cat_Preferences and Cat_Applications.To apply the setting to all enrolled browsers, leave the top organizational unit selected. The first categorie we find in the ADMX file is the top category and as we can see that is Cat_GoogleUpdate. When we open the ADMX file in a text editor, we can see there are several categories. These categories can be found in the Chrome ADMX file. Between every part we have the ~ sign.Īfter Policy we see the name of two categories. It starts with GoogleUpdate (the ADMX file name), like in the ADMXInstall URI, followed by Policy. GoogleUpdate~Policy~Cat_GoogleUpdate~Cat_Preferences/Pol_AutoUpdateCheckPeriod The part that comes next is not always the same, we need to follow some rules: This is default for managing applications using an ADMX file: Let`s split up the OMA-URI in seperate parts. Device/Vendor/MSFT/Policy/Config/GoogleUpdate~Policy~Cat_GoogleUpdate~Cat_Preferences/Pol_AutoUpdateCheckPeriod This is for example the OMA-URI to manage the Auto Update Check Period: But the OMA-URI for managing the settings consists of some information we need to collect ourselves from the Google Update ADMX file. How to build up the OMA-URIĪs with deploying the ADMX file, for the settings to manage we also need to know the OMA-URI which we need to use. In the next steps we add the settings we manage with Intune to the same policy. The policy to deploy the ADMX file is ready.

Now open a browser to sign-in to the Microsoft Endpoint Manager portal.

After downloading the bundle, locate the ADMX file and open the file with a text editor. The Google Update ADMX file can be downloaded as part Chrome Enterprise bundle. Note: most settings do only work on (Hybrid Azure) AD Joined devices. The second part of the policy is used to manage the settings of choice. The first part is used to deploy the Google Update ADMX file to the Intune managed device. Like the Google Chrome settings, the Google Update settings can also be managed using a custom configuration profile for Windows 10.

In this post I will show how we can use Microsoft Endpoint Manager (Intune) to manage Google Update settings. This is a follow-up post on Managing Google Chrome settings with Microsoft Intune.
