Manage Google Chrome Extensions on macOS

What this profile does

This macOS profile controls which Google Chrome extensions are blocked or force-installed. Use it when Chrome extension policy is managed through FileWave rather than through Google Admin.

Choose one source of truth for the same Chrome policy. If Google Admin already manages Chrome for these users or browsers, configure the extension there instead of deploying a competing FileWave profile.

Requirements

• Google Chrome installed on the pilot Macs
• The extension ID and update URL supplied by the extension publisher
• The downloadable example profile below

macOS

Import the profile into FileWave Central, replace the example extension ID and comment with the intended extension values, and create a Deployment for pilot Macs. Restart Chrome, verify the required extension installs, and confirm unrelated extensions follow the wildcard policy before expanding the Deployment.

Contents of Profile:

Dict {
    PayloadDisplayName = Google Chrome Extension Policy
    PayloadScope = System
    PayloadType = Configuration
    PayloadRemovalDisallowed = false
    ConsentText = Dict {
        default = 
    }
    PayloadContent = Array {
        Dict {
            PayloadVersion = 1
            PayloadDisplayName = Custom: (com.google.Chrome)
            PayloadType = com.apple.ManagedClient.preferences
            PayloadContent = Dict {
                com.google.Chrome = Dict {
                    Forced = Array {
                        Dict {
                            mcx_preference_settings = Dict {
                                ExtensionSettings = Dict {
                                    * = Dict {
                                        installation_mode = blocked
                                    }
                                    obeophmpnnhboefjagnpbllfbbaeodnn = Dict {
                                        installation_mode = force_installed
                                        update_url = https://clients2.google.com/service/update2/crx
                                        comment = Required organization extension
                                    }
                                }
                            }
                        }
                    }
                }
            }
            PayloadEnabled = true
            PayloadIdentifier = ml1063.lan.c7256e52-e8f0-4b6b-b48d-5ec98c03ff8a.com.apple.ManagedClient.preferences.87789162-48a1-42bf-b444-ff6567a9e7f0
            PayloadUUID = 87789162-48a1-42bf-b444-ff6567a9e7f0
        }
    }
    PayloadIdentifier = ml1063.lan.c7256e52-e8f0-4b6b-b48d-5ec98c03ff8a.Configuration.c7256e52-e8f0-4b6b-b48d-5ec98c03ff8a
    PayloadVersion = 1
    PayloadUUID = c7256e52-e8f0-4b6b-b48d-5ec98c03ff8a
}

Policy notes

Review the wildcard rule. The example sets * to blocked, so every extension not explicitly allowed is blocked. Remove or change that rule when it does not match your Chrome policy.

Restart Chrome after the profile installs so the browser reads the managed extension settings.

Related Content

• Google Chrome Extension Management (Windows)