azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from HOWARD-HOME at 2026-05-29 12:35:52

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-05-29 12:35:52
This commit is contained in:
Howard Enos
2026-05-29 12:36:01 -07:00
parent 0eeef72e01
commit 6821d4d6fc
3 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.claude/memory/feedback-rmm-unc-path-encoding.md Normal file
View File

@@ -0,0 +1,19 @@
---
name: feedback-rmm-unc-path-encoding
description: RMM PowerShell UNC paths via user_session context lose one backslash when using string literals — must build with [char]92
metadata:
type: feedback
---
Never use `"\\CS-SERVER\..."` string literals in PowerShell scripts dispatched via GuruRMM `user_session` context. The backslash gets halved somewhere in the encoding pipeline, producing `\CS-SERVER\...` (a local path) instead of the UNC `\\CS-SERVER\...`.
**Why:** The `user_session` execution wrapper appears to process escape sequences in the script text differently than `system` context, stripping one backslash from `\\`.
**How to apply:** Always build UNC paths explicitly when using user_session:
```powershell
$bs = [char]92
$base = "${bs}${bs}CS-SERVER${bs}homes${bs}Username"
```
This constructs `\\CS-SERVER\homes\Username` correctly regardless of context.
The `system` context (offline hive reg query) showed correct `\\CS-SERVER` output, so the issue is specific to `user_session`.