Tech Support Gripes HERE!

The one thing that bothers me the most is when people assume I'm in India. No, actually, I'm in North Carolina, thanks. A good number of my co-workers are indian, but they too are in North Carolina. Being a company that provides 24/7 around the clock tech support there may be times that you get someone who is in India. If that's the case, you probably opened the case around 3am EST.

sigh

Arch said:

The one thing that bothers me the most is when people assume I'm in India. No, actually, I'm in North Carolina, thanks. A good number of my co-workers are indian, but they too are in North Carolina. Being a company that provides 24/7 around the clock tech support there may be times that you get someone who is in India. If that's the case, you probably opened the case around 3am EST.

sigh

Click to expand...

We have a couple of people from India in our center. Because of security policies put on us by the company, we're not to divulge the center's location. One time, a guy calls in and gets one of the Indian girls there. He asks where we're located, she says she can't tell him because of security. He starts screaming saying he doesn't know why she can't tell him since she's just over in India anyhow, then asks for her supervisor. The supervisor (an all-American looking boy) actually takes her headset and says "We're not in India. Any other questions?" The guy was apparently so embarassed he just hung up.

Ok I have a gripe about users:

I was working contract for this company, and in a team of about 10 other contractors doing tech support on Monday after we moved quite a few computers around the night before. So 1 hr into the project, I hear a person yell that they lost their documents on the printer. Well soon to our horror, in a few seconds so did everyone on the 4th floor. Print Server went down, I quite as well knew what usually accompanies the printer server shutting down, the file server going down.

Soon enough, we were getting calls from the 5th floor that the fileserver went down. Ok, into the third hour, the Dns server for the building shuts down, and so did the dhcp server. First conference call for the day, no resolve. Into the conference call, someone on the line yells that they lost connection to the other adjoining building.

Great I tell myself, two buildings lost all network traffic, files and whatnot. So a emergency tech team heads out for restarting the servers in Blue Ash, OH. That is a no go, the servers startup and shut down, somethings resetting it. Now the second conference call, they try to blame us, the contractors for screwing it up. Into that conference call, boom, the client looses network connection for the offices in greater Cincinnati.

So trying to run around, trying every best you can to tell the people to chill. Print server is restarted and printing documents in it's que, but sending them to the wrong building.

As all of us contractors, ask ourselves what else can go wrong. Well to put it this way, everything had gone wrong. We are two hours past our due time, we just happen to take a lunch. Our boss, and his partner walks past a wiring closet on the ground floor, then hear someone cutting something.

A lan tech for the company is cutting rows and rows of lan cable in the closet. The two ask what are you doing? He says: Oh I'm making room for another server rack. They ask him that he took out all network traffic to the company.

His answer, Oh I'm Sorry. He doesn't skip a beat either and continues to snip cable in the closet. I just have to say, we got overtime and someone lost their job that day.

i woulda taken somethign out a just smacked the living shit out of him for that

Scorpionjwp said:

A lan tech for the company is cutting rows and rows of lan cable in the closet. The two ask what are you doing? He says: Oh I'm making room for another server rack. They ask him that he took out all network traffic to the company.

His answer, Oh I'm Sorry. He doesn't skip a beat either and continues to snip cable in the closet. I just have to say, we got overtime and someone lost their job that day.

Click to expand...

are you fucking kidding me?? he would have gotten his ass KICKED out the door

I have a user who needs her hand held everytime she needs to create a word document.

No, I am not kidding.

She also routinely forgets how to log in to windows. Constant ray of sunshine in my day.

But honestly, I've been "lucky", and most of my gripes are aimed the other way: Tech support. Namely, sbc tech support.

And while I'm on that topic, don't ANY of you give them a fucking dime. They don't deserve it.

I have a few locations that I administrate where I don't have any windows boxes, blissfully. One of those locations had sbc dsl, and it was signed up right at the beginning, so we had some weird one of a kind service that no tech this side of the pacific ( name of "David" ) had ever heard of. Eventually swore I was making up what I was telling him.

