Printable View
I don't see anything in there that's an invalid windows filename character. (I assume windows since you mention IIS).Quote:
Originally Posted by Melcar
I was even able to get a space in front of the first character via clever re-use of the "rename" command and quotation marks for the string.
True - which is why she could open the PDF's off a share or as an email attachment.Quote:
invalid windows filename character
Nope, that's just called: "getting older". :grinyes:Quote:
Originally Posted by Mileron
Because nobody seems to be learning, People do not learn from tech support they just keep calling tech support.Quote:
Originally Posted by Mileron
Yes, this exactly: "Why should I learn anything when I can just ask Melcar & he already knows the answer!"Quote:
Because nobody seems to be learning, People do not learn from tech support they just keep calling tech support.
---
"Geee - I never knew that document existed!"
Yes, that's because I cleverly hid it in our departmental share, where we put all our notes, under the folder Telephones. Cause I knew nobody would EVER look there for notes on the phone system. (and Yes, I said that out loud too!)
LOL I forgot to tell you guys about this one from Tuesday....
Get a call from one of our users:
My docking station isn't dead - the laptop is fine, but the dock doesn't work at all, no lights on it nothing, I had "Secretary who is going to school to be an IT tech" look and she couldn't figure it out.
----- get up there take a look; Turn to my user & say - is it April fools today?
she says "what no? why"?
Your power cord is unplugged. or rather it's plugged into the laptop not the dock... If it's plugged into the dock it'll power both - if it's plugged into the laptop then only the laptop works.
"Well how would that have gotten switched?"
I dunno - that's why I asked if it was April 1st -- to see if somebody was playing a practical joke on you.
That's creepy - I had a user with the same exact problem on Tuesday.Quote:
Originally Posted by Melcar
I figured it was the cleaners being careless.
those also sound like what I call a persistent disease in the office world. Tryphobia, Nobody is ever willing to just try something.
I once had someone who had plugged a power strip into itself insist their laptop was broken because it wouldn't turn on. And then proceeded to argue that wasn't the problem when I showed them what was going on. And then was surprised the laptop started charging when I unplugged the power strip from itself and into the outlet. You never know what kind of stupidity people will come up with next...
Tech support: is your computer plugged into the wall?Quote:
Originally Posted by Salamane
Customer: My computer did not come with a wall.
Don't forget though, wall != outlet.Quote:
Originally Posted by FilanFyretracker
I have the opposite where I work, for 20 years the company has existed without an 'IT guy', so they've just muddled through. Now they employed me to manage a transition to new software and develop (new) IT strategies as they've finally decided they want to grow the business from what it's been for the last 10 years. I'm forever trying to get them to leave stuff to me as they've developed, what is best called, 'bad habits' over the years.Quote:
Originally Posted by FilanFyretracker
One example that I fixed in my first week: it's a small company (20 people) and not one of the 20 PCs had anti-virus software installed. Amazingly, not one of those PCs had any sort of infection.
That's the week you play the lottery.Quote:
Originally Posted by HerbertDypp
That's the week you don't play. All your luck has already been burned up.
ka-ching!Quote:
Originally Posted by FilanFyretracker
It's almost like an incentive to not educate end users...if only they'd generate work when I wanted them to instead of when I was in the middle of something actually complicated instead of something I'd told them already 9 times.
In the words of my Theories of Personality prof at Temple (for whom I had a major crush), "If you all don't get A's in my course I have to go back and figure out how I failed to reinforce you to do so."Quote:
Originally Posted by Merrick ap'Milandra
E.g. you are in a co-dependent relationship with your miscreants here. Frankly well upwards of 90% of the problem here is with your recidivists. Indeed they may be, like ivory soap ... 99 and 44/100% to blame. Whatever is left there is within your control. Of course that begs the question is it worth your effort AND within your abilities to reinforce them to knock it off?
In the meantime your misery is the gain of those of us in the cheap seats getting shits and giggles at their expense. I doubt I'd have the patience to deal with customer service. Hats off to those of you here who do.
... :Popcorn:
The problem I run into is that most of my users don't have any ambition to learn. Even the ones who don't use it as an excuse to slack off and blame it on IT just aren't driven to do anything to understand the what or the why.Quote:
Originally Posted by Aennyil
Why would they? If they wanted to know how computers function to the same degree you do they would be in IT themselves. Most users just want their stuff to work. Their computer is a black box to them, and they like it that way.
I'm not even talking to the degree I am at.Quote:
Originally Posted by Schezar
I don't think it is too much to expect to understand the difference between a Windows login box and an application login box. For an application that is used every day.
Or how to fill out a web form completely after you've been told you need to 4-5 times.
Awesome prof, except for the word "reinforce". Indicates a failing on the part of the students.Quote:
Originally Posted by Aennyil
I had a similar prof, but he said "If anyone gets a failing grade, I see it as a failing in myself to motivate you to care about the material."
LOL. Busting out the Fox News phrasing here.Quote:
Originally Posted by Aennyil
Thing is, it's not their JOB to know how to deal with application crashes from home-brewed software that's written by another team than I'm on. It's mine. Their job is to USE the software to do THEIR job.
Mine is to assist them in making it work.
The end users are NOT idiots, it's just not their job to know how to deal with the fact that some LEC portal has gone down or that InHouseApp#1 is chucking an eax offset error, or that suddenly lots of apps won't launch because, without prompting the user, their machine updated to java 8, which breaks the 20 year old stuff that still relies on java 1.3 because there ARE no firmware upgrades for switches that old.Quote:
Originally Posted by Aennyil
There is a TON of stuff within my control, and educating end users is part of that. Generally, I'm lucky, because they're happy to learn.
That being said, most of them use us for what our JOB is, and that is for helping them with things they can't do for themselves either because they don't have the access rights or because they can't interpret the errors.
I don't "deal" with customer service.Quote:
Originally Posted by Aennyil
Your automatic assumption of "misery" annoys me. I don't do this because I HAVE to. I do it because I enjoy it and I can still regularly advance in my pay grade while doing so, and work with like-minded people.
It's what I really love doing, day in and day out.
I went back from administering dozens of citrix and exchange farms, which I was GOOD at, to a mixed management/tech role that involved direct contact with callers because I like the ability to plan things out in advance rather than shoot from the hip under management that insists on reactive instead of proactive.
So yeah, now I'm at a job that cares more about doing things right the first time than doing things over and over for the quick solutions.
I still have plenty of funny stories to tell, but over the last decade or so, it's become clear that what I love the most is customer service.
Not a meat mill like an average call center, but actual customer service group staffed with knowledgeable techs.
It's a far cry from "My Cup Holder Isn't Working".