Unknown to them, this default group was required for normal network authentication without it, authentication broke.Īfter the issue was identified, it was discovered to be behind several other, seemingly unrelated problems the customer had experienced. In the end, it turned out the error was caused by the customer having removed a default group membership from the local computer. And they worked on the problem for days, moving tech support teams across the global "to follow the sun." The customer was upset with me and my company. I brought in a team of people who wrote the code. The error message being thrown was a common one, but nothing I had done before to resolve it worked. Rarely did it take more than a day to figure out the problem and move on.īut this particular issue was different. Occasionally, I've run into install errors or other issues that I had to troubleshoot. I had installed this program hundreds of times over several decades. Changing the defaults in other cases will just end up biting you in the end with little increased security to show for it.Ī few months ago I was onsite at a favorite customer's of mine installing a big new software program that would be a mission-critical component of the security environment. There's an old security mantra that says "always change the defaults!" Although this seems like a good general rule, in fact it's true only for certain kinds of settings.
0 Comments
Leave a Reply. |