My New Work Laptop Was Not Quite What It Said on the Box
Setting up a business laptop the way I would for a client with Autopilot, Intune and Entra join, and what the laptop itself turned out to be hiding.
Write-ups from home lab work and lessons learned.
Setting up a business laptop the way I would for a client with Autopilot, Intune and Entra join, and what the laptop itself turned out to be hiding.
Three staged modules and a year-old wording bug went into the manual at once, because I decided against a version-bump chain that would leave v1.4 stale the day it shipped. What got added, what got corrected, and the placement call I made against my own source material's advice.
Three used office PCs, one new build, and two days where DNS did not work. Building a Proxmox cluster from scratch, including the parts I got wrong.
How six Claude Projects that couldn't see each other turned into one folder Claude can read directly, why that finally makes 'second brain' mean something, and three mistakes I only found by running the system cold.
Five days, three versions, and roughly 57,000 more words. What got added, what got corrected, and the one instruction in my own source material that I did not follow.
A wildcard DNS record, an allow-list entry, and a DLP policy in simulation mode. Different products, same failure: the diagnostic still returned an answer, and the answer was wrong.
Thirty-seven thousand words of operational reference, built around one rule: search the tag, not the prose. Here is why I stopped keeping notes and started keeping a manual.
Round 1 was tutorial-led and full of failures. Round 2 was a rebuild from my own playbook, timed, to find out whether the documentation actually worked.
No posts match this filter.