Then, my PHB ( at the time ) got involved. Now, up to this point, I had been keeping the nasty "L" word out of our conversation ( linux ), knowing full well what it would do to this tech. He would ask me to do something in windows, and I'd give him the information he was asking for. End of story. My boss, not the sharpest knife in the drawer, more of a spoon really, demanded why we were having such a hard time getting our linux router working. Yelled at the tech, which I'll admit felt good just in proxy.

After days of fighting with sbc to get that dsl line working, I finally gave up and called speakeasy ( highly recommended, no matter the extra cost ). And lo, there was a light. And it was glorious.

As far as users are concerned, I don't get that riled up as long as they are trying their best. That's all I can ask of them, and in part what I'm paid to do.

xor, what was the problem you were having?

Stang Man said:

xor, what was the problem you were having?

Click to expand...

It was odd. We had an account with SBC that was pretty basic: The modem worked in gateway mode, and I simply assigned the router the IP address. No pppoe, none of that.

One day the router went out, so I replaced it with a linux box. No big deal, except the location hadn't kept the information of the order, and I was a month new to the job. So I didn't have anything like IP address, gateway, subnet...nothing.

So, innocently, I called up sbc and asked for the information. They told me we were on pppoe, which I knew we were, and gave me IP information that was simply impossible. The ip address with the subnet mask put me on a completely different network than the gateway ( although now I can't remember the exact numbers ), and given the subnet the address they gave me was either the broadcast or the network address. On top of that, the phone number that the dsl line was on wasn't in their records. Essentially, they were providing service to us, but had no idea ( as far as the tech ticket ) what the phone number was we were working on.

And then, "David", was having a hard time actually believing we were customers...even after he found the account ( which, given the rest of the conversation, as a miracle ). He had never seen an account like ours ( grandfathered in for being so old ), and so assumed it must be in error.

I never did get correct information from them, but they couldn't understand what I was telling them about the IP address information they gave me. We got his supervisor ( "Bob" ) and a few other people involved. Their end result answer: I had to call the partitioning dept if I don't like the IP address information given. And they told me I had to call the regular support line when I called them. When they actually answered the phone that is.

It was loads of fun.

A coworker just sent this to me:

These are the unwritten rules from the highly over worked, but highly under paid technical support staff at an Internet service provider near you...

1. DO NOT talk over me. Listen damn it, you can't do what I tell you to do constantly jabbering bullshit over me. I talk... you do. Why did you even ask me a question if you are going to fucking answer it?

2. DO NOT call me and then put me on hold. You called me, genius. You want my help, stay on the fucking line and listen. We have much better things to do than talk to you anyway.

3. DO NOT read long error messages to me unless I ask you to. Do you honestly think we get anything out of a 50 digit hex number???

4. DO NOT start off a call by saying anything in the neighborhood of "hi, how's it going" or "busy today?" That just serves to piss us off. Get to the problem so we can get you off the phone. The day was great until I had to start answering your totally moronic questions.

5. DO NOT get pissed when we tell you that your system is royally fucked. We didn't fuck it up. It wasn't us. We're simply telling it like it is.

6. DO NOT call about unrelated products. We DO NOT know the intimate details of every piece o' shit shareware program you dredge out of the internet. Nor do we want to. Stop it!

7. We DO NOT manufacture modems, write e-mail programs or engineer browsers. If something in this arena goes wrong, call the people who made the goddamned thing. YOU DON'T USE THE INTERNET TO FAX!!! Can't stress that one enough.

8. DO NOT compare us to AOL when something goes wrong with your connection to us. If you had the computer literacy of an 8 year old with a broken Atari 2600 you'd know better. Everyone else connects just fine. It's just you. Keep that in mind. It's just you.

9. DO NOT call simply for the purpose of giving us your thoughts on the content of our homepage or to request that we send you flyers so you can pass them out at bridge tournaments and bingo night. Not only is this a waste of our time, but it encourages just the type of user tech support reps fear most... the elderly.

10. DO NOT make us sit there on the phone while you tip toe through setup instructions so easy they were originally tested on lab chimps. We have better things to do than act as zoo keepers.

11. DO NOT call us and complain about a problem with your system and then say you're not in front of your computer when we try and help you. We aren't technological psychics.

12. DO NOT call us assuming the problem you're experiencing is our fault. If your computer crashes, performs illegal operations, gives you the blue screen of death, or flips you off and runs away with the fucking toaster to
Mexico, you can be damn certain it isn't us who caused it.

13. DO NOT call us and announce to us that you don't know anything about computers. This really pisses us off. Trust me, we're well aware of that fact. We figured it out the minute you called and announced "help, the internet
is broken!" Something here definitely needs help. People who know computers don't call us.

14. DO NOT call us and act as if you know all that are computers and that you're doing us a favor by gracing us with your call. This pisses us off more than 13. Chiming in with stupid suggestions and comments only increases the already tremendous temptation we face to use you as an unwitting instrument of destruction and really do some damage to your system. Not that you'd notice.

15. DO NOT (in addition to 14) say acronyms you don't know the meaning of or even what they are for. Just admin your completely lost and leave the techno bullshit to us.

16. DO NOT call in if you can't speak English. This might seem like a small thing to you, but we find it just a tad annoying when we try and assess your problem and we can only understand every fifth word you say. And no, just because those words may be 'computer' or 'broken' doesn't absolve you of the offense.

17. DO NOT call in hoping to get another tech rep to tell you something different than the first one did. If one of us tells you your system is fucked, it's fucked. The second guy is going to simply look at the log and tell you the same thing, it's fucked. That is of course unless you really piss him off and then he's going to make sure your computer has the functionality of a house plant.

18. DO NOT be stoned or drunk when you call us. You wouldn't think this would need to actually be said, but believe me it's come up. For god sakes, if you can't control yourself and must call, at least have the common courtesy to offer us some of what you're on.

LMAO nice post!

lol i love that post
i get those calls
ya my system has this blue screen with uhhhh 00x78344.slkduf;aksf whatever
i say
bring it in and i can fix it....then they ask why teh blue plug wont come out of the pc..
"i pull and pull but nothing...so i just pulled harder:

hey now, I worked on the other side, and having to call for business lines now, makes my head hurt.

1) Don't fucking ask me for the telephone number, I work at a NOC, the remote site is 2000 miles away.

