sync: auto-sync from HOWARD-HOME at 2026-05-05 18:51:23

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-05-05 18:51:23

clients/cascades-tucson/session-logs/2026-05-05-howard-chef-pc-slow-and-mdirector-ram.md

@@ -253,3 +253,18 @@ Changes:
 - Bumped `Last updated:` header to 2026-05-05 with a one-line explanation that the roster was previously stale.
 
 Closes the "Update `clients/cascades-tucson/CONTEXT.md` 'Agents currently enrolled' section" pending item from the original 2026-05-05 chef-pc-slow session.
+
+---
+
+## Update: 18:50 PT — Hostname-to-user mapping deferred (user list incoming)
+
+Started a remote-PowerShell probe across the 9 online unmapped Cascades agents (CIM read-only — `Win32_ComputerSystem.UserName`, recent profile dirs, manufacturer/model). 9 commands queued via GuruRMM `POST /api/agents/{id}/command`. Howard interrupted before any results were consumed — Cascades will provide a user list directly, which is faster and more authoritative than inferring from interactive logons (especially for shared-desk machines and devices that don't have a current logged-on user).
+
+The dispatched commands are harmless (read-only CIM queries) and will complete on their own when each agent picks them up; their results sit in GuruRMM unused. No state on the workstations was modified.
+
+CONTEXT.md "Agents currently enrolled" still flags the 13 unmapped hosts as `(unmapped — needs hostname rename)` / `(unmapped)`. Once Howard provides the user list, fold the mappings back into that table in one pass.
+
+Pending (replaces the implicit "do per-machine probes" plan):
+- [ ] Receive Cascades hostname-to-user list from Howard
+- [ ] Update CONTEXT.md unmapped rows in one pass
+- [ ] Tie into the fleet-wide hostname-rename plan (Intune naming convention) once user mapping is in hand