If we had tickets here, my coworker, who's on the first line of fire this morning, would have this to write up.
Problem:
Customer called to report that his workstation was locked and he was unable to do anything.
Action taken:
Confirmed customer is working on [on-campus Windows domain]
Asked customer if workstation had been left idle recently.
Stepped customer through pressing Ctrl+Alt+Del and entering his domain password to unlock workstation.
Customer recovered his workstation
Status:
Resolved
Sometimes I'm afraid I'm no good at my job because I can't understand how upon seeing this (both pics taken from google cause Print Screen doesn't work when the workstation is locked):
one wouldn't know what to do. HOLY CRAP! Once you do hit Ctrl+Alt+Del, you get this:
and I think it speaks for itself!
Am I really that bright?! I've had people ask me why I'm "so good" and I tell them it's because I've been using computers since I was big enough to propped up in front of one of these:
But really, it's just a knack for these things. It's sitting down at a new application and just knowing that the command you want is probably available if you highlight the thing and right-click, and then being brave enough to try
Along the same vein as that rant, I had someone call about Quicken last week. I like the lady and technically it's work for a prof and heck, it's dead here, so I go to check it out.
She can't print, with an error message along the lines of "You cannot print because we are missing a PDF driver. Close Quicken, run the command q:\path\command.cmd and then restart and try again." So I write down the path, close the program, run the command, and it works. (Best damn error message I've ever seen.)
I don't expect her to know how to run a command, but considering I stepped her through what I was doing, her question at the end of "But how did you know what to do?" seemed a little redundant.
It's like people are afraid to read.
Problem:
Customer called to report that his workstation was locked and he was unable to do anything.
Action taken:
Confirmed customer is working on [on-campus Windows domain]
Asked customer if workstation had been left idle recently.
Stepped customer through pressing Ctrl+Alt+Del and entering his domain password to unlock workstation.
Customer recovered his workstation
Status:
Resolved
Sometimes I'm afraid I'm no good at my job because I can't understand how upon seeing this (both pics taken from google cause Print Screen doesn't work when the workstation is locked):
one wouldn't know what to do. HOLY CRAP! Once you do hit Ctrl+Alt+Del, you get this:
and I think it speaks for itself!
Am I really that bright?! I've had people ask me why I'm "so good" and I tell them it's because I've been using computers since I was big enough to propped up in front of one of these:
But really, it's just a knack for these things. It's sitting down at a new application and just knowing that the command you want is probably available if you highlight the thing and right-click, and then being brave enough to try
Along the same vein as that rant, I had someone call about Quicken last week. I like the lady and technically it's work for a prof and heck, it's dead here, so I go to check it out.
She can't print, with an error message along the lines of "You cannot print because we are missing a PDF driver. Close Quicken, run the command q:\path\command.cmd and then restart and try again." So I write down the path, close the program, run the command, and it works. (Best damn error message I've ever seen.)
I don't expect her to know how to run a command, but considering I stepped her through what I was doing, her question at the end of "But how did you know what to do?" seemed a little redundant.
It's like people are afraid to read.
