Another example of Corp. stupidity

[cobra]

Ok, so the company I owrk for has offices around the US, and most of the sites have a LAN admin...We have 2 onsite payroll employees, (don't get me started on when we did not have any)
but the payroll "headquarters" is in Texas...the payroll "bosses" supervisors are there. Well we have been having trouble with our Kronos time clocks for about a year, payroll has had us change all of the time clocks out like 3 times in the past year (since we had no payroll person here then)...reason: "we can't collect the data off the time clocks"
Well, like I said, we switched out all 12 clocks 3 times...anyway, I could go on and on about that...

I got a call from the payroll supervisor last week, he says:
John, what speed is your network?
I say 100mb
he says: well, we need to slow it down to 10mb, because 100 is too fast.
I say, (long silence for "tard" laugh) um well, our switches are autosensing and will work with 10mb devices.
He says: well that won't work, we did this at another site and it worked.
I said: well give me the site name and I will call that lan admin to ask him about it.

There was a little more tech talk, but the point is, I and the rest of the guys here were laughing so hard the rest of the day.
Just another one of those, "how did he get that job" stories.

[WJWheels]

Sounds like that commercial, "All I know about computers is that I want a better one than anyone else!"

[doctorgonzo]

I remember that at my last job we had to replace the Kronos time clocks because they weren't Y2K compliant. Since I worked New Year's Eve that night, it was fun seeing the old clock (it was still hanging there, next to the new clock) say that it was Jan 1, 1900.

Hmm, I guess that was apropos of nothing...

[homer15]

too fast? that's like saying a chair is too comfortable...

[Christoph]

lol - that's a good one!