2) Don't ask me what the lights on the modem look like, I have no fucking idea, if we had a web-cam, it'd be broken too.

3) Don't tell me that you have to create a ticket for every modem in the city I'm calling about, If they'e all down, just give me a BS excuse like maintenance to get me off the phone, don't be a hero.

4) Don't ask me what SNMP is.

5) Don't tell me that everything is "green" on the router, if it's cable it's a cmts/ubr if it's dsl it's more like a CO switch, stop fluffing my balls and telling me what you see on your gay CGI script.


Sorry, I had a real bad night last night, circuits dropped out left and right and cable modem and dsl techs are retarded. I know I did the job a while back, but I at least researched what I was talking about and was able to pull the data right from the UBR, not from some queer CGI scripted website.

</rant>

Rabidfox said:

Sorry, I had a real bad night last night, circuits dropped out left and right and cable modem and dsl techs are retarded.
</rant>

Click to expand...

that would be Level3 and I think Cogent being retarded that gave you a bad morning.

back on topic....I started out on the helldesk back in 95 for a aussie ISP, good days. We got bugger all calls.

Now being on the "other" side, I try to be nice to my tech support pals. If I have to call up for something (recently I had a Cisco 9216 SAN switch be stupid) I try my best to be nice. Still, for things like that they rarely have monkeys answering the phone....they send the monkeys out tho (took EMC fckin 6 hours to install a "maintenance pc"...useless fuckers)

