Installing the rig agent

Each rig PC runs a small Windows agent that PitwallOS drives over HTTPS. The agent loads circuits, cars, and sessions on cue from the admin console; it never opens an inbound port, so it doesn't need any firewall changes on your side.

1. Download the installer

In your admin console, go to Settings → Rigs & agents and click Download installer. You get PitwallOS-Agent-Setup-X.Y.Z.exe (~25 MB, signed). The same page shows the currently published version, so you can double-check against a rig's heartbeat later.

2. Generate a setup token

On the same settings page, click Generate setup token. The token is one-shot and expires after 24 hours — anyone with the token can register a rig against your venue, so treat it like a password. It only lets an attacker registera rig; approval still needs an admin click (step 5), so a stolen token doesn't start eating bookings.

3. Run the installer on the rig PC

Double-click PitwallOS-Agent-Setup-X.Y.Z.exe. The wizard has three short pages:

1. Where to install the agent (default %ProgramFiles%\PitwallOS\Agent).
2. Where Assetto Corsa lives — auto-detected from Steam, override if you installed to a different drive.
3. Where Content Manager lives — also auto-detected.

The installer drops pitwallos-agent.exe and pitwallos-setup.exe under %ProgramFiles%\PitwallOS\Agent, registers the Scheduled Task \PitwallOS\PitwallOS Rig Agent (runs at logon, as the interactive user), and adds a Start- menu shortcut called PitwallOS Setupthat opens the agent's setup GUI. The agent starts immediately — no reboot needed.

Silent / unattended install

For RMM tools or pre-imaging, the installer accepts standard Inno Setup switches plus a handful of PitwallOS-specific flags:

PitwallOS-Agent-Setup-X.Y.Z.exe /VERYSILENT /SUPPRESSMSGBOXES \
  /AC="D:\Steam\steamapps\common\assettocorsa" \
  /ACDOCS="D:\AC-Docs" \
  /CMPATH="D:\Tools\Content Manager.exe" \
  /SETUPTOKEN=ots_abc123... \
  /BACKEND=https://your-venue.pitwallos.com

Every path flag is optional — anything you skip falls back to auto-detection. Passing /SETUPTOKEN and /BACKEND together lets the installer bind the rig on its own; without them, an operator opens the setup GUI (step 4) and pastes the token by hand.

4. Bind the rig to your venue

Open the PitwallOS Setup shortcut on the rig PC. On the Register rig tab, paste your setup token and click Bind. The agent exchanges the token for a long-lived rig token (stored encrypted via Windows DPAPI) and starts heartbeating.

The same tab is how you re-bind later — if you re-image the PC or swap the disk, open the setup GUI, paste a fresh setup token, and click Bind. The corresponding rig row in the admin console keeps its history.

5. Approve the rig

Back in the admin console at Settings → Rigs & agents, the newly- bound rig shows up under Pending approval. Give it a friendly name (e.g. Rig 3) and click Approve. If you're adding a spectator rig instead, use the Spectator role picker here.

Approval is required before the platform will route any bookings to the rig — this prevents a stray PC from binding to your venue and consuming sessions.

6. Confirm the heartbeat

Once approved, the rig gets a coloured dot on Sim Control:

• Green— heartbeat in the last ~75 seconds, ready to launch.
• Grey— no heartbeat lately. Rig PC might be off, offline, or the Scheduled Task didn't start. See troubleshooting.
• Red— heartbeating but the last command failed. Click into the rig to read the error.

7. Per-engine prerequisites

The agent is multi-title (agent v3.0.0+): a single rig PC can run Assetto Corsa, rFactor 2, and Le Mans Ultimate (once it ships) from the same install. Each engine needs its own setup pass before PitwallOS will route bookings to it.

Assetto Corsa

• Install AC from Steam. The installer auto-detects %PROGRAMFILES(X86)%\Steam\steamapps\common\assettocorsa; override on step 2 of the wizard, or later on the Engine paths tab of the setup GUI if you moved the install.
• Install Content Manager + Custom Shaders Patch per the pinned versions in the AC config guide. Newer CSP previews can break the agent's INI parser.

rFactor 2

• Install the rF2 client from Steam (App ID 365960). The dedicated server (App ID 400300) is installed automatically by the agent on first heartbeat — no operator step, no SteamCMD needed on your end.
• Point the agent at the rF2 Install dir and UserData dir on the Engine paths tab of the setup GUI. rF2 sometimes puts UserData under Documents and sometimes under the install dir; the agent needs both.
• Full walkthrough of the rF2-specific bits (shared-memory plugin, .rfmod cache, port requirements): see rFactor 2 configuration.