Deploy the ConcealBrowse extension to Chrome on macOS using Jamf Pro Deploy the ConcealBrowse extension to Chrome on macOS using Jamf Pro

Deploy the ConcealBrowse extension to Chrome on macOS using Jamf Pro

Description

Deploy the ConcealBrowse extension to Google Chrome on macOS endpoints seamlessly with Jamf Pro.

Applies to

  • Jamf Pro
  • Apple macOS
  • Google Chrome

Procedure for Normal Installation (user can disable)

Note: These steps have been written based on vendor articles but not yet verified by Conceal.

Prepare the Chrome plist file

  1. Download our pre-configured JamfPro com.google.Chrome.plist.removeme file attached to this article. Once downloaded, delete the .removeme extension.
  2. Open the file with a text editor which handles XML well
    Ex. Visual Studio Code - you can download it here if needed. The XML Tools extension is very helpful
  3. Review and modify any other settings desired. For example Incognito mode and guest mode will be disabled by the plist file to prevent bypassing ConcealBrowse protections.
  4. Save the file

Prepare the ConcealBrowse plist file

  1. Download our pre-configured JamfPro ConcealBrowse.plist.removeme file attached to this article. Once downloaded, delete the .removeme extension.
  2. Open the file with a text editor which handles XML well
    Ex. Visual Studio Code - you can download it here if needed. The XML Tools extension is very helpful
  3. On lines 8 and 10, replace "your company id from dashboard.conceal.io" with your Company ID and Site ID. Ensure they are all lowercase. Find your Company ID & Site ID: Register New Device > Step 4
  4. Save the file

Load the Chrome plist file into Jamf Pro

  1. Log in to Jamf Pro
  2. Click Computers at the top of the page
  3. Click Configuration Profiles
  4. Click New
  5. Use the General payload to configure basic settings, including the level at which to apply the profile and the distribution method.
  6. Click the Applications & Custom Settings payload, and then click Configure
  7. To upload a custom PLIST file:
    1. Choose Upload File

    2. Enter the preference domain for which you want to set properties: com.google.Chrome

    3. Click Upload PLIST File, and then choose the JamfPro com.google.Chrome.plist file you previously customized
      Note: If the PLIST file contains formatting errors, follow the on-screen instructions to remediate the issue, and then execute the following command before re-uploading the file:
      /usr/bin/plutil -convert xml1 /path/to/file.plist
  8. Click the Scope tab, and then configure the scope of the configuration profile. For more information, see Scope in the Jamf Pro Documentation.
  9. Click Save

Load the ConcealBrowse plist file into Jamf Pro

  1. Ensure you've completed: Prepare the ConcealBrowse plist file
  2. Log in to Jamf Pro
  3. Click Computers at the top of the page
  4. Click Configuration Profiles
  5. Click New
  6. Use the General payload to configure basic settings, including the level at which to apply the profile and the distribution method.
  7. Click the Applications & Custom Settings payload, and then click Configure
  8. To upload a custom PLIST file:
    1. Choose Upload File

    2. Enter the preference domain for which you want to set properties: com.google.Chrome.extensions.jmdpihfpelphmllgmamebdbelmobjfpg

    3. Click Upload PLIST File, and then choose the JamfPro ConcealBrowse.plist file you customized
      Note: If the PLIST file contains formatting errors, follow the on-screen instructions to remediate the issue, and then execute the following command before re-uploading the file:
      /usr/bin/plutil -convert xml1 /path/to/file.plist
  9. Click the Scope tab, and then configure the scope of the configuration profile. For more information, see Scope in the Jamf Pro Documentation.
  10. Click Save

Procedure for Enforced Installation (user cannot disable)

Use the directions above; within the JamfPro com.google.Chrome.plist file, change the installation_mode from normal_installed to force_installed.

<key>installation_mode</key>
<string>force_installed</string>

References