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

sync: auto-sync from HOWARD-HOME at 2026-07-07 06:53:34

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-07-07 06:53:34
This commit is contained in:
Howard Enos
2026-07-07 06:54:02 -07:00
parent 5968ee9231
commit 8854a584f3
4 changed files with 140 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
.claude/memory/reference_windows_edition_upgrade_rmm.md
View File

@@ -30,6 +30,25 @@ the offline window. `is_connected` is null fleet-wide — track `last_seen` age,
**Gotcha 3 — the ACG MAK `infrastructure/windows-pro-mak` is a Pro-for-WORKSTATIONS MAK** (mislabeled
"Pro"). `slmgr /ipk` of it on a Professional machine AUTO-UPGRADES the edition to ProfessionalWorkstation
(a strict superset of Pro). If a client genuinely needs *plain* Pro, this key will over-shoot to PfW —
there is no plain-Pro MAK in the vault. Billing: each activation consumes one MAK count = $99 to the
customer (ACG-internal machines: no invoice, still burns a count).
(a strict superset of Pro), live, **no extra reboot** (verified DALLAS 2026-07-07). If a client genuinely
needs *plain* Pro, this key will over-shoot to PfW — there is no plain-Pro MAK in the vault. Billing:
each activation consumes one MAK count = $99 to the customer (ACG-internal machines: no invoice, still
burns a count).
**Gotcha 4 — `changepk.exe` TIMES OUT under SYSTEM but STILL flips the edition. Do NOT treat the timeout
as failure — VERIFY EditionID.** Run as SYSTEM via `/rmm`, `changepk.exe /ProductKey <key>` does not return
cleanly (the RMM command comes back `failed` / exit -1 `Command timeout`, or your Start-Process/`&` wrapper
hangs to the agent timeout), yet the registry `EditionID` flip to `Professional` DID happen. Always confirm
with a one-liner (`Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' EditionID`) before
concluding anything — if it reads `Professional`, proceed to the finalize reboot; the running OS still
reports Home in `Win32_OperatingSystem.Caption` until that reboot. (Verified DALLAS 2026-07-07 — the
`changepk` command timed out but EditionID was already `Professional`.)
**Gotcha 5 — Modern Standby laptops (S0 Low Power Idle) drop the RMM/SC agent when idle/lid-closed, which
mimics an endless reboot.** On a Core Ultra / S0-only machine, idle or a closed lid drops Wi-Fi -> agent
offline for long stretches (looked like a 25-min "slow reboot"; the box had actually been up 25 days and
never rebooted). Before a reboot-driven upgrade on a laptop, pin it awake first:
`powercfg /change standby-timeout-ac 0; powercfg /setacvalueindex SCHEME_CURRENT SUB_BUTTONS LIDACTION 0;
powercfg /setactive SCHEME_CURRENT` (AC only — safe; DON'T lid-nothing on DC/battery). A command dispatched
to an already-offline agent goes `pending` and fires (uncontrolled) on next wake — cancel stale ones with
`/rmm cancel`. NOTE: an RDP *target* laptop must STAY awake to be reachable, so keep the AC no-sleep in place.