Tom Yager spends a column berating "fixers" - the non-IT staff guy who fixes things for end users:

It becomes the fixer's goal to leave no problem unsolved. He comes to see every call for legitimate support as his personal failure. He gets addicted to being so needed and celebrated, and IT becomes just as addicted to the fixer as a labor-saving device. No one who benefits from his existence worries about the fixer's power to shortcut not only process but policy.

By the time the first problem is spotted, the damage is already widespread. License audits reveal twice as many installed copies of a costly application than are licensed. The bootable CD the fixer created is passed around to create unauthorized backups of desktop drives. The employee who got the fixer to hook him up with an FTP account decides, on termination, to use that account to host a publicly accessible library of ripped DVDs. The well-intentioned guy who just likes to help out is a one-man back door for every foolish or malicious user who wins his trust. And guess who gets stuck holding the bag?

Now for the question Yager didn't think to ask - why does the fixer exist in the first place? Well, that would be an unresponsive IT department, wouldn't it? Why do they end up holding the bag? Because they spent years pretending that the bag didn't exist in the first place. Yager needs to read Dilbert until he gets it.

What's the actual lesson here? If you have fixers in your organization, it's an indication of a broken IT department. Address that problem, and the need for the fixer will disappear.