
Why Find-UnknownSID Left My Monorepo
I moved Find-UnknownSID out of my scripts repo so it could have releases of its own. The audit before the move found docs for a tool that never existed, and the loader hit case-insensitive names.

I moved Find-UnknownSID out of my scripts repo so it could have releases of its own. The audit before the move found docs for a tool that never existed, and the loader hit case-insensitive names.

I rebuilt my old Find-UnknownSID script as OrphanedSid, a PowerShell Gallery module with three commands, then ran the published 1.0.1 against a lab domain from discovery through removal and back.

My Surface Pro 11 put a Copilot key where Right Ctrl belongs, so I made it Right Ctrl with Keyboard Manager. That grew into a PowerToys tour, plus why Windows’ new Right control option did nothing here.

I saw MarkX 0.1.4 announced with Hugo support and pointed it at this blog, where Hugo already renders every post. It had nothing to add. It fits elsewhere: tables as data, link audits, objects as tables.

I shipped CaOutcome with 204 passing tests and a README example that gave thirteen wrong answers. Every test passed the collection by parameter. Maester pipes it, and PowerShell unrolls a piped array.

I found MC1448379 while hunting for my next post: on November 3, every memberOf group, administrative unit and auto-assignment policy stops updating. Microsoft says grep for the word. I wrote a parser.

On 10 September my UDM’s WAN port renegotiated to 100 Mbps and stayed up. No alert fired, and the house sat at 178 ms for hours. I traced it to a cable and wrote a poller to catch it next time.

One VM running qBittorrent was pulling about 98% of my WAN traffic. I capped it in qBittorrent, shaped the WAN with Smart Queues and aimed a UniFi throttle at it. Only some of those limits bind today.

I sent a query from my IoT VLAN to 8.8.8.8 for a name only my Pi-hole knows, and Pi-hole answered. Then I went after the encrypted DNS paths a port 53 redirect can’t touch.

One allow rule on my IoT VLAN hadn’t passed a packet in two months, and it took two fixes to find out why. This is the rule set, the test I ran from inside the VLAN, and the two holes it found.