Skip to main content
Connect your AI

Delivering the settings through your RMM

You can have StackJack deliver the settings files to staff machines through the remote management tool you already connected. This page explains how a push works, how to set up each tool and which…

Written By Christopher Scaminaci

Last updated 13 days ago

You can have StackJack deliver the settings files to staff machines through the remote management tool you already connected. This page explains how a push works, how to set up each tool and which machines each tool reaches.

At a glance

  • Plan: every plan.
  • Who: a governance administrator.
  • Where you set it up: AI Governance → Staff computers → Coding tools, in the delivery targets. The RMM connection itself is on the Connectors page.
  • Where you see the result: each target's runs on the same page. Your RMM shows the result for each machine.

For what the files are and where they go, see Settings for staff machines.

How a push works

  1. Add a target on the Coding tools page. Pick the tool, the operating system and the machines. A machine group is an organization, a site or a device, whichever that tool uses.
  2. Turn the target on. A target starts switched off.

StackJack uses your organization's shared default connection for that tool. That is the connection on the Connectors page.

A push installs the files only if every file passes its check. It keeps a backup of what it replaces. It reports one result line for each machine and never the settings themselves.

When a push runs

A push runs when an administrator presses Push now. With automatic redeploy on, which is the default, a push also runs when the approved or denied list changes or the token is rotated. Several changes close together become one push.

After three failed pushes in a row, a target is paused until an administrator resumes it. Some tools cannot take a settings payload as large as a long approved list. The page then says so, and the download is the way to deliver it.

Tools where you import a script once

For these tools you import StackJack's installer script once. Then you enter its id on the target. The page offers the script for each operating system.

  • NinjaOne. Add the downloaded script to the script library: PowerShell for Windows, shell for macOS and Linux. It takes one parameter. Enter its numeric id.
  • Datto RMM. Add a component from the downloaded script and give it one variable named STACKJACK_PAYLOAD. Enter the component's id.
  • N-able N-central. Add the downloaded script to the repository with one parameter named Payload. Enter its id.
  • SuperOps. Add the downloaded script with one argument. Enter its id.
  • ConnectWise Automate. Build a script with one PowerShell step that runs the downloaded installer and one parameter named Payload. Enter its id.

Tools where StackJack makes the script itself

  • ImmyBot and Action1. You import nothing. StackJack creates and keeps its own script in the tool, named "StackJack AI Governance endpoint settings", with the system and the target, and runs it.
  • Addigy. You import nothing. StackJack sends the installer as the command itself.
  • Jamf Pro. You import nothing. StackJack keeps its own script there and one policy that runs it on your Macs at their next check-in. It deletes its older policy and script when the settings change. A Mac that is off waits.

A settings payload that is too large for one script is refused. The download is the way to deliver it.

The script or command StackJack sends holds the settings, including the token your staff machines report with. Anyone who can read scripts or commands in ImmyBot, Action1, Addigy or Jamf Pro can read that token. The same token is already readable on every staff machine that receives the settings. Rotating it stops the old one after seven days.

Which machines each tool reaches

  • Addigy and Jamf Pro reach Macs only.
  • ConnectWise Automate reaches Windows computers only.
  • N-able N-central does not deliver to Linux.

Tools StackJack does not deliver through

  • N-able N-sight can only run a task you created inside it, and cannot be given the settings. It has no delivery.
  • Atera publishes no way to run a script, and Syncro publishes no path for it. Neither has one.

Use the download for those tools.

Microsoft Intune

An Intune push needs two things: your own Microsoft sign-in on the Connectors page, connected at the full permission level, and one or more Entra groups whose devices should receive the settings. A push acts in your directory, so it runs only when you press the button and never by itself. When the lists change, the page shows "Update ready: push again". Windows devices receive a script. Macs receive a profile.

Not every machine can be reached this way

Codex on Windows has no system-wide place for its reporting settings. On Windows that file is a download for each user's home folder, and no delivery tool installs it. A tool that is not in the list, such as Jamf Pro, N-sight, Syncro or Atera, can still use the download. Any MDM can install macOS profiles.

Troubleshooting

What you seeWhat to check
The push cannot reach your toolStackJack uses the shared default connection for that tool. Check that it exists and works on the Connectors page.
A target is pausedThree pushes in a row failed. Read the runs, fix the cause and resume it.
The page says the payload is too largeUse the download for this tool.
One machine did not get the fileRead that machine's result in your RMM. The push reports one line per machine.
"Update ready: push again" on an Intune targetThe lists changed. Press the button. Intune never pushes by itself.

Next