So a few months back I had a client with some wonky stuff happening on their local AD. They were using a .local address for their machines, which in it of itself isn’t that big of a deal, but this particular ADFS was giving me a huge headache as the cmdlet to set up the server just wouldn’t work. It kept giving me a bunch of errors about how the machine isn’t accessible.

Well, after spending a large portion of my Saturday tinkering with it, I figured it all out. For no discernible reason it needed to be run from the machine with just the machine name, which is completely against the procedure Microsoft outlines, but whatever, who am I to question the workings of gods?

Now, this didn’t completely fix my problem, unfortunately I’d set some SPNs up custom as an additional troubleshooting step, and of course being the super skilled IT guy I am, I’d totally forgotten I had done it. (IT WAS THREE DAYS LATER!) So it took me another two hours to finally realize I should boot up the AD PowerShell module and find the SPN that was screwing the install up.

What does all this have to do with text messages? Well, I’ll let you in on a little lesson I learned that day… Don’t hit send on texts until you check and see who you are sending it to… Exhibit A:

That my friends is the sound of a consultant shoving his foot so far in his mouth he gags. I literally choked on my drink when I looked at who it was sent to… Suffice it to say, not my friend. Nope, that is my client…

I got lucky this time around, and the client was really understanding about the whole thing… But next time… There won’t be a next time, because I always check who the hell I’m sending a text to… And so should you!


Leave a Reply

Your email address will not be published. Required fields are marked *