# 2026-07-14 — Dataforth: Sage GURU credential + Sage printing fix (DESKTOP-U8PHS72 / SAGE-SQL)

## User
- **User:** Howard Enos (howard)
- **Machine:** Howard-Home
- **Role:** tech

## Session Summary

Started with a lookup for a Sage application login for Dataforth. No entry existed in the SOPS
vault (`clients/dataforth/` had only server/infra creds) or wiki. Dataforth staff reset the
password on their Sage `guru` user; the credential was vaulted at `clients/dataforth/sage`
(username `guru`). Initial value was corrected twice per user updates — final password is
`Itword26!` (confirmed intentional, not a typo). Login later verified working.

The real issue then surfaced: DESKTOP-U8PHS72 could not print from Sage — Sage showed no
printers. Investigation via GuruRMM: Sage Pro 200 ERP 2010 (`S:\sbt\sbtw.exe`, Visual
FoxPro-based) is NOT installed on the workstation; users RDP to SAGE-SQL (192.168.0.153, RDS
Session Host) and run Sage there, so Sage printers = RDP-redirected printers. The affected user
dlopez (new AD account created 2026-07-06) had two long-running RDP sessions on SAGE-SQL
(session 4 active since 7/13 + session 9 stale disconnected) with ZERO redirected printers —
each reconnect re-entered the stale sessions. His client-side `Default.rdp` correctly had
`redirectprinters:i:1`. Mike noted a registry change to RDP behavior had been made previously
(before this session) that required a fresh logon to take effect.

Fix: logged off both dlopez sessions on SAGE-SQL via GuruRMM. Fresh RDP connection brought
printer redirection up correctly; Mike verified in Sage as the `guru` user — printers listed
and selectable. Resolved.

Wrote Syncro ticket #32552 (Dataforth Corp), resolution comment (registry-fix detail
intentionally omitted per Mike), billed 0.5 hr remote labor against the prepaid block
(25.75 → 25.25 hrs), invoice 1651043602 ($0.00 prepaid), ticket marked Invoiced, block-hours
note set on invoice, bot alert posted.

## Key Decisions

- Vaulted the Sage credential at `clients/dataforth/sage` even before testing — capture-first
  policy; updated in place when the username/password were corrected.
- Diagnosis order: workstation recon → server-side RDS policy/printers → per-user RDP files →
  session source IPs → Sage process identification. Ruled out server policy (fDisableCpm=0, no
  printer cap), client config (redirectprinters:i:1 present), and driver-level issues before
  landing on stale sessions.
- Registry fix left out of ticket notes per Mike's explicit request.
- Ticket created directly in Resolved status (work already complete), then Invoiced after billing.

## Problems Encountered

- Inline JSON dispatch to RMM failed on `\\` escapes ("invalid escape") — switched to
  `ps-encoded.sh` file-based encoded dispatch per the /rmm skill guidance.
- Vault push rejected (remote ahead) — `git pull --rebase` then push, clean.
- Initial theory (VFP/Sage Pro can't use Easy Print queues) was plausible but superseded:
  Mike reproduced the failure in a session that HAD Easy Print printers, then revealed the
  prior registry change; stale sessions predating it were the actual blocker. Note: session
  defaults on SAGE-SQL are all "Microsoft Print to PDF" and native Brother/HP drivers are NOT
  installed server-side (event 1111s) — may resurface as a future issue.

## Configuration Changes

- Vault: created `clients/dataforth/sage.sops.yaml` (then updated username/password) — pushed
  (final vault commit 73cf333).
- SAGE-SQL: logged off dlopez sessions 4 and 9 (only change made this session — no
  settings/drivers/registry touched today).
- Scratch recon .ps1 files created and deleted in repo root.

## Credentials & Secrets

- **Sage Pro ERP login (Dataforth):** username `guru`, password `Itword26!` — vaulted at
  `clients/dataforth/sage` (kind generic, notes describe SAGE-SQL usage). Password reset by
  Dataforth staff 2026-07-14; verified working by Mike in Sage. NOTE: password is `Itword26!`
  ("Itword", NOT "Itworks") — confirmed intentional.

## Infrastructure & Servers

- DESKTOP-U8PHS72 = 192.168.0.48, Dataforth D2, GuruRMM agent 25a75932-31cf-4b33-b94b-f4c404830877.
  Users: dlopez (console), kellynwackerly. Local printers: Brother DCP-L2550DW (USB002, default
  for both users), HP LaserJet Pro 400 M401n "Kellyn Desk" (USB001), ASSEMBLY-LJD2 + NPI3EDBF9
  HPs (WSD/network).
- SAGE-SQL = 192.168.0.153, RDS Session Host, GuruRMM agent 120ba7bf-8544-48a0-98a1-40ed5cdd3e1f.
  Sage Pro 200 ERP 2010 at `S:\sbt\sbtw.exe` (share C:\sage). ~10 concurrent RDP users.
  Kellyn connects from 192.168.0.68 (different machine than U8PHS72).
- RDS printer redirection: enabled, no policy key, no MaxPrintersPerSession set. All redirected
  queues use "Remote Desktop Easy Print". Native Brother/HP Universal drivers NOT installed on
  server (event 1111 "driver unknown"). Every user's session default printer = Microsoft Print
  to PDF.

## Commands & Outputs

- Vault: `vault-helper.sh new/set clients/dataforth/sage`; read with
  `vault.sh get-field clients/dataforth/sage credentials.password`.
- RMM quote-safe dispatch: `bash .claude/scripts/ps-encoded.sh rmm <agent-id> <script.ps1> --timeout 120`
  (inline JSON with `\\` fails the API's JSON parse).
- Session logoff (SAGE-SQL): `logoff 9 /v; logoff 4 /v` — logoff returns nonzero exit (status
  "failed") but works; verify with `query user`.
- Session source IPs: TerminalServices-LocalSessionManager/Operational events 21/25.
- Per-user default printer: `HKU\<SID>\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device`.

## Pending / Incomplete Tasks

- None for this issue. Watch-item: if Sage printing complaints recur (esp. for the VFP app vs
  Easy Print queues), next step is installing native Brother DCP-L2550DW + HP Universal PCL 6
  drivers on SAGE-SQL. Also `staff` share still missing on FILES-D1 (pre-existing note).

## Reference Information

- Syncro ticket #32552 (id 113826861) — https://computerguru.syncromsp.com/tickets/113826861
- Invoice 1651043602, $0.00 prepaid, line 43262662 (0.5 hr Labor - Remote Business), Dataforth
  prepay block 25.75 → 25.25 hrs.
- Vault: `clients/dataforth/sage` (vault repo commit 73cf333).
- Related session log: `2026-07-06-mike-sage-sql-peter-session-reset.md` (prior SAGE-SQL session work).
