20+ years in IT.
Still finding bugs nobody documented.
Senior Engineer. MSP veteran. The person who Googles the error, finds nothing, figures it out anyway — and now writes it down so you don't have to.
I'm Chris — a Senior Engineer with over 20 years of experience across nearly every corner of IT. My roots go back to Windows NT, building custom machines young and spending every free moment in my school's Tech Room tearing things apart and putting them back together. That obsession never left.
Most of my career has been spent in MSP and consulting environments, which means no two days look the same. I've led Intune and Autopilot deployments, managed cloud migrations to Azure and AWS, handled Tenant-to-Tenant and Google Workspace to M365 migrations, and guided teams through projects that most documentation doesn't come close to covering. When I was in college full-time studying Network and Communications Management, I was simultaneously running my own IT consulting business — managing 200+ business and residential networks. That kind of environment teaches you to figure things out fast, with no safety net.
That's the thread running through everything I do: I hit problems that don't have a documented answer, I figure them out, and I move on. For years I moved on without writing anything down. This blog is me fixing that habit — for my own benefit and for anyone else who's stared at a vague Intune error at 3AM wondering if they're the only one who's ever seen it.
Spoiler: you're not. And now there's a runbook for it.