Scripts that never wait for a prompt
The LiveConnect suite is 21 standalone PowerShell scripts built for Kaseya VSA LiveConnect terminals. Each runs entirely from parameters — no menus, no prompts, no interactive calls — so you can drop one into a terminal and walk away.
Why it's a separate suite
The main Technician Toolkit is built around
interactive menus, Read-Host prompts, ReadKey
pauses, and Clear-Host calls — the things that make it guided and
approachable when a technician is at the keyboard. The LiveConnect PowerShell shell cannot
handle any of those. The moment it hits an interactive call, the session hangs or errors out.
So these scripts are not ports — each one was written from scratch to guarantee no interactive calls are present. They are not launched from GRIMOIRE and share no code with the main scripts. All behavior is controlled by switches and arguments, all output is plain status lines, and the report path is printed clearly at the end of every run.
The design rules
Every script in the suite follows the same pattern, without exception:
Every input is a parameter — nothing waits for typed input.
No key-wait calls of any kind that would hang the session.
Output is never wiped mid-run, so the whole transcript survives.
The header is plain Write-Host lines — no menu chrome.
[OK], [!!], [*], and [ERROR] prefixes throughout.
Every run prints its report/log path on its own line for easy retrieval.
No dependency on other toolkit scripts or a shared module.
Five functional categories
Software installs, system diagnostics, account audits, baseline enforcement, and Windows Update — all non-interactive.
Persistence, TPM and BitLocker readiness, Defender posture, SMART, firmware, and battery health.
Wi-Fi profiles, VPN inventory, certificate expiry, and subnet discovery with port scanning.
OneDrive Known-Folder-Move readiness, Outlook archive discovery, and a unified handoff diagnostic.
Read-only disk audits, parameter-driven cleanup, and service / task / event-log health.
How a run works
Open a PowerShell terminal through LiveConnect, paste a script's one-liner — it fetches the
.ps1, sets execution policy for that session only, and runs
immediately — and append any parameters after & $f. Switches
and arguments control every option, so nothing waits for input and the script is safe for
unattended runs. When it finishes, the output path prints on its own line:
REPORT PATH: C:\Temp\PROBE_20260416_103045.html
Pull that file back through LiveConnect's file transfer or a mapped share. Most scripts
default their report folder to C:\Temp and accept a
-ReportPath (or -LogPath) override —
point it at a network share and the report lands there directly.
Relationship to the main toolkit
Each LiveConnect script is a counterpart to a tool in the main toolkit — NEXUS to CONJURE, AEGIS to PALADIN, ANCHOR to TETHER, and so on. The behavior is the same; what differs is the delivery: no banner, no “press Enter” pause, no browser auto-open, and every option moved onto the command line. A few main-toolkit tools have no counterpart here at all — COVENANT, CIPHER, ARCHIVE, RUNEPRESS and others are interactive by nature or need auth flows LiveConnect can't host. Each script's detail page names its main-toolkit equivalent.