Favorite revenge tactics?
Apr. 22nd, 2005 07:57 pmA couple recent posts inspired me to ask...
What are your favorite revenge tactics for annoying asshat users? What super powers and info do you have that could severely ruin a user's day? Which ones can you get away with? Which ones would get you fired if you used them?
Personally, I have the basic toolset and a handy advanced toolset. Name, phone number, email address, department they work in, etc. I can sign them up for porn and spam and whatnot, and I can do that from home so work can't really trace me, but that's boring. I can send stupid attachments from a non-work account to theirs, and send them over quota. That's boring and the other downside to these is we rarely get to hear about the payoff. Oh, and the "accidental" hangup.
My advanced revenge toolkit includes:
- locking the user's domain account so they can't log into their office computer, any lab computer, or their Exchange or Blackberry
- removing the user's DHCP registration so they'll have to re-register it (or call us to do it) and wait an hour before they can get on the campus network again
- giving ridiculously bad advice the next time they call (hey, uninstall sp2 and your virus scanner. our network alone will protect you from trojans and worms, you'll be fiiiiine)
All of these will usually result in a user calling in again (after being an asshole) and asking why so-and-so isn't working. These tactics pose a greater risk of us phone monkeys getting caught.
So what are yours?
What are your favorite revenge tactics for annoying asshat users? What super powers and info do you have that could severely ruin a user's day? Which ones can you get away with? Which ones would get you fired if you used them?
Personally, I have the basic toolset and a handy advanced toolset. Name, phone number, email address, department they work in, etc. I can sign them up for porn and spam and whatnot, and I can do that from home so work can't really trace me, but that's boring. I can send stupid attachments from a non-work account to theirs, and send them over quota. That's boring and the other downside to these is we rarely get to hear about the payoff. Oh, and the "accidental" hangup.
My advanced revenge toolkit includes:
- locking the user's domain account so they can't log into their office computer, any lab computer, or their Exchange or Blackberry
- removing the user's DHCP registration so they'll have to re-register it (or call us to do it) and wait an hour before they can get on the campus network again
- giving ridiculously bad advice the next time they call (hey, uninstall sp2 and your virus scanner. our network alone will protect you from trojans and worms, you'll be fiiiiine)
All of these will usually result in a user calling in again (after being an asshole) and asking why so-and-so isn't working. These tactics pose a greater risk of us phone monkeys getting caught.
So what are yours?
no subject
Date: 2005-04-24 02:45 am (UTC)