this post was submitted on 24 Apr 2024
995 points (98.3% liked)
Technology
57703 readers
5225 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nothing personal, lol, but I stand by my quotes.
I feel like sysadmins need to be comfortable in multiple environments. I also work with some really crappy ones who only know how to reboot a faulty system or crawl to Microsoft for support. No reviewing logs, no digging in at all, just "welp, a reboot didn't fix it. Gonna submit a support ticket and make no further effort".
There's a lot to be said for a good generalist, but at some point, specialization takes you farther. I ended up with Windows server and Active Directory, as well as Exchange (lots of other stuff, too, but those are the main things). Apart from mass workstation management, or when a help desk person asks for a hand, I haven't dealt with non-servers in a loooong time.
My last few experiences with Microsoft support (spread over many years) have been "If I can't figure it out, Microsoft probably can't, either." For a smaller company, with a limited IT staff, having someone who is able to efficiently interface with vendor support without necessarily having all the answers themselves can be a useful thing. But I totally get what you're saying.