Join the Aabco Tasks Fleet

Which install is this machine?

Both kinds take rtTasks from Makana and run them. Pick one; each has its own command and its own requirements, and nothing from the other one is needed.

Machine manager — runs the compiled task handlers (detailing, End Files, builds) and talks to the Indigo BranchGate app over TCP, so it can drive Indigo on this machine. Installs as a Windows service and installs the apps its queues need. Needs nothing installed first.
JS worker — runs rtTasks whose JavaScript code arrives with the rtTask itself. The same fleet member, minus the TCP link to Indigo BranchGate: for a machine that has no Indigo to drive. Needs Node.js 20 or newer.

Machine manager (servers and build machines)

The Windows service that takes rtTasks from Makana, runs their compiled handlers, drives Indigo through the BranchGate app over TCP, installs the apps its queues need and keeps itself up to date. Open PowerShell as Administrator and run this; it asks your name and email.

[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; irm https://workerhub.aabcoonline.com/downloads/manager-setup.ps1 | iex

Requires: Windows 10/11 or Windows Server 2012 R2 and later. Nothing else — no Node.js, no .NET: the download carries its own runtime. Nothing secret to type or be sent. The first part of the command turns on TLS 1.2 for that window, which older Windows PowerShell does not use by default.

JS worker (installed as aabco-worker)

Takes rtTasks from Makana and runs the JavaScript that comes with each one. It does not talk to Indigo BranchGate, so it suits any machine without Indigo. Open PowerShell and run this. It asks your name and email, then does the rest.

irm https://workerhub.aabcoonline.com/downloads/aabco-worker-setup.ps1 | iex

Requires: Windows 10/11 and Node.js 20 or newer (install the LTS build first; the script stops if it is missing). Nothing secret to type or be sent.

What happens

The worker installs itself Downloaded from this Hub and installed as a Windows service that starts with the machine.
the installer
It asks to join, and says what it can do It declares which kind of worker it is and which tasks it carries handlers for — so an administrator approves a capability, not just a hostname.
the installer
It waits, holding nothing An unapproved machine is not a member of the fleet: no keys, no work claimed. It simply re-checks whether it has been approved.
automatic
An administrator approves it They see your name, your machine, and what it claims it can run, then admit it to a group.
the only step you wait on
It configures itself and starts working The Hub sends the settings and keys it needs. They stay in memory — no key is ever written to this machine's disk — and can be changed centrally later.
automatic, within a minute of approval

Check on your machine

After installing, see where your request has got to. The installer prints your machine's id when it finishes.

What you are agreeing to

Once approved, this worker connects out to the fleet Hub and lets an administrator monitor and manage this machine remotely — viewing performance and running processes, ending processes, browsing, uploading, downloading and deleting files anywhere on disk, and installing the applications its assigned tasks need. Only install it on a machine you are authorised to enrol.

Already installed? It stays idle until approved. To remove it:

Machine manager: Settings → Apps → Indigo Tasks Worker, or from an elevated PowerShell & "C:\Program Files\IndigoTasksWorker\ConsoleApp1.exe" uninstall.
JS worker: Unregister-ScheduledTask aabco-worker, then delete %ProgramData%\aabco-worker.

Join the fleet

What happens

What you are agreeing to