sync: auto-sync from GURU-5070 at 2026-06-11 08:02:42

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-11 08:02:42
This commit is contained in:
2026-06-11 08:02:55 -07:00
parent 6bd3210e21
commit 55445d78dc
4 changed files with 55 additions and 2 deletions

View File

@@ -70,3 +70,19 @@ Per Mike's "Do all", executed the full remediation: (1) restore-printer test wit
- Canonical: `clients/wolkin/`, `wiki/clients/wolkin.md`. Vault: `clients/wolkin/`.
- Syncro ticket #32369 (Remote Work Access Setup).
- Memory: `feedback_client_slug_fragmentation.md`, `feedback_rmm_password_limitation.md`.
## Update: 08:10 PT — DIAG MISMATCH RESOLVED (printer was working)
Mike remoted into RSW-Laptop (real interactive session) and `\front\Sharp` **printed fine**
contradicting the entire RMM-based diagnosis. Root cause of the mismatch: **GuruRMM `user_session`
is a WTS-impersonated, non-interactive token that cannot establish authenticated SMB to a remote
host**, so `net use`/`net view`/`Add-Printer` to `\FRONT` return error 67 / RPC 1702 regardless of
the (healthy) plumbing and even with valid creds. The RMM tests never reflected Julie's real
session. This also reconciles 2026-06-07 (same artifact; the "manual fix" worked only because it
was interactive — there is no SMB-over-ZeroTier wall).
Corrections made: reframed the wiki Patterns entry from "[KNOWN WALL]" to "[MEASUREMENT ARTIFACT]";
flipped Active Work printer item to WORKING; wrote memory `feedback_rmm_user_session_smb_false_negative.md`.
The original "no printers" report was likely transient (pre-reboot / momentary ZeroTier hiccup).
Net: nothing was actually broken; the real deliverables this session were the data-hygiene fixes
(consolidation + vaulting) and capturing two reusable lessons. Still open: rotate `front\julie`.