ah well, we are all idiots til we know better.

twyztyr said:

YOU DON'T USE THE INTERNET TO FAX!!! Can't stress that one enough.

Click to expand...

I do

I say I would have to agree with the majority of posters here...

I work for one of Europe’s largest electrical retailers, in their PC service / repair division. My job actually entails providing second level support to the peeps who actually provide support to the end user…

What really gets my goat is having to answer for the umpteenth time in day how to diagnose a faulty HDD, or explain to some one that diagnosing a wireless network really isn’t much different to diagnosing a wired network, and to stop being so scared about it…

However, nothing compares to some of the calls that I have listened in to or have been involved in…

For example:

Customer calls in and immediately asks to speak to a male call handler (after getting through to one of the few females we have working here). The young lady in question takes offence at this and explains that she can deal with any problem. The customer then goes on to explain that his PC does not work. He then goes on to explain that he had taken the side of his case, and had “pleasured” him self inside the case, and that he would like a engineer to come out and fix his machine. The young lady handling the call hung up on him at this point.

The customers mother then called up a few hours later, and explained that customer hadn’t actually “pleasured” himself in side the machine, but had “passed water” in to it instead.

Strangely enough we terminated the warranty on his machine.

The moral of this story is that while tech support can be bad at times, customers can be just the same.

FireExit said:

The customers mother then called up a few hours later, and explained that customer hadn’t actually “pleasured” himself in side the machine, but had “passed water” in to it instead.

Click to expand...

Thats golden.

Kristo said:

Thats golden.

Click to expand...

We thought so at the time... After going Ewwwwwwwwwwww first....

Yikes. Qwest DSL(home) tech support is the worst.

I had some problems with my DSL line after a two week vacation(everything was powered off). I would obtain an ip address and everything, but I could only pull dns-requiring data(HTTP) for about 15 secs before it ceased to function, if I left the modem on for a few hours it would work again for 15secs when I tried it(ping worked all the time). Weird huh? So I call tech support up and troubleshoot the issue. The tech was obviously reading from the manual and was not doing any thinking on her own two feet. So, after attempting to connect to the internet with FOUR different computers(3 comps, one xbox), numerous different cables, TWO different DSL modems, and over 10 different NICs with the same result(data transfer{http} only worked for 10-15 secs after resetting the DSL modem); the tech concluded that the problem was on my end because she could ping my computer and my lights were green. She didn't even understand the concept that the Actiontec GT-701 was a router, I had to explain how the DSL modem that Qwest had sent me worked(at first she kept insisting that I needed to turn my firewall off on my computer so she could ping me). In the end, I ended up requesting a tech to come out, she said that it would be $100 if they determined the problem was my fault. I told her that I would GLADLY pay the $100 if it was MY fault. So a tech was scheduled for the next day around one. I woke up at 10AM, reset my DSL modem, and my net worked, even better than when I left on vacation. I canceled the tech out-call and, when I did, the tech on the phone mentioned that they may have messed with something at the CO already.

I'm just amazed at the fact that they could come to theconclusion that my equipment was to blame given the extensive troubleshooting I did.

^ I've had similar problems with comcast in the past.

My connection had worked great for years with comcast up until this spring when their national dns servers shit the bed. A few weeks after that I started having horrible packet loss after 7PM or so at night (peak load times). I ran line tests and trace routes and tried to get this information out to them. Some techs would listen and take the info, but could never give me an update on the problem. Some techs insited that the problem was on my end, even though I was getting 30% packet loss at the SECOND hop from my router. It's absolutely infuriating when the level 1 techs don't know shit and you have an ongoing issue that lasts for weeks. If I'd been able to talk to someone who actually dealt with their network I would have learned that it was a bad router that was slated to be replaced (why it took weeks, I don't know. I have 4 hour 24x7 replacement service at work for our cisco equipment).

Here's a story I just remembered. Names changed to protect the reatrded.

The company I waored for took a job as tech/IT at a local compant that had just canned it's IT guy.

