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

sync: auto-sync from HOWARD-HOME at 2026-06-26 08:41:22

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-26 08:41:22
This commit is contained in:
Howard Enos
2026-06-26 08:41:53 -07:00
parent bd52dde6a7
commit 10a90bb213
4 changed files with 83 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
.claude/skills/drive-map/SKILL.md
View File

@@ -99,10 +99,32 @@ bash .claude/skills/drive-map/scripts/drive-map.sh map --host SOME-PC \
--server '\\CS-SERVER\SalesDept' --letter S
```
## CRITICAL — the RMM `verify` is NOT authoritative (read this)
`verify` (and any RMM-dispatched `net use`/`net view`/`Test-Path`/`Get-SmbConnection`)
runs in an agent-injected process that does **not** share the user's real interactive
network-logon session. It **false-negatives**: it can report `error 67 (BAD_NETWORK_NAME)`
/ `RPC 1702` / "not reachable" for shares that are **actually fine**. Proven at Cascades
2026-06-26 — RMM tests failed against a user's daily-use NAS and showed "no connections"
for a client that had a live server-side session with open files; an entire "CS-SERVER SMB
outage" investigation turned out to be this artifact (the server was healthy: `Get-SmbSession`
showed 7 users / 30 open files). It is **inconsistent**, not always-wrong — it passes once a
cmdkey is freshly stored in the active session (as in the successful Karen ALDocs migrate).
**Therefore:**
- A `verify` **failure is NOT proof of a problem.** Never diagnose a "server/share outage"
from RMM client-side SMB results. Validate the SERVER with `Get-SmbSession` /
`Get-SmbOpenFile` (server truth), or do a REAL interactive test on the endpoint.
- A `verify` **success is meaningful** (reachable confirmed). Treat the cred+shortcut
operations (cmdkey, `.lnk`, Quick Access) as the real deliverable — those persist
reliably — and have a human confirm interactively when possible.
- See errorlog friction `rmm/smb-testing` and memory `project_cascades_network_segments`.
## Hard rules
- **Always `verify` first and last.** Confirm the target is reachable for that user
before declaring success — a green `net use` line is not proof of access.
- **`verify` first and last, but treat a FAILURE as inconclusive** (see CRITICAL above) —
confirm interactively before declaring either success or a server problem. A green
`net use` line is not proof of access; a red one is not proof of failure.
- **One user at a time, with a session.** If no interactive user is logged on, stop
and say so; do not "succeed" against SYSTEM's profile.
- **Additive to permissions.** This skill never touches share/NTFS ACLs. If the user