Re: So ...
For the record, my job title at the time was Floating Senior Member of the Technical Staff. I wandered from department to department, putting out fires. In this case, I was straightening out broken corporate computing culture in wholly owned subsidiaries of a Fortune 50, reporting directly to The Board. Part of my remit was to shake up Sr. Management at the subsidiaries ... They were dragging their feet over adhering to the new (to them) corporate mandate. When you're an F-50, you don't want unauthorized equipment anywhere near your network, but cowboys (like most of the above commentards, apparently) always think they know better. A high-level firing or two usually makes 'em realize that THEY don't own the network, the corporation does.
I've used the same methodology ever since, when necessary. Seems to pay the bills quite nicely now that I've struck out on my own.
As for interpersonal relations within the company ... back before I decided to become a contractor, I was the guy who started Homebrew clubs in several companies, and I was one of the people who helped introduce Cricket to Silly Con Valley ... I'm a happy go-lucky guy, for the most part. Just don't fuck with the equipment that I have been charged with safekeeping. You'll lose.
And no, I'm not a "BOFH". Do any of you lot even know what an Operator is? An operator is the flunky who swaps out tapes during late night backup runs. An operator keeps the admins in coffee and the printers in paper and ink. An operator counts supplies in the stock room. Most operators are interns these days. If you're a machinist, an operator deburs and degreases parts. Operators are rarely given jobs more important than remembering "one lump or two". The whole concept of an operator having admin access to corporate equipment is laughable.