A woman comes up to me very cautiously and says " I just accidentally deleted a file, is it backed up from yesterday?"

I tell her it is and not to worry (I verified the backup system myself). After checking her PC to see if it was still in the trash, and it wasn't, I head to the backup server to restore the file. Once it's restoring I go to tell her.

She's thankful and then says "I feel so much better when you're around, when Tom's around I get scared".

Thankfully Tom, my boss, left about two months later.

I liked gateways online tech support. I was bugging them about an early 1990s 486 (this was 2 years ago) .

Mircosofts tech support for windows activation really pisses me off. I uninstalled, and reinstalled a network card driver. That was all. I havent even had my case lid off, not even for blowing out dust, ever since I intalled XP. So anyways, it says my hardware significantly changed and I need to reactivate...

I dont know if I speak with an accent, talk like a redneck or what, but their damn automated voice pile of crap cant understand anything im saying. Tells me to speak my product activation or whatever code into the phone... 15 minutes later I get to talk to a person that I have a hard time understanding. Ugh... If they would only leave out the automated thing, or let me push the numbers in on my phone... Aside from that, mirosofts regular tech support, when I called four years ago, was awesome.

Dell, they wanted to run through a whole scriped call "is it plugged in... are you at the desktop... is the monitor light blinking?". I dont mind that, they are just doing their job and probably saves them some mental anguish.

My experiance for giving people "tech support":

Im the only one around here for about 5 city blocks that actually knows anything (small town full of old people). So my parents are always bugging me to teach them how to send a file attachment, parents are always "oh I Know this lady down the street, she has a son in laws uncles dogs owners friend who has a problem with their pc...". My friends, even a few from far out of state, call me and get me on the phone for 2 hours sometimes to help them with their computers.

What really burns my ass, is that people are afraid to do anything or click anywhere, they think they will seriously ruin the computer. Im standing right there next to them, or on the phone talking them through it. I wish they would just trust themselves, and have some confidence, and click on the damn button.

My grandparents were like this. Didnt want to break anything, I told them something like "unless you actually open the computer up and mess with its internals, you arnt going to hurt it". Their hard drive took a dump or something, from a virus. They dont know nothing about computers, but somehow managed to format the drive/reinstall XP and get some of their stuff up and running, even back online to msn's dialup. I wish all people would stop being so shy and worried and listen.

I have some serious respect for any tech support person that is trying to do a good job. I think I would have a mental break down and go psyco if I had to do it for a living. Keep up the good work, fighting the war on stupidity.

bob said:

I have some serious respect for any tech support person that is trying to do a good job. I think I would have a mental break down and go psyco if I had to do it for a living. Keep up the good work, fighting the war on stupidity.

Click to expand...

there's been some calls customers would push me over the edge and I would just about snap.



oh, and guys... if you're put on hold, and you hear no music..... you're not on hold

Stang Man said:

if you're put on hold, and you hear no music.....

Click to expand...

Not always. I work outsource VOL DSL level 3 and sometimes our hold music isn't 'working'. Every now and then a voice pops in and says thank you for holding.


If you guys think customers are bad, the kind of 'techs' that $10/hour brings...

kcthebrewer said:

Not always. I work outsource VOL DSL level 3

Click to expand...

Residential or business? If it's residential, would you by chance either be in Grapevine or Odessa?

twyztyr said:

Residential or business? If it's residential, would you by chance either be in Grapevine or Odessa?

Click to expand...

Grapevine

valve1138 said:

I tell her it is and not to worry (I verified the backup system myself). After checking her PC to see if it was still in the trash, and it wasn't, I head to the backup server to restore the file. Once it's restoring I go to tell her.

Click to expand...

Hrrm thats intersting. You should know that when you delete a file from a network drive it never goes to the recycle bin

