Skip to main content
Connect your AI

Installing the browser extension

You put the StackJack browser extension on your staff's computers with the tools that manage those computers: Microsoft Intune, Group Policy, or any RMM. One page does it for both StackJack products:…

Written By Christopher Scaminaci

Last updated 4 days ago

You put the StackJack browser extension on your staff's computers with the tools that manage those computers: Microsoft Intune, Group Policy, or any RMM. One page does it for both StackJack products: AI Governance → Staff computers → Deploy. You do not ask each person to install anything.

At a glance

  • What it does: shows how to install the extension in Chrome, Edge and Firefox with Intune, Group Policy or one PowerShell script.
  • Plan: every plan.
  • Who: an Administrator.
  • Where: AI Governance → Staff computers → Deploy, on the Browser extension card. Then Staff computers → Coverage to check that it works.

This page walks through the setup. What the extension does is in The StackJack browser extension.

Before you start

  • You need the Admin role in AI Governance.
  • Each computer needs access to the Chrome Web Store, or to Firefox Add-ons, to download the extension.

The Deploy page

The menu entry Deploy opens the page Deploy to staff computers. Open Coverage, in the page head, opens the page that lists each computer.

At the top are two cards, one for each product: Browser extension and Endpoint agent. Select a card to open that product. The Browser extension card is open when the page opens. Each card shows one state and how far the product reaches:

State on the cardWhat it means
Not availableThe browser extension is not available in your region yet.
Turned offThe extension is off for this organization.
Needs a tokenThe extension is on, and the organization has no browser token yet.
Not readyNo browser can be deployed yet. Step 1 says why.
Waiting for dataEverything is ready, and no browser has reported yet.
WorkingAt least one browser reported in the last 14 days.

The card also says how many browsers report, for example "12 browsers report". StackJack does not know how many browsers you have, so the card shows a count with no "of" and no bar.

Under the cards is one panel, Deploy the browser extension, with three numbered steps:

  1. Check that it is ready
  2. Choose how you deploy, then do it
  3. Watch computers report

Beside the steps are three cards with the facts: Reach, Your browser token and Try it on one computer first. Reach has one row for each product, and Open Coverage under it.

The page has one filled button at a time: the next thing to do. That is Turn it on and make the token, then Make the token, then Copy script.

Set it up

  1. Open AI Governance → Staff computers → Deploy. The Browser extension card is open first.
  2. In step 1, Check that it is ready, read the three checks:
    • Turned on or Turned off. If the check says Turned off, press Turn it on and make the token. StackJack turns the extension on and makes your organization's browser token with it. If the check says Not available here, the browser extension is not available in this region yet, and there is nothing to press.
    • Browser token ready or No browser token yet. If the extension is on and has no token, press Make the token. You do not see the token on the page. The script carries it.
    • The browsers that are ready, for example "Chrome, Edge and Firefox ready". While the first two checks are open, this check reads "Ready once the extension is on and has its token." A browser that is not ready for a reason of its own says why: the store listing for this browser is not set up in this region yet, or this region's StackJack address for browsers is not set up yet.
  3. Choose your policy on the Browser extension page. See Browser policy. The first choice to make is what happens on an AI site that is not approved. The default is Allow, which only finds sites.
  4. In step 2, Choose how you deploy, then do it, pick one card: Microsoft Intune (marked Recommended), Group Policy, Script, or macOS and Linux. The numbered lines under the cards are the ones for the card you picked, and each line holds the button it needs. Each way is described below.
  5. In step 3, Watch computers report, the page says how many browsers report. They are counted over the last 14 days. A browser shows there a few minutes after it first starts with the policy. See which computers opens Staff computers → Coverage, where each computer and person appears as it reports in.

Do not install the extension by hand and do not copy the browser token. A computer that gets the policy gets the extension and the token together.

The store pages

The card Try it on one computer first links to the two live store pages. The store pages install the extension on one computer, for a test:

Edge has no listing of its own. It installs the Chrome Web Store package, so one listing covers Chrome and Edge. For a whole organization, deploy it with a policy: nobody has to press Add.

