Deployment Guide

macOS Configuration Profiles

macOS Chrome Edge Firefox

Deploy Ghostery to Mac devices using Apple configuration profiles. This MDM-agnostic approach works with JAMF, Kandji, Mosyle, Intune, and any other MDM that supports custom configuration profiles.

Chrome Configuration Profile

Create a .mobileconfig file with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>PayloadContent</key>
  <array>
    <dict>
      <key>PayloadType</key>
      <string>com.google.Chrome</string>
      <key>PayloadIdentifier</key>
      <string>com.ghostery.chrome.extension</string>
      <key>PayloadUUID</key>
      <string>YOUR-UUID-HERE</string>
      <key>PayloadVersion</key>
      <integer>1</integer>
      <key>ExtensionInstallForcelist</key>
      <array>
        <string>mlomiejdfkolichcflejclcbmpeaniij;https://clients2.google.com/service/update2/crx</string>
      </array>
      <key>3rdparty</key>
      <dict>
        <key>extensions</key>
        <dict>
          <key>mlomiejdfkolichcflejclcbmpeaniij</key>
          <dict>
            <key>disableOnboarding</key>
            <true/>
            <key>disableUserControl</key>
            <true/>
            <key>trustedDomains</key>
            <array>
              <string>your-company.com</string>
            </array>
          </dict>
        </dict>
      </dict>
    </dict>
  </array>
  <key>PayloadDisplayName</key>
  <string>Ghostery Chrome Extension</string>
  <key>PayloadIdentifier</key>
  <string>com.ghostery.chrome</string>
  <key>PayloadType</key>
  <string>Configuration</string>
  <key>PayloadUUID</key>
  <string>YOUR-PROFILE-UUID</string>
  <key>PayloadVersion</key>
  <integer>1</integer>
</dict>
</plist>

Edge Configuration Profile

Use com.microsoft.Edge as the PayloadType:

<key>PayloadType</key>
<string>com.microsoft.Edge</string>
<key>ExtensionInstallForcelist</key>
<array>
  <string>fclbdkbhjlgkbpfldjodgjncejkkjcme;https://edge.microsoft.com/extensionwebstorebase/v1/crx</string>
</array>
<key>3rdparty</key>
<dict>
  <key>extensions</key>
  <dict>
    <key>fclbdkbhjlgkbpfldjodgjncejkkjcme</key>
    <dict>
      <key>disableOnboarding</key>
      <true/>
      <key>disableUserControl</key>
      <true/>
    </dict>
  </dict>
</dict>

Firefox Configuration

Firefox doesn't use configuration profiles the same way. Instead, deploy these files:

policies.json

Location: /Applications/Firefox.app/Contents/Resources/distribution/policies.json

{
  "policies": {
    "ExtensionSettings": {
      "firefox@ghostery.com": {
        "installation_mode": "force_installed",
        "install_url": "https://addons.mozilla.org/firefox/downloads/latest/ghostery/latest.xpi"
      }
    }
  }
}

Managed Storage Manifest

Location: /Library/Application Support/Mozilla/ManagedStorage/firefox@ghostery.com.json

{
  "name": "firefox@ghostery.com",
  "description": "Ghostery managed configuration",
  "type": "storage",
  "data": {
    "disableOnboarding": true,
    "disableUserControl": true,
    "trustedDomains": ["your-company.com"]
  }
}

Deploy these files using a script payload in your MDM.

Deploying the Profile

Upload the .mobileconfig file to your MDM:

• JAMF Pro: Computers → Configuration Profiles → Upload
• Kandji: Library → Add New → Custom Profile
• Mosyle: Management → Profiles → Add Profile
• Intune: Devices → macOS → Configuration profiles → Create

Verify Installation

After the profile is deployed:

1. Check System Preferences → Profiles to confirm the profile is installed
2. Open the browser and navigate to the policy page (chrome://policy, edge://policy, or about:policies)
3. Verify the extension appears as force-installed