I had a lil problem with my crappy local ISP. I could connect, get online and everything but the second I started to download over 10K I would loose connection, same with my upload. I called tech support and they insisited that it was my router, then my firewall, and then windows firewall. Finally I decided to wait another day to see if things would start to function normally. Next day crap still didn't work, so I called tech support once more and got someone with some brains, apparently they had just upgraded a couple servers but didn't secure a cable and it had worked its way loose thus everyone in town would be getting dropped. Yeah...I guess it was a problem at my end after all huh?

kcthebrewer said:

Grapevine

Click to expand...

I'm a tier 3 in Fishers. Kinda cool to find another VOL victim, and a T3 at that.

I just clasp my hands together, twiddle my thumbs and thank the good lord above that I have a job.

Rabidfox said:

hey now, I worked on the other side, and having to call for business lines now, makes my head hurt.

1) Don't fucking ask me for the telephone number, I work at a NOC, the remote site is 2000 miles away.

2) Don't ask me what the lights on the modem look like, I have no fucking idea, if we had a web-cam, it'd be broken too.

3) Don't tell me that you have to create a ticket for every modem in the city I'm calling about, If they'e all down, just give me a BS excuse like maintenance to get me off the phone, don't be a hero.

4) Don't ask me what SNMP is.

5) Don't tell me that everything is "green" on the router, if it's cable it's a cmts/ubr if it's dsl it's more like a CO switch, stop fluffing my balls and telling me what you see on your gay CGI script.


Sorry, I had a real bad night last night, circuits dropped out left and right and cable modem and dsl techs are retarded. I know I did the job a while back, but I at least researched what I was talking about and was able to pull the data right from the UBR, not from some queer CGI scripted website.

</rant>

Click to expand...

GRRRRRRRRRRRRRRR

As someone who has supported business customers, your attitude pisses me off.

1) MOST calls come from the location affected, and most employees seem to be more likely to remember the phone number than the account number.

2) See #1, if you're off-site, say so, don't be an ass about it.

3) Suppose there's a new outage and you're the first person to report it? Wouldn't you like them to FIX it?

4) I won't if you don't bring it up.

5) That's just damned out of line. There are cases when a) you have a ubr from the ISP or similar equipment, or b) all our gear IS working properly and it's actually a problem with your gear.

Just because you had a bad night is no excuse to dump on tech support, would you like it if they had a bad day and dumped on you?

Explain things politely, it seems to work better than being a wiseass know-it-all (note, not directed at you, just a general observation).

Atragon said:

GRRRRRRRRRRRRRRR

As someone who has supported business customers, your attitude pisses me off.

Click to expand...

yup.. just let us do our job. sure, you'll get some people who aren't as smart as others, but don't knock them and make their job hell.

Atragon said:

GRRRRRRRRRRRRRRR

Click to expand...

Agreed. The first rule (well maybe not first but defenitly top 10) is to assume the person on the other end is an idiot, and give them full instructions. You can always just ignore extra steps or instructions, but if you don't know what your doing you can't skip steps. Also it's always good to cover ALL the basics first because theres nothing worse then assuming they know what their doing and find out its something really simple. Even if they seems knowladgable, its always possible they missed something simple, i do all the time. I've wasted too much time just assuming they know what thier doing and having it come down to an unplugged cable or something. So let us do our job, be nice, and just answer all of our questions because it may just solve your problem. If you don't want help, then don't call and solve your own problem.

Karlos said:

Agreed. The first rule (well maybe not first but defenitly top 10) is to assume the person on the other end is an idiot, and give them full instructions. You can always just ignore extra steps or instructions, but if you don't know what your doing you can't skip steps. Also it's always good to cover ALL the basics first because theres nothing worse then assuming they know what their doing and find out its something really simple. Even if they seems knowladgable, its always possible they missed something simple, i do all the time. I've wasted too much time just assuming they know what thier doing and having it come down to an unplugged cable or something. So let us do our job, be nice, and just answer all of our questions because it may just solve your problem. If you don't want help, then don't call and solve your own problem.

Click to expand...

