Computer uptime: 156 days
Don't worry, tomorrow's ticket will be "It was doing it every time before you got here"
No one who's worked in IT ever thinks it's going to be a quick ticket.
Attempting to access the keyboard in order to physically unmute the mute button for the HR director in a live conference spanning five continents, while being yelled at and called "incompetent" for "not knowing how to do my work", in front of the entire board of directors, by the HR director, was probably the longest goddamn minute, can confirm.
I had this near exact situation happen. I turned around and in a calm tone told her “I need to to stop trying to do my job over my shoulder and if that’s an issue I can get my director to come and resolve this for you” (my it director and her were buddies) she became silent in shock I assume. Resolved the issue a minute later (video feed issue). Walked back to my office and got fired for my comment 2 hours later.
Wow, that's fucked up.
everyone treats these anecdotes like funny little isolated instances but they really paint a constellation of just how oppressed we all are in many tiny ways. people just accept the massively biased power balance as normal.
idk what’s wrong with us man. all this time and we’re still here bopping each other on the head.
"You're on unmute."
'So de-unmute me, come on!'
Whenever I’m in the middle of something and I get a message from someone high up on the org chart.
“Hey, got a moment for a quick question?”
Me, internally: ‘Ah, fuck.’
Externally: “Yeah, totally!”
"ticket number?"
see I just ignore that shit until I actually have a moment, if it were important then they'd have said what it's about
I'm not IT. but I can't imagine being IT would change my response
and given that my job is often 4 hours straight of running from one fire to another, it could be a while until they get a response
That’s part of the gig in many IT roles. You have to be at least partially available for IT help requests.
Well I still do sometimes but I am a very slow learner. In my defense, I've only been in the field for 20+ years.
When I worked phone support I'd say about 50% of incoming calls were easily identifiable as quick tickets, cuz I knew I wouldn't have the access, tools, knowledge, or some combination to deal with it. Just document and escalate. Hell those were quicker than the supposedly quick and easy password resets. Thinking I'd actually figure something out or getting roped into remoting in because they don't want to wait for someone is where problems would arise.
I think I have learned about seven separate ticketing systems at my work, so far. The specialized ones are associated with small teams I know and can go harass if they don't answer in a reasonable time frame. The big main one, the associates reliably answer quickly, to let me know they can't help me. It all feels very broken.
I always liked these problems because I'd likely have to tinker around in the registry.
As "The IT Guy", having to call another with this shit is the stuff of nightmares. Like, are you suuure you can't just make me look like a fool and get this over with so we can both move on with our days?
And than the other joins the call and asks the client, again, to click on the basic option and run the basic command. What you just asked them to do. Like you're some moron who would forget to do a basic check. And than it turns out that you are a moron who forgot to do a basic check.
Rather find out I'm a moron than be stuck all day, or have to call for parts or schedule a "once we've figured it out" return visit. Doesn't happen nearly often enough for me to be upset or insulted by it.
100%. I've done IT support. If I've called you, you either have access I don't to solve my problem or this ticket is gonna take a week to resolve.
Honestly I prefer a good stumper, usually. If it's some bullshit that Microsoft did, then we're both going to be sad. But if it's an interesting problem and I can (mostly) figure it out, that's way better then fixing the same thing over and over and over and over again.
Same, they're like puzzles.
Not directly relevant, but this reminded me of the joke that debugging is like a murder mystery where the programmer is the detective, the murderer and the victim.
90% of the time I put in a ticket, it's just Microsoft being shit
it annoys me too, but I have come up with a few stumpers for our IT company. even once got to sit in on a call of two guys from our IT team and two engineers from the service's team as they tried to figure out what was going on. and there's me not understanding networking at all just laughing my ass off listening to them discuss what might be the problem
Not pictured, the 15 prior tickets where it was in fact a simple fix.
They refused to turn it off and on again. Typical.
As an IT guy I fucking hate you
I secretly broke it real bad so we could spend the day together! :3
That'd be actually really sweet.
Now kiss!
Aww! 🤩
if it were simple, I wouldn't have made a ticket, I'd have fixed it myself
God I used to hate it, they'd put a ticket in and immediately go to lunch or go home.
I'd go to their desk, ticket vague AF. Every damn time, I'd have to get their manager to call them to go over the ticket.
My department at work has made what I’m just now naming A Deal With The Penguin.
We pretty much don’t get IT support, but it’s because we can run Linux!
Things like broken hardware or locked out M360-AD accounts are another matter of course. But come to think of it, the front desk admin ordered me a replacement part once, and we have a dedicated website for resetting and changing your password. So other than initial onboarding years ago I don’t think I’ve used them at all. lol.
People Twitter
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a pic of the tweet or similar. No direct links to the tweet.
- No bullying or international politcs
- Be excellent to each other.
- Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.