Files

T

Gray Williams 98983c337a Fixes broken links in managing-chrome-with-fleet.md (#47093 )

Links to the solutions folder weren't quite as expected, resulting in
404's

2026-06-10 16:41:09 -04:00

7.3 KiB

Raw Permalink Blame History

Managing Google Chrome on Windows with Fleet

Use configuration profiles to enforce consistent Chrome browser settings across your Windows devices. Before configuring Chrome policies, you must first deploy the Google Chrome ADMX file to your devices — skipping this step will cause errors during verification or prevent policies from applying.

Prerequisites:

Administrative access to Fleet.
Windows devices enrolled in Fleet.
Basic familiarity with XML syntax and Group Policy concepts.

Resources:

An example Google Chrome ADMX configuration profile is available in our GitHub solutions folder (May not be the latest version available)
An example configuration profile for enrolling your browsers into Chrome Enterprise Core for a Cloud-managed Chrome browser is available in our GitHub solutions folder

Step 1: Download the Google Chrome ADMX files

Download the latest Google Chrome ADMX templates from the official source: Download Chrome ADMX templates (zip file)
Extract the ZIP file and locate the chrome.admx file in the windows\admx folder.

Step 2: Deploy the ADMX file to the device

To apply Chrome policies, Windows needs the ADMX file to understand what settings are being configured. Do this by creating a configuration profile that deploys the ADMX content to your devices. For more information, see Creating Windows CSPs: Ingesting custom ADMX templates.

Create a configuration profile for ADMX ingestion

Create a new file in your editor of choice, and use the following template:

<Add>
  <Item>
    <Meta>
      <Format xmlns="syncml:metinf">chr</Format>
      <Type>text/plain</Type>
    </Meta>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Chrome/Policy/ChromeAdmxFile</LocURI>
    </Target>
    <Data><![CDATA[
      <!-- Paste the full contents of chrome.admx here -->
    ]]></Data>
  </Item>
</Add>

Note:

Add the entire contents of the chrome.admx file into <![CDATA[ ... ]]>
This ensures the ADMX file is available for policy configuration on target devices.

In Fleet, navigate to Controls > OS settings > Configuration profiles and add a profile.
Select the .xml file you have just created.

Step 3: Configure Chrome policies or enroll into Chrome Enterprise cloud management

Once the ADMX file is deployed, you can configure Chrome policies using the <Replace> block in a new or existing configuration profile.

Example: enrolling devices in to Chrome Enterprise cloud management

If you would like to enroll your Chrome browsers to control the settings from the Google cloud management portal, you can deploy a profile with the relevant enrollment key. Replace the the x's with your key.

<Replace>
  <Item>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/Config/chrome~Policy~googlechrome/CloudManagementEnrollmentToken</LocURI>
    </Target>
    <Meta><Format xmlns="syncml:metinf">chr</Format></Meta>
    <Data>&lt;enabled/&gt;&lt;data id=&quot;CloudManagementEnrollmentToken&quot; value=&quot;xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&quot;/&gt;</Data>
  </Item>
</Replace>

Example: configuring `RelaunchNotification` and `RelaunchNotificationPeriod`

However, if you would like to manage your Chrome configuration by code, you can use profiles to configure any settings available from the ADMX file.

<Replace>
  <Item>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/Config/chrome~Policy~googlechrome/RelaunchNotification</LocURI>
    </Target>
    <Meta><Format xmlns="syncml:metinf">chr</Format></Meta>
    <Data>&lt;enabled/&gt;&lt;data id=&quot;RelaunchNotification&quot; value=&quot;2&quot;/&gt;</Data>
  </Item>
  <Item>
    <Target>
      <LocURI>./Device/Vendor/MSFT/Policy/Config/chrome~Policy~googlechrome/RelaunchNotificationPeriod</LocURI>
    </Target>
    <Meta><Format xmlns="syncml:metinf">int</Format></Meta>
    <Data>&lt;enabled/&gt;&lt;data id=&quot;RelaunchNotificationPeriod&quot; value=&quot;259200000&quot;/&gt;</Data>
  </Item>
</Replace>

Key points:

<Format>: Use int for integer (REG_DWORD) values and chr for string/boolean values.
<LocURI>: The OMA-URI path for the policy. Refer to the Chrome Enterprise Policy List for valid paths.
<Data>: The policy value. For boolean policies, include <enabled/> followed by the <data> tag.
RelaunchNotificationPeriod values are in milliseconds. The example value 259200000 equals 3 days.

Step 4: Deploy and verify

In Fleet, navigate to Controls > OS settings > Configuration profiles and add your new configuration profile.
You can Refetch the devices to apply the configuration sooner.
Verify the policies:

Open regedit on a target device and navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
Confirm that the policies (e.g., RelaunchNotification, RelaunchNotificationPeriod) appear with the correct values.
Restart Chrome and test the behaviour (e.g., check if the relaunch notification appears as configured).

Troubleshooting

Issue	Possible cause	Solution
Error during verification	ADMX file not ingested	Ensure the profile was deployed successfully.
Policies not applying	Incorrect `<Format>` or `<LocURI>`	Double-check `<Format>` (e.g., `int` for REG_DWORD) and the OMA-URI path.
ADMX file not found	Incorrect `<LocURI>` in the `<Add>` block	Verify the path in the `<Target>` section matches Fleet's expected location.
Device sync failures	Network or Fleet agent issues	Check the Fleet agent logs on the device for errors.

References

Next steps

Explore additional Chrome policies in the Chrome Enterprise Policy List.
Test policies in a staging environment before fleet-wide deployment.

7.3 KiB Raw Permalink Blame History