Um, yeah...

[draggar]

"I got this notification that something called SP3 is installing on my computer. 10 minutes later it was still there and it wouldn't let me quit so I forced my computer off. Now, it won't turn on. What did you do to my computer?????"

Yeah, right.

Time to reinstall OS!

[Racket_Man]

had that happen years ago when I worked on IBM AS/400's and RS6000 AIX machines for a company that had divisions all over the country. AHHHHH those lovely Cumulative PTF packages

I even scheduled the PTF install update/backup on a Federal HOLIDAY!!!!!! and sent out the appropreiate e-mail informing people about the down time.

about an hour into the initial backup (pre update install) I get a call asking why the machine is down/not accesable.

Well I scheduled an update/backup for this time. did you NOT get my e-mail????

BUUUUUTTTTTTT we have work to do!!!!! elventy eleventy (on a frackin holiday to boot)

sorry but once the process is started IT CAN NOT BE STOPPED (not really true but I really wanted to get this done because I also had scheduled a disaster recovery excerise for about a week later that required me to make sure I had ALL updates done and a system OS/kernal backup for the recovery site)

[Eric the Grey]

I even scheduled the PTF install update/backup on a Federal HOLIDAY!!!!!! and sent out the appropreiate e-mail informing people about the down time.

Nothing unusual there. I have to kick users off one of our systems on a weekly basis for maintenance that takes about 10 minutes. I will get a call on almost a monthly basis (1 in 4 weeks) from someone wondering why they can't log in.

We only do this EVERY SINGLE WEEK!



Eric the Grey

[Bandit]

Just remember, your average user has the IQ of cauliflower.

Oh - and no matter how bad they fuck things up, it's always your fault.

B

[Skeksin]

and not nearly as tasty when covered in cheese.

[Der Cute]

I'm sorry, you will not be able to access your gossipmill *ahem* email for the next 6 hours. We are doing a system wide update, so that our company can run better instead of HAVING LAZY ASS PEOPLE LIKE YOU SIT THERE AND THINK THEY'RE WORKING WHEN ALL THEY DO IS FUCKING SURF THE NET AND TRY TO SCORE CHICKS FROM CRAIGSLIST....oh where was I?

No email for the next 6 hours. Thank you for your cooperation.

-SysAdmin



cutenoob

[Gerrinson]

We have touchscreen POS terminals that have to remain off when updating the server, or the update will cancel itself and we have to start all over again.

We've tried turning them off and putting post it notes that say 'Do not turn on' in the middle of the screen. Which results, of course, in someone turning on a terminal and using it - without ever removing the note.

Next, we tried taping full page signs so they covered the whole touchscreen. Again, someone turns on a terminal but the screen is still covered by the sign when we get there.

Last time, we tried taping the signs at the top and bottom so they couldn't flip them up (which we assumed had happened.) We also pointed one of the security cams at the terminal most often turned on during the updates. We watched as one of the staff walked over, stared at the sign (reading it, one would assume), tried to pull it up but stopped when she discovered there was tape at the top and bottom. Finally, success!

Then she turned it on and walked away without even using the bloody thing.

Finally, we've transitioned to a user proof solution. We just pull the ethernet cable out of the back of the server. Problem solved.

And, just for the record, I'm pretty sure a head of cauliflower would get the point better than our staff. Please don't insult my cauliflower like that in the future, Bandit. Thank you.

[Racket_Man]

We have touchscreen POS terminals that have to remain off when updating the server, or the update will cancel itself and we have to start all over again.

We've tried turning them off and putting post it notes that say 'Do not turn on' in the middle of the screen. Which results, of course, in someone turning on a terminal and using it - without ever removing the note.

<snip>

Finally, we've transitioned to a user proof solution. We just pull the ethernet cable out of the back of the server. Problem solved.

And, just for the record, I'm pretty sure a head of cauliflower would get the point better than our staff. Please don't insult my cauliflower like that in the future, Bandit. Thank you.

my solution would have been to not just unplug the network cable but to also unplug the power cables as well (Unless there were more than a couple)

[Gerrinson]

my solution would have been to not just unplug the network cable but to also unplug the power cables as well (Unless there were more than a couple)

Between terminals & PCs there's 20+ stations. And we tried pulling power on the terminals, but the staff are smart enough to plug them back in, while being stupid enough to not read the sign. *sigh*

And the network cable was pulled from the server itself, so that works quite well.


Oh, and for the record: CURSE YOU DRAGGAR! Curse you for this thread!

I thought to myself 'At least no one here ever kills power during a Windows update.' And then I realized what I had done and took it back, but clearly the universe does not recognize take backs.

This morning, I had a long rambling message about how one of users thought the PC was taking too long to finish an update (more than 5 whole minutes!!!) so she just pulled the power cord out and now Windows doesn't work right.

So, I curse you and this thread for making me think that horrible, horrible thought!



J/K about the curse. Not about the idiot user.