Google Chrome Managed (macOS)
Description
Chrome browser user experience may be managed on multiple device types by way of a Google Management Token available through the Google Admin Console.
Details on obtaining a token and Chrome management can be found in the following KB:
The directions below describe applying the token to macOS devices.
If you want to configure Chrome locally without Google Admin console enrollment, use the Google Chrome Configuration recipe (macOS). That is a different workflow from the enrollment-token profile below.
Ingredients
- Chrome installer Fileset
- Chrome Browser Enrolment Token (only available via Google Admin Console)
- Profile to push out the token. On macOS 11 and later, the Mac must be enrolled in MDM for managed profile installation; see Apple Profile Filesets.
The downloadable template contains a system-scoped Custom Settings payload for com.google.Chrome. Replace the CloudManagementEnrollmentToken placeholder with your organization’s token. It also sets CloudManagementEnrollmentMandatory to true: Google documents that this prevents Chrome from starting if cloud enrollment fails, for example because the token is invalid or revoked. Keep that setting only if mandatory enrollment is your intended policy; review it before assigning the profile.
macOS
Directions
- Download the above provided Fileset zip file, expand and drag into FileWave > Filesets
- Open the Profile for editing and access the Custom Settings Payload
- Edit the CloudManagementEnrollmentToken String, entering the copied token from the Google Admin console. The token shown in the screenshot is illustrative; do not deploy that value or the template’s REPLACE ME placeholder.
Association/Deployment
When assigning with devices, to ensure the configuration is installed with the Application, consider creating a Fileset Group:
Assigning the 'Google Chrome Management Token' Fileset Group targets both the application and profile to the devices. This does not prove that the profile arrived or that Chrome enrolled successfully. Begin with a pilot Mac, save the Deployment, review shared pending changes, and select Update Model in FileWave Central. Below is an example Deployment:
When there is an update to Google Chrome, replace the version in the Fileset Group with the latest version (after testing) or switch to a new Fileset Revision if desired.
After confirming that the profile installed, quit Chrome completely and reopen it. Verify that the browser appears in the intended organization in the Google Admin console’s Managed browsers view, following Google’s enrollment verification steps. Test the intended cloud policy as well as application launch before expanding the Deployment. On a shared Mac, check each intended macOS user; Google requires separate enrollment for each user.




No comments to display
No comments to display