The script

One PowerShell script does the whole job on Windows, for all three browsers. The Script card is for your remote management tool, or for one computer by hand. Its lines are:

  1. Pick the browsers. Tick the browsers you want. Every browser that is ready is ticked to start with.
  2. Get the script. Press Copy script or Download script (.ps1).
  3. Run it as Administrator, or as the system account from your remote management tool.

The Microsoft Intune and Group Policy cards hand out the same script, for the browsers that are ticked on the Script card. While no browser is ready, Copy script is off and its tip says "Fix the checks in step 1 first."

The script:

  • installs the StackJack extension in the browsers you ticked (Chrome, Edge and Firefox);
  • writes the extension's settings, including your organization's browser token, where each browser reads its managed policy;
  • adds to the lists your organization already manages and never replaces them, so running it twice changes nothing the second time;
  • needs Administrator, or the system account from an RMM. It works in Windows PowerShell 5.1 and in PowerShell 7, and it writes to the 64-bit registry, so a 32-bit PowerShell started by an RMM agent still reaches the browsers.

Run it as an administrator. The page shows the command, with a copy button:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install-stackjack-browser-extension.ps1

Add -DryRun to see what it would change without changing anything. A dry run needs no administrator and never prints the token.

The script plans every change from what is already in the registry before it writes anything. If Firefox's extension policy holds something the script will not merge into (it is not valid JSON, or it is stored as a registry key instead of a value), the script stops and writes nothing at all, not even for Chrome and Edge. Fix that policy and run the script again. Its last line is always STACKJACK-RESULT followed by a code and the number of changes:

CodeWhat happened
0Done, or there was nothing to change.
13The script was not run as Administrator or as the system account.
15A registry value could not be read or written.
16Firefox's policy holds something the script will not merge into. It was left untouched.

The script holds your organization's browser token. Treat it like a password. The token only lets a browser report to your organization, but anyone who can read the script can read the token. Copy script asks StackJack for the script when you press it and writes it straight to your clipboard. The page itself never shows the token. Every copy and every download is recorded in the audit trail with the browsers named and never the token.

Microsoft Intune

One script does everything, so this card is marked Recommended. Its lines are:

  1. Get the script. It installs the extension and writes your token and settings in one run. Press Copy script or Download script (.ps1).
  2. Open the Intune admin center. Go to Devices, Scripts and remediations, Platform scripts, Add, Windows 10 and later.
  3. Upload the script with these three settings. The page lists them as a table: Run this script using the logged on credentials is No, Enforce script signature check is No, and Run script in 64-bit PowerShell host is Yes.
  4. Assign it to your group of computers, then create it. Intune runs the script once on each computer, and again when you upload a changed copy.

After you rotate the token, upload the new copy.

If you prefer to manage the install list with settings, open Prefer the settings catalog to a script? under the lines. The Intune settings catalog can install the extension. It cannot carry the token, so run the script as well, or the extension has nothing to report with:

  • Edge: Microsoft Edge, Extensions, Control which extensions are installed silently. Enabled, and add <extension id>;https://clients2.google.com/service/update2/crx.
  • Chrome: Google, Google Chrome, Extensions, Configure the list of force-installed apps and extensions. Enabled, and add the same value.
  • Firefox: the settings catalog has no Firefox settings. Use the script.

The Deploy page shows the exact value with your extension id.

Group Policy

The same script runs as a computer startup script, for computers in Active Directory. It is the only Group Policy way that also writes the token. Its lines are:

  1. Get the script and put it where the computers can read it, for example the GPO's own Startup folder.
  2. Edit the GPO that applies to the computers. In Group Policy Management: Computer Configuration, Policies, Windows Settings, Scripts (Startup/Shutdown), Startup.
  3. Add the script. Open the PowerShell Scripts tab, press Add and choose the script.
  4. Restart a test computer. Startup scripts run at boot.

