---
title: "Deploying the SysAid Browser Extension via VMware Workspace ONE"
slug: "deploying-the-sysaid-browser-extension-via-vmware-workspace-one"
updated: 2026-06-23T11:10:16Z
published: 2026-06-23T11:10:16Z
canonical: "documentation.sysaid.com/deploying-the-sysaid-browser-extension-via-vmware-workspace-one"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.sysaid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploying the SysAid Browser Extension via VMware Workspace ONE

Use this guide to deploy the SysAid Browser Extension using VMware Workspace ONE. This deployment method lets IT admins manage deployment from a single console, while using the appropriate OS-specific payload for each device: a Custom Settings profile for Windows and a custom profile for macOS.

## 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.

## Deploy on Windows devices

Push the same two registry values via a **Custom Settings** profile running PowerShell:

1. In the Workspace ONE UEM console, go to **Resources** > **Profiles & Baselines** > **Profiles.**
2. Click **Add** > **Windows** > **Custom Settings**.
3. In the payload, deliver both keys (e.g., via a PowerShell command/script step). Replace the ID and Token values with those for your SysAid account:

```plaintext
$ExtensionId = "YOUR_EXTENSION_ID"
$Token       = "YOUR_TOKEN_VALUE"
$Force  = "HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist"
$Policy = "HKLM:\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\$ExtensionId\policy"
New-Item -Path $Force -Force | Out-Null
Set-ItemProperty -Path $Force -Name "1" -Value "$ExtensionId;https://clients2.google.com/service/update2/crx" -Type String
New-Item -Path $Policy -Force | Out-Null
Set-ItemProperty -Path $Policy -Name "token" -Value $Token -Type String
```

Assign to your pilot group and click **Save & Publish**.

## Deploy on macOS devices

To deploy on macOS devices:

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

```plaintext
<?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 to VMware Workspace ONE, validate it in Terminal to make sure the file is properly formatted: `plutil -lint SysAid.mobileconfig`
5. In the Workspace ONE UEM console, go to **Resources** > **Profiles.**
6. Click **Add** > **macOS** > **Custom Settings**.
7. Paste the contents of the .mobileconfig (both payloads).
8. Assign to a macOS pilot group and click **Save & Publish**.

## Verify the setup

To verify the setup:

1. In the Workspace ONE UEM console, go to **Resources > Profiles & Baselines > Profiles**.
2. Click on the profile you created for the SysAid extension (e.g., your Windows Desktop or macOS device profile).
3. Look at the **View Status** ring. • **Installed:** The device successfully processed the profile. • **Unassigned/Assigned:** The device hasn't checked in or hasn't evaluated the group assignment yet. • **Failed:** The payload syntax or custom settings script had an error.

## Related

- [Application Discovery Overview](/application-discovery-overview.md)
- [SysAid Browser Extension](/sysaid-browser-extension.md)