Files
claudetools/clients/lens-auto-brokerage/docs/gururmm-deployment.md
Howard Enos c757318ffa sync: auto-sync from HOWARD-HOME at 2026-06-01 10:26:59
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-01 10:26:59
2026-06-01 10:27:12 -07:00

5.0 KiB

Len's Auto Brokerage — GuruRMM Agent Deployment

Status: IN PROGRESS (started 2026-06-01, Howard) Method: ScreenConnect (workgroup — no AD domain, GPO not used) GuruRMM site: Len's Auto Brokerage / "Main" — site code UPPER-STAR-2820 (this code IS the enrollment key) Target: ~10 Windows endpoints + the EOL lab-server (enroll to monitor until decommission)

Enrollment command (run on each endpoint via ScreenConnect, ELEVATED PowerShell)

Standard (modern Windows 10/11 / Server 2016+):

irm https://rmm.azcomputerguru.com/install/UPPER-STAR-2820/windows | iex

Explicit fallback (if the hosted installer is blocked):

$u='https://rmm-api.azcomputerguru.com/downloads/gururmm-agent-windows-amd64-latest.exe'
$d='C:\Windows\Temp\gururmm-agent.exe'
Invoke-WebRequest $u -UseBasicParsing -OutFile $d
& $d install --server-url 'wss://rmm-api.azcomputerguru.com/ws' --api-key 'UPPER-STAR-2820'

The agent installs as a SYSTEM service and auto-registers on first WS connect; it appears in the dashboard under Len's Auto Brokerage / Main within seconds.

lab-server (Server 2008 SP2, 192.168.1.241) — SPECIAL HANDLING / likely fails

Server 2008 SP2 (6.0.6002) is EOL and predates TLS 1.2-by-default + the modern Windows runtime the Rust agent is built against. Expect problems:

  1. TLS: old PowerShell defaults to TLS 1.0 — the irm | iex download will fail. Force TLS 1.2 first:
    [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
    $u='https://rmm-api.azcomputerguru.com/downloads/gururmm-agent-windows-amd64-latest.exe'
    $d='C:\Windows\Temp\gururmm-agent.exe'
    (New-Object Net.WebClient).DownloadFile($u,$d)
    & $d install --server-url 'wss://rmm-api.azcomputerguru.com/ws' --api-key 'UPPER-STAR-2820'
    
  2. Binary may not run at all on 2008 SP2 (missing API sets / UCRT). If it errors on launch, that is EXPECTED — do not burn time on it. Note the failure here and rely on the planned decommission instead. (This is consistent with the box being retired anyway.)

Reconciliation — 2026-06-01 (Syncro asset list vs GuruRMM)

Howard enrolled all machines online in the last ~2 months via ScreenConnect. Source list = Syncro assets (15 machines). Logic: a machine in Syncro but absent from RMM = offline >2 months (being removed from Syncro). GuruRMM shows 8 online agents under Len's / Main.

Enrolled & online (8)

Hostname (RMM) Syncro list match Notes
DESKTOP-0J55V6L DESKTOP-0J55V6L Win 11 Home
DESKTOP-JDQMLCE DESKTOP-JDQMLCE Win 11 Pro
EV-DAWG EV-DAWG Win 11 Pro
Josh-Lens JOSH-LENS Win 11 Pro
LAB-Becky LAB-BECKY Win 10 Pro
LAB-DAWN LAB-DAWN Win 11 Pro
LAB-MADONNA LAB-MADONNA Win 11 Pro
LAB-SVR = DESKTOP-BMBTQLI (rebuilt) Win Server 2019. CONFIRMED via SN 3M1D1T12PD + IP .81: this is the old DESKTOP-BMBTQLI rebuilt to Server 2019 (installed 4/15/2026) and renamed. CURRENT production server.

Missing from RMM = offline >2mo / Syncro-deleted (no action)

DESKTOP-LJ825H1, LAB-005252, MATT, PARKER. (DESKTOP-BMBTQLI is NOT missing — it was rebuilt + renamed to LAB-SVR, which IS enrolled.)

Resolved 2026-06-01 (Howard)

  • LENS-SV = the new server = LAB-SVR in RMM. One physical box (HPE MicroServer Gen10+ v2, SN 3M1D1T12PD, Server 2019, IP .81): Syncro tracks it as LENS-SV, GuruRMM enrolled it as LAB-SVR, the old overview doc called it DESKTOP-BMBTQLI. All the same machine — enrolled & online. Accounted for. (Minor: RMM hostname LAB-SVR vs Syncro name LENS-SV — cosmetic; rename later if desired.)
  • LAB-SERVER (Server 2008, .241, old Xeon E3-1220 v3) — NOT enrolling. Agent will not install on Server 2008 (confirmed decision). Leave it; decommission will handle it.

Deployment status: COMPLETE & RECONCILED

All machines online in the last ~2 months are enrolled (8 agents). Offline>2mo machines are being removed from Syncro (no action). desertRV machines tracked separately. Optional: walkthrough + user self-installer to catch any straggler.

desertRV machines (do NOT belong to Len's)

  • DESERTRVSERVER — online, NOT in GuruRMM anywhere; no desertRV client/site exists yet. Needs a desertRV group created + fresh enroll. Tracked separately.
  • DRV-TK-DESKTOP — DRV- prefix, also a likely desertRV machine; absent from RMM.

Catch any stragglers (Howard's plan)

  • Physical walkthrough of the site to spot any machine missed.
  • Hand users the self-installer (site code UPPER-STAR-2820) so they can enroll their own machines.

Verification

After a batch, confirm enrollment count from the RMM API (or ask Claude /rmm to check):

  • Client "Len's Auto Brokerage" bc76984f-8dc9-42e7-b978-c8def1143144, site "Main" d8f69cd8-5c42-43bc-ae45-9cc6078d37fb.
  • Done when all live endpoints show online/heartbeating.

Reference

  • Network 192.168.1.0/24, WAN 174.77.67.237. ScreenConnect present.
  • Installer download verified live 2026-06-01 (HTTP 200, ~4.9 MB, built same day).