Under the lines, Or use the policy templates for the install list shows the template settings. The templates install the extension. They cannot carry the token, so the script is still needed for that:

  • Edge: Administrative Templates, Microsoft Edge, Extensions, Control which extensions are installed silently.
  • Chrome (needs Google's Chrome templates): Administrative Templates, Google, Google Chrome, Extensions, Configure the list of force-installed apps and extensions.
  • Firefox (needs Mozilla's Firefox templates): the ExtensionSettings policy force-installs an add-on by its id.

Edge installs an extension from the Chrome Web Store only on computers joined to a domain. Microsoft documents this for Windows computers joined to Active Directory, and its ExtensionSettings page also names Microsoft Entra join. Check one pilot computer at edge://policy and edge://extensions before you roll Edge out. The page shows a short form of this warning under each of the three Windows ways.

macOS and Linux

The Windows script does not run on macOS or Linux. StackJack makes a configuration profile for macOS and a policy file for Linux from your managed settings policy. The macOS and Linux card has the link Open Coding tools, Token and files. On Staff computers → Coding tools, choose the browsers in the policy (Chrome extension, Edge extension, Firefox extension), make the settings, and take the files from Token and files. Deliver them with your RMM or with Intune, as you do for the other endpoint settings. See Settings for staff machines.

Delivering the files with your RMM

If your RMM is NinjaOne, Datto RMM, N-central, SuperOps or ConnectWise Automate, StackJack can also deliver the managed settings files itself, including the browser files, through a delivery target. See Delivering settings through your RMM. If you imported the Windows installer script of the delivery lane before the browser extension existed, import it again once. The old script does not know the browser settings. When it meets a bundle that holds browser settings, it stops and reports an error instead of changing anything. Bundles without a browser are the same as before and need nothing.

The raw values

At the end of step 2, under each of the three Windows ways, open Raw registry values, for people who set them another way. A table lists the exact registry values the script writes for each browser, with a placeholder where the token goes. Inside it, Read the script before you run it shows the script's text with the places StackJack fills in. Use it if you set the values another way.

If you already manage the browser

Your own settings are never overwritten.

  • Chrome and Edge on Windows. The script adds our entry to your list of force-installed extensions at the lowest free number.
  • Firefox on Windows and Linux. The script (and the installer for the managed settings files) reads the policy that is there, adds our entry only if it is not there, and writes the policy back. If the existing Firefox policy cannot be read as valid JSON, the script leaves it untouched and stops with an error that names the problem. Fix that policy, then run it again.
  • Firefox on macOS. macOS does not merge Firefox settings that come from two different profiles. If you already deliver Firefox extension settings in your own profile, do not deploy ours. Add our entry to yours instead. The Deploy page shows the exact Firefox values under Raw registry values, for people who set them another way.

Checking a computer

After the browser reads the policy, the extension shows in the browser's extension list as installed by your organization. The browser's policy page lists the policy: chrome://policy in Chrome, edge://policy in Edge and about:policy in Firefox. If a computer does not get the extension, check that the policy is listed there. Browser makers decide which computers they treat as managed, so a computer that the browser does not treat as managed can ignore the policy. Check the browser maker's own rules if the policy is missing.

A computer or person appears on Staff computers → Coverage after the extension reports in. This takes a few minutes after the browser first starts with the policy. Coverage shows, for each person, which browsers run the extension, which version, and when it was last seen. See Browser coverage and troubleshooting.

Updating

The browser updates the extension from the store on its own. When StackJack changes the list of AI sites it reads, the extension fetches the new list without a new install.

Rotating the browser token

On the Deploy page, the card Your browser token shows the start of the token, the day it was made and its state. It never shows the whole token. Rotate the token opens a dialog. Type ROTATE and press Rotate the token. Then copy or download the script again and deploy it again. The old token keeps working for seven days.

You can also rotate a token, and revoke one, on the Token tab of the Browser extension page. See Browser coverage and troubleshooting.

Turning it off

  1. Turn off Use the StackJack browser extension on the Browser extension page. Within about five minutes the extension stops blocking and stops checking sends.
  2. To remove the extension, remove the force-install policy with your RMM or Intune (for the script, delete the extension's entry from the browser's force-install list). The browser then removes the extension.