Who SqlSpnManager is for

The audience

SqlSpnManager is built for the technical people who own (or adjacent-to-own) SQL Server's Kerberos story. You're not a full-time Kerberos expert. You're a SQL DBA, an AD admin, a sysadmin, a security analyst — and SPNs come up two or three times a year, always at the worst time, always when something's already on fire.

Common thread: if you've ever spent two hours debugging an SPN and the answer turned out to be "we needed both the FQDN form AND the NetBIOS form," SqlSpnManager is in scope.

From Keith

I'm Keith Ramsey. For a living, I'm a SQL Server database administrator, and in my own time, I'm a massive PowerShell enthusiast. Thirteen-plus years of SQL Server administration as a craft will do that to you. SqlSpnManager is the second tool I've built on my own time and released to the public — sister to GitEasy — and just like that one, the process of designing for strangers, polishing the code, and writing in plain English just to be helpful has been an absolute blast.

SPNs sit in this strange corner of the job where we know we need to do them, but most of us never really understand them. Someone might hand you a formula that works once, but you don't understand it well enough to know what'll happen the next time — or what the consequences of a small mistake look like. There are whole categories of SPN you don't even know exist until they bite you. BI SPNs. The quirks around AlwaysOn availability groups. FCI Virtual Computer Objects. I've fumbled through all of them more than once.

I'll be honest with you — one time it took me two or three days, trying to make a set of SPNs airtight enough that anyone could pick them up and get them right. I kept finding gaps. I'd find flaws. I had an AI review my work, and the AI couldn't get it right either. I couldn't get it right. I was ready to give up.

I came up with the idea for SqlSpnManager sitting at home one night. I just said to myself: there's gotta be an easier way. I'm going to build something — and I really hope I earn the respect of DBAs and sysadmins, because I think this is too hard. It shouldn't be this hard. There should be a way to make this so a DBA or a sysadmin can just say, “all right, I'll run the tool. Done right. Let's move on.” That's what I tried to build here. I know there are other alternatives out there. This is my way of contributing, and I really do hope it helps you in your day-to-day work.

One important note: for now, I'm the only one making changes to SqlSpnManager. Setting up the right legal paperwork to accept code changes from other people involves a lawyer, and I'd rather put my time and money into shipping more useful code than into legal forms I might have to redo. It's not a permanent stance; I'm just taking it slow. But rest assured, SqlSpnManager is licensed under MPL-2.0, which means anyone is free to pick up the code and continue with it on their own. The project's survival doesn't depend on me.

I completely understand if that decision gives you pause. I'm just a guy figuring out the open-source world one step at a time. The door isn't bolted, it's just closed for today. I am fully open to bug reports and feature ideas — head to the GitHub project and open an Issue, tell me what you need, and I'll read it. No code necessary. If you want to chat, find me at @greenmtnsun on GitHub.

Where to start

SqlSpnManager is currently distributed via the GitHub repository — clone it or download a ZIP. The PowerShell Gallery publish is pending while the owner's pre-publish quality bar gets sorted. The quickstart guide has the 30-second install recipe, and the DBA-facing how-to walks through the everyday flows. If you're on the receiving end of a handoff bundle, see For Sysadmins.