sync: auto-sync from GURU-5070 at 2026-06-15 17:49:06

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-15 17:49:06
This commit is contained in:
2026-06-15 17:49:23 -07:00
parent 9b4e86cdfc
commit 4ef6a9a3b0
5 changed files with 66 additions and 2 deletions

View File

@@ -146,3 +146,4 @@
- [Physical access codes -> vault + wiki pointer](feedback_physical_access_codes.md) — alarm/lockbox/door codes go in vault clients/<slug>/physical-access-<location>.sops.yaml (kind: physical-access) + a `## Physical Access` pointer section in the client wiki; never plaintext. First entry: Peaceful Spirit NW.
- [CT Thoughts backlog](feedback_ct_thoughts_backlog.md) — ClaudeTools harness ideas go in docs/CT_THOUGHTS.md (trigger "ct thought:"); CT analogue of RMM_THOUGHTS. Don't build until explicit go. First entry = ClaudeTools 3.0 web co-work vision.
- [AI-auth product boundary](project_ai_auth_product_boundary.md) — ClaudeTools/ClaudeTools 3.0 = internal-only, per-person subscription OAuth ok; GuruRMM = sellable, customer brings own API key (never ACG's subscription); backend dev = internal. Anthropic ToS bans subscription auth in third-party products.
- [RMM SYSTEM context can't see user mapped drives](feedback_rmm_system_context_mapped_drives.md) — RMM runs as SYSTEM; `Test-Path F:\` etc. is False even when the user's mapped/redirected drive exists. Diagnose mapped-drive/redirect issues in `context:user_session`. Elevated apps (e.g. QB DB Server Manager "unable to retrieve root folder") need `EnableLinkedConnections=1` + reboot.

View File

@@ -0,0 +1,28 @@
---
name: feedback-rmm-system-context-mapped-drives
description: RMM commands run as SYSTEM and cannot see a user's mapped network drives / network-redirected folders — diagnose those in user_session; elevated apps need EnableLinkedConnections.
metadata:
type: feedback
---
GuruRMM agent commands execute as **SYSTEM**, which has **no access to a logged-on user's
mapped network drives or network-redirected shell folders**. A `Test-Path F:\` (or a
redirected Desktop on a UNC) will return **False under SYSTEM even when it exists fine in the
user's session** — do not conclude the drive/folder is "missing/dead" from a SYSTEM check.
**Why:** Mike corrected exactly this on LS-1 (Lonestar) 2026-06-15 — I called `F:\FolderRedirection\Robin\Desktop`
a dead drive; it's actually `F: -> \\tower\Data` (folder redirection to the Unraid "Tower"
server), present with 102 items in Robin's session.
**How to apply:**
- For any mapped-drive / network-redirected-folder / per-user-path question, dispatch the RMM
command with `"context": "user_session"` (runs under the active user's token) and verify with
`whoami`, `net use`, `Get-PSDrive`.
- Separately: an **elevated** app (UAC) gets a different token that also lacks the user's mapped
drives. Symptom seen: QuickBooks Database Server Manager ("Add" folder) throws
`FolderBrowserDialog ... Unable to retrieve the root folder` because its root (the Desktop) is
on an unmapped `F:` in the elevated token. Fix: set
`HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections = 1`
(DWORD) and reboot — shares the mapped drives across the user's elevated + normal tokens.
Related: [[feedback_tmp_path_windows]]