If you work for Dell or HP. The STFU and send me the part i'm telling you is bad. I am sure I am more qualified than any of the "tech" anyone has EVER got on the phone. So when i explain the sympotoms and tell you what i'd done just send me the part.

oakfan52 said:

If you work for Dell or HP. The STFU and send me the part i'm telling you is bad. I am sure I am more qualified than any of the "tech" anyone has EVER got on the phone. So when i explain the sympotoms and tell you what i'd done just send me the part.

Click to expand...

The reason they have to go through all the steps (every company is the same) is because its expensive for companies to send out replacment parts. If the part isn't actually bad its a huge unnessesary cost to the company. I can;t count the times i've gotten calls from people saying "my mouse is dead, send me a new one" and the mouse is unplugged. Or even if it is broken its because they keep knocking it off the desk... Even if the person is an experienced tech they still have to by procedure double check everything you've done. Just say yes so they can complete their steps. Could you imagine just shipping out parts everytime someone says its not working? and how are they to know your a tech and know what your talking about? Almost everyone says "i've tried everything and it still dosen't work?" because 90% of the time, they haven't tried everything.

Karlos said:

The reason they have to go through all the steps (every company is the same) is because its expensive for companies to send out replacment parts. If the part isn't actually bad its a huge unnessesary cost to the company. I can;t count the times i've gotten calls from people saying "my mouse is dead, send me a new one" and the mouse is unplugged. Or even if it is broken its because they keep knocking it off the desk... Even if the person is an experienced tech they still have to by procedure double check everything you've done. Just say yes so they can complete their steps. Could you imagine just shipping out parts everytime someone says its not working? and how are they to know your a tech and know what your talking about? Almost everyone says "i've tried everything and it still dosen't work?" because 90% of the time, they haven't tried everything.

Click to expand...

When the HP tech tells me to clear the CMOS when the PC will not power on there is something wrong. I am not some run of the mill customer. I represt the nations larget dental care provder. One could say we do a bit of business with these compnay's.

I don't mide asking question but when they are completly off the wall. I had a system with a bad MB (I know this for a fact because i tested it myself.). The system would not POST. The HP tech asked me 3 times to put in the quick restore CD. First off tell me how a system restore is going to fix a hardware problem. Second an orgainzation of our size would never use the standard HP image. You wantto ask me some reasonable fine. Don't wasit my time and your time with rediculous questions. I swear these phone techs are the same people who put masking tape over their VCR because they can't figureout how to program the VCR.

oakfan52 said:

When the HP tech tells me to clear the CMOS when the PC will not power on there is something wrong. I am not some run of the mill customer. I represt the nations larget dental care provder. One could say we do a bit of business with these compnay's.

Click to expand...

umm, clearing CMOS can solve a no-boot issue. I've had it happen before. drain the power from the caps and jump the cmos pins for 10 seconds and power back on... defaults restored

Stang Man said:

umm, clearing CMOS can solve a no-boot issue. I've had it happen before. drain the power from the caps and jump the cmos pins for 10 seconds and power back on... defaults restored

Click to expand...

Ya i'll let ya know when a clearing the CMOS solves a "NO POWER" ISSUE .

oakfan52 said:

Ya i'll let ya know when a clearing the CMOS solves a "NO POWER" ISSUE .

Click to expand...

I've never heard of clearing CMOS with absolutely 0 power fixing anything. I have however witnessed the fans turning but nothing else, no beeps no nothing. Figured it was a bad motherboard. Turns out CMOS battery was bad, replaced it with a brand new one, BAM system came right up and back into windows.

it was beautiful *sniff*

oakfan52 said:

Hrrm thats intersting. You should know that when you delete a file from a network drive it never goes to the recycle bin

Click to expand...

You never know with people. Sometimes they keep stuff on there desktop or local drive no matter how many times you tell them to keep it on the network. Plus this was a new client so I wasn't sure what there level of knowledge was.

I had a CPA once go through the directories on her local drive just to put files in the local my documents folder.