I'll just leave this here...
https://www.youtube.com/watch?v=YLdK9zaLaG8
Printable View
I'll just leave this here...
https://www.youtube.com/watch?v=YLdK9zaLaG8
Coworker: Why do the replies to emails I send keep ending up in the group mailbox?
Me: Because you're either originally sending using, or replying to, emails that are in that mailbox.
Coworker: When did they change that?
Me: 1999.
I had to help somebody edit a windows Hosts file today... (so 127.0.0.1 would work instead of ::1) --Quote:
Coworker: Why do the replies to emails I send keep ending up in the group mailbox?
Me: Because you're either originally sending using, or replying to, emails that are in that mailbox.
Coworker: When did they change that?
Me: 1999.
I used my domain admin account & the administrative share, browsed the users c, opened the file in notepad, made the change, saved it.
"Wow! when did they add that!"
That's ALWAYS been there.
"well, I know DOS stuff, I DOn't know this new stuff."....
Did you want to watch me do that in DOS commands? This could have been done command line. If you could have done it command line, why didn't you?
Transcript from an IM session
Coworker: i am WFH tried to log in network but kept telling me the login failed 9:13 AM
(She even sent me a screenshot): Screen capture 9:13 AM
Me: the VPN login? 9:13 AM
Coworker: yes 9:13 AM
Me: Did you change your password recently or get the notification emails? 9:14 AM
Coworker: no same pw when i login every day 9:14 AM
Me: Try restarting? 9:14 AM
Coworker: i did but still not working 9:14 AM
Me: Then unfortunately you might need to call the Help Desk. That password is the same as your regular network password, and if that doesn't work, you shouldn't be able to log into the computer. 9:15 AM
Coworker: i know 9:15 AM.
so weired 9:16 AM. (she called the Help Desk at this point)
for some reason my vpn pw has expired but I didnt get notification email though 9:43 AM
Me: so are they giving you a new certificate or something? 9:43 AM
Coworker: yes they changed it for me now 9:44 AM
Coworker: aren('t) we supposed to get an email to change pw? 9:44 AM
Me: for the VPN? no. Usually that login is based off the VPN certificate on your computer. It automatically "learns" your current password 9:45 AM
Me: You do get an email for the regular network login two weeks before the end of every 90 days. 9:45 AM
Coworker: so since i haven't changed my current password why my VPN password was expired? 9:46 AM
Me: I don't know 9:46 AM
Coworker: is it something i should be concerned about? 9:47 AM
Me: Only if it happens again 9:47 AM
Coworker: now i have to enter my user id and pw (the new one she gave it to me) in order to access network apps 9:48 AM
Me: at least it works 9:50 AM
Coworker: shoot I just saw the email from IT service about my pw is due to expire
...
Frustration with other tech again...
So, an Email comes in stating somebody's name got screwed up in the email Global Address book. (Just the display name) - So I start fixing, and composing an apology letter to the affected person.... Other tech starts talking to the office manager about the problem and about how the problem could have happened.. and OMG! What do we do?
We correct the fucking typo and go back to your regularly scheduled day dipshit.
Oh, how I *LONG* for the days I could fucking do THAT.
Our AD is populated by a bunch of behind-the-scenes scripts that populate from the HR Software's Database.
Nightly.
As in a full push of the database of active employees over-writes Active Directory nightly.
Put someone in a group when HR doesn't have them set to be there?
They get pulled out again at midnight.
Correct the spelling of someone's name?
Reverts at midnight.
Fix a fuck-up HR made by putting the new VP or CEO in entirely the wrong subset of departments?
Reverts at midnight.
This means that when HR messes something up, it STAYS BROKEN until *they* figure it out, THEN we get to wait...
...you guessed it...
...until midnight.
Now, this wouldn't be a HUGE problem, except for the fact that SOMETHING is wrong with 8/10 new hires...
...and HR is so utterly concerned with fixing it that it typically takes the better part of a week on their part.
My favorite was the one where they took a part time temporary employee and hired him on full time.
They "terminated" his temporary employment and created a full time employee labelled username2...and our Exchange farm is set up so that when your employment is terminated, it remote-wipes your cell phone.
So, since we got to add his old e-mail address as an alias for his new one, his phone was getting wiped over...and over...and over...and over...for about a week because he was setting it up with his alias e-mail and the system said "WIPE THAT PHONE!".
But but but... automation saves time and money!11!
only if you do it right and you don't have a dozen trained monkeys doing the initial input.
That seems like a lot of overhead for little practical benefit to me. But then, my AD is comparatively small - only about 200 users.Quote:
Nightly.
As in a full push of the database of active employees over-writes Active Directory nightly.
Guy calls our dispatcher saying he's locked out of his account.
Dispatcher resets his password to "Company2015". So, "Company 2015 with a capital C".
Spends TWENTY MINUTES on the phone with this guy, trying to get him into his machine.
Can't do it.
Dispatcher escalates the ticket.
He gets in.
Then, unlike your average everyday user, he calls back and says:
"I thought this would make you laugh. I'm a moron. My wife called me an idiot.
I was typing "company2015C". Thanks for being so patient with me."
This guy is now on my "help instantly no matter what" list. :)
Nice.Quote:
I was typing "company2015C". Thanks for being so patient with me."
This guy is now on my "help instantly no matter what" list.
Yeah, scale does change things.Quote:
10 times that here.
Still seems interesting to me that they would take an IT function (User Accounts/Group Memberships/Domain Security) & place that in the hands of Non-IT people, even if it is "automated".
Gah, people like that rile me up.
Shit happens. Mistakes happen. You fix them, look at what went wrong, and move on. VERY RARELY do you need to escalate the issue to managers.
In my experience, the people who treat issues this way are the ones with too much time on their hands. The rest of us are busy actually making things work.
Yes.Quote:
In my experience, the people who treat issues this way are the ones with too much time on their hands. The rest of us are busy actually making things work.
*as the admin
It's so ridiculous it's funny. I mean, it's an honest mistake and the person in question (who was getting it wrong) was getting REALLY irate (but not abusive).
The thing that really set this caller apart was that he CALLED BACK and admitted his fuckup.
That kind of stuff gets you put to the top of the "gets the fastest help possible" list.
You *will* get put ahead of other tickets.
Callers won't be put on hold or anything, and outages still come first, but when we're to the point where we're choosing which tickets to tackle and there's nothing higher priority looming?
Front of the line.
I definitely tend to help the people who understand they are the problem before people who just drop their problems in my lap because they can't be bothered to try.
I think a good slogan for Google would be "Google, is it really that hard?"
I work for a small company of 20 people. Every damn one of them believes that their password gets changed behind their back. Every. Damn. One.
Some pretty sweeping changes related to the way the program updates its data structures are being tested for one of the products I support.
As a lead, I received an advanced post-alpha pre-beta copy and have been playing around with it.
I've pointed out some changes to the QA manager (the lady who actually packages the installers as well as finalizes testing).
She looks at one of my screenshots and starts to panic.
(I can't include any for various obvious reasons, but...)
And her email (paraphrased)Quote:
Originally Posted by mine
Maybe she needs to change her file compare tool to show KB instead of bytes...Quote:
Originally Posted by her