Deploying the SysAid Browser Extension in Chrome via Addigy (macOS)

Use this guide to deploy the SysAid Browser Extension to Chrome on managed macOS devices using Addigy.

This deployment method uses an Addigy Custom MDM profile to upload and deploy the SysAid configuration profile, so IT admins can centrally apply the required Chrome extension settings.

Before you start

You’ll need your SysAid Browser Extension ID and Token.

To find them:

1. In SysAid, go to License Manager > Applications Discovery.

2. Click Manage Connections in the top right corner.

3. Under Browser Extension, click Setup to see the ID and Token.

Build the profile

Before uploading the configuration profile to Addigy, create the SysAid.mobileconfig file:

1. Copy this profile template and save it as SysAid.mobileconfig:

   
   <?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>
       <!-- Payload 1: force-install -->
       <dict>
         <key>PayloadType</key><string>com.google.Chrome</string>
         <key>PayloadUUID</key><string>UUID-ONE</string>
         <key>PayloadIdentifier</key><string>com.sysaid.chrome.forceinstall</string>
         <key>PayloadVersion</key><integer>1</integer>
         <key>ExtensionInstallForcelist</key>
         <array><string>YOUR_EXTENSION_ID;https://clients2.google.com/service/update2/crx</string></array>
         <key>ExtensionSettings</key>
         <dict><key>YOUR_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>
       <!-- Payload 2: token delivery -->
       <dict>
         <key>PayloadType</key><string>com.google.Chrome.extensions.YOUR_EXTENSION_ID</string>
         <key>PayloadUUID</key><string>UUID-TWO</string>
         <key>PayloadIdentifier</key><string>com.sysaid.chrome.token</string>
         <key>PayloadVersion</key><integer>1</integer>
         <key>token</key><string>YOUR_TOKEN_VALUE</string>
       </dict>
     </array>
     <key>PayloadType</key><string>Configuration</string>
     <key>PayloadScope</key><string>System</string>
     <key>PayloadUUID</key><string>UUID-THREE</string>
     <key>PayloadIdentifier</key><string>com.sysaid.chrome.profile</string>
     <key>PayloadVersion</key><integer>1</integer>
   </dict></plist>

2. Generate 3 unique IDs in Terminal (uuidgen && uuidgen && uuidgen) and paste them into the three UUID slots.

3. Replace YOUR_EXTENSION_ID and YOUR_TOKEN_VALUE with the values from your SysAid account.

4. Before uploading the file, validate it in Terminal to make sure the file is properly formatted: plutil -lint SysAid.mobileconfig.

   Please note:

   This check confirms that the file is valid. It does not confirm that the token is correct or that the extension was installed successfully.

The finished profile has two payloads:

• com.google.Chrome force-installs the extension from the Chrome Web Store (update URL https://clients2.google.com/service/update2/crx).

• com.google.Chrome.extensions.YOUR_EXTENSION_ID delivers the token.

Deploy the extension

1. In Addigy, go to  Policies > Catalog > MDM Configurations > New > Custom Profile.

2. Upload your .mobileconfig (confirm both payloads).

3. Assign to a pilot policy.

4. Click Save.

Verify the setup

To verify the setup:

1. In your macOS, go to System Settings > General > Device Management. See that the SysAid profile is installed with two payloads.

2. Go to chrome://extensions.

   1. The extension should be present and turned on.

   2. It will display a building/enterprise icon next to it, indicating it is managed.

   3. The option to "Remove" or toggle it off will be locked out for the end-user.