Mac Quick Start
This page describes how to get started with managing Google Chrome on a Mac network using Apple’s Profile Manager. These instructions are only an example to help you get started. You can use any system management software you choose, but specific steps may vary.
Note: These steps focus only on pushing out a plist configuration file for the Chrome Browser. Your Mac network must be set up and in a managed state. This guide does not cover how to setup macOS Server or Profile Manager to manage your Mac devices.
- Log into Profile Manager on the server machine from a web browser
- Navigate to Devices > Settings, choose the device group for which to define Chrome policies.
- Click Edit.
- Go to Custom Settings and add a Preference Domain with domain 'com.google.Chrome'
- Upload a pre-configured plist file or manually add items by key and value. A full list and description of policies can be found at https://www.chromium.org/administrators/policy-list-3.
- Click Ok and payload will be created and synced to the selected devices.
If you have trouble, it usually pays off to examine whether the settings are correctly stored and read by Chrome. First of all, navigate to about:policy in Chrome. It lists any policy settings that Chrome has picked up. If your settings show up, good. If not, you can dig deeper and check whether macOS actually put them into place correctly. Mandatory policy is stored in /Library/Managed Preferences/<username>/com.google.Chrome.plist while recommended policy is stored in /Library/Preferences/com.google.Chrome.plist. The plutil command can be used from a terminal to convert it to XML format:
cd /Library/Managed Preferences/<username>
plutil -convert xml1 com.google.Chrome.plist
For debugging, this file is in a place where it can be edited manually. Chrome will pick up the updated preferences automatically. Note that this is not recommended for making persistent changes to policy, since macOS will rewrite the file with settings configured through Workgroup Manager.
Chrome on macOS does not show unknown policies on the chrome://policy page. If you don't find a policy you have set there check if the name is spelled correctly and if the policy is actually supported on the macOS platform.
Notes for Chromium
Chromium can be managed in a similar way, with a few differences:
- The Chromium application must be managed, instead of Google Chrome
- Chromium is identified as "org.chromium.Chromium"
- The plist file is in the same place but is named "org.chromium.Chromium.plist"
Please file a bug report at http://new.crbug.com and select the "Enterprise Issue" template.