- 07 Mar 2025
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Mass Deploy Whatfix Extension using Jamf for MacOS on the Chrome Browser
- Updated On 07 Mar 2025
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Jamf is a Mobile Device Management (MDM) system that is used to remotely manage apps on end user machines. Read this section to learn about how you can setup and manage Whatfix extensions on your end users’ MacOS devices on the Chrome browser.
Prerequisites:
You must have access to Jamf to smoothly deploy the Whatfix extension for your end users.
You need to add the policy manifest in Jamf for Google Chrome.
To install Whatfix extension in the end user’s web browser on a MacOS device perform the following steps:
Use the following steps to add a configuration profile:
Log in to Jamf Pro. You are logged in to the Jamf Dashboard page.
Click Computers.
In the Content Management section, click Configuration Profiles. This opens a new, unnamed configuration profile for you to define for MacOS devices.
Click New to create a new configuration profile.
In the General section, enter a meaningful Name and Description for your configuration profile.
Scroll to the Application & Custom Settings tab, and then click Upload.
In the Distribution Method, select Install automatically.
Click Add.
Under Preference Domain, enter the following domain:
com.google.Chrome
Under Property List, copy and paste the following code block:
For Whatfix Store
<?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>ExtensionSettings</key> <dict> <key>lpbfekfcnoafocpigbcmbhhndbadhkba</key> <dict> <key>installation_mode</key> <string>force_installed</string> <key>update_url</key> <string>https://addons.whatfix.com/whatfix-store/chrome/lpbfekfcnoafocpigbcmbhhndbadhkba/update.xml</string> </dict> </dict> </dict> </plist>
For Google Web Store
<?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>ExtensionSettings</key> <dict> <key>WHATFIX_EXTENSION_ID</key> <dict> <key>installation_mode</key> <string>force_installed</string> <key>update_url</key> <string>https://clients2.google.com/service/update2/crx</string> </dict> </dict> </dict> </plist>
Info:
Based on your requirements, perform the following changes to the code in the Property List section:
If you want your end users to have the option to uninstall the Whatfix extension, change the keyword
force_installed
tonormal_installed
.If you don't want to automatically pin the extension to the end user's toolbar, remove the
key_toolbar_pin
and the associated stringforce_pin
.Click Scope.
Click + Add.
Use the Add button to add all the target computers.
Info:
Added target computers appear as follows:
Click Save.
Troubleshooting
After you’ve added the configuration profile created in Jamf and deployed on the target devices, confirm the installation to validate the deployment process.
Perform the following steps to validate the configuration profile:
Confirm the presence of the configuration profile
Use the following steps to verify the details of the configuration profile:
On the end user’s Mac, in the Apple menu, click System Settings.
Click Privacy & Security.
Click Profiles.
Double click the configuration you added in Jamf.
Verify the Property List information and other details.
Validate the content of your delivered profile
Once you've confirmed that the configuration file is present, validate that the file is formatted correctly by checking that the browser correctly force-installs the extension.
Use the following steps to verify content of the configuration profile:
On the end user’s device, launch the Chrome browser.
Note:
If the Chrome browser app is already open, quit and re-launch the browser.
Go to
chrome://extensions
.Verify that Whatfix Internal Extension profile appears under My extensions.
Note:
If you specified
force_installed
when creating the configuration profile, you can’t disable the extension from the page.Go to
chrome://policy
, and verify the details of the extension.