Doing It Right When There's a Shortcut

October 27, 2026

Every time we onboard a new client, there's a moment where you find out what you're really walking into. With one recent client, that moment came fast. Their domain controller was offline.

The previous IT provider never finished onboarding them. Nobody had access to the AWS account the DC lived in. The card on file expired, AWS shut the account down for non-payment, and the DC went down with it.

Their fix was to pull every computer off the domain and point DNS at 8.8.8.8. People could get back online, so it looked solved. It wasn't. They'd just stopped looking at it.

I understand how that happens. Tracking down who owns an account is slow, frustrating work. But that shortcut left the client with no central identity, no policy enforcement, and a security gap they didn't even know about.

So we took the long way. I followed the trail back to an IT provider the client had worked with five and a half years earlier, got access to the account restored, brought the DC back up, and rejoined every machine to the domain.

The technical part wasn't what made it hard. What made it hard was staying patient when there was a shortcut sitting right there. Ownership means treating a client's environment like it's your own, and doing things the right way even when nobody would notice if you didn't.