Shark Tank: Spoilsport!

Help desk pilot fish gets a trouble ticket: A support tech is having a problem with asset management software that isn't reporting properly on a user's PC in a remote office.

"After checking several routine system settings remotely, I determined that I needed to log into the user's PC myself," fish says.

"In order not to interfere with productivity on this minor issue, I ran a script to check if anyone was logged in to this PC. There was, so I resolved to wait till the next morning to try again."

So at just past 8 a.m. the next morning, fish checks again. Sure enough, no one is logged in -- the user probably doesn't start work until 8:30 or 9:00, fish figures.

He quickly logs in remotely and sets up exclusive control so the user won't accidentally interfere if she shows up. After about three minutes of quick work, fish restarts the PC, ends the session and logs out.

Then fish confirms that the PC came back up, closes the ticket and figures he's done with it.

But later that day, fish gets an e-mail forwarded by his boss. It's a harshly worded report from the IT manager in that remote office, who says a user complained that fish "shut down her application without warning, logged her off, logged in himself and restarted her computer, causing her to lose some of her hard work."

Says fish, "I immediately recognized this as a user who either was late for work or missed some deadline, and either way decided to blame the computer guy.

"Acting fast, I gathered workstation and network logs and quickly formed a response. I explained my actions, and attached the logs showing no previous log-ins for the day -- and another late log-in from the day before."

Sharky figures there's plenty of blame to go around -- for users, bosses, consultants and even IT people. Whoever it's about, send me your true tale of IT life at sharky@computerworld.com. I'll send you a sharp Shark shirt if I use it. You can also add comments by using the form at the bottom of this page.

See more Shark Tank stories at the Sharkives.

Join Shark Bait

Now you can post your own stories of IT ridiculousness. Join Shark Bait today and vent your IT frustrations to people who've been there.
Go to the
Shark Bait homepage
or
Post a story now

Modern society relies on 'dangerously fragile' software

Are we ready for a civilization that's based on pervasive computing and increasingly complex "systems of systems," all dependent upon software written by unlicensed people calling themselves programmers? In this Computerworld interview, software guru Grady Booch, chief scientist at IBM Rational, talks about the enduring difficulties of software development and the complexity of today's systems: Software [development] has been and will remain fundamentally hard. Most of the interesting systems today are no longer just systems by themselves, but they tend to be systems of systems. It is the set of them working in harmony. We don’t have a lot of good processes or analysis tools to really understand how those things behave. Many systems look dangerously fragile. The bad news is they are fragile. This is another force that will lead us to the next era of how we build software systems.

Image Gallery: How to troubleshoot Windows Home Server problems

Preston Gralla explains how to overcome common issues with Microsoft's new networking software.

Image Gallery: Windows Home Server review

Preston Gralla is impressed by the backup-and-restore, media streaming and remote access capabilities of this software, which for once hasn't been "dumbed down" by Microsoft.

How to troubleshoot Windows Home Server problems

Preston Gralla shows you how to solve common issues you may run into when installing or using Windows Home Server and its associated software.

Review: Windows Home Server is a powerful networking tool

Preston Gralla is impressed by the backup-and-restore, media streaming and remote access capabilities of this software, which for once hasn't been "dumbed down" by Microsoft.