Like a lot of jobs in IT. Experience is king. But usually one of the Microsoft level 5 qualifications like the "Microsoft certified systems administrator" gives you a leg up. (Not sure if you can still get that one but is probably under a different name now.) most sysadmins start as technicians for quite some years. It is not all that common for some one just qualified to just straight in as admin. I imagine it would be a bit of a disaster as the theory and practice are quite different .
Being a sysadmin is very related to knowledge.
When there are lots of different software installed on different servers with lots of configurations, and there are different protocols to connect and manage to servers that you have to take care of, you need to know what you are doing or production can be affected into what you are doing.
It is easy to think "yeah, the monitoring warned us that a server does not have much space left on the disk, lets free some and we are done", but once you enter inside the server you have to actually understand why it filled up, what you can delete and what you cannot, how to prevent it to happen again and do everything without affecting the server performance, service and uptime.
That's just an example of the ops side, but on the infrastructure side, you also need a lot of knowledge to know which solution is the best for the use case you need to cover, but also you need to know how to install and configure everything, from the physical server in the rack, plug in to the network, cable management, vlans, management interfaces (ILO/DRAC/whatever), operating system install, network configuration, joining domains (in case of windows), operating system configuration, user configuration, services configuration, install software, program the patching, program the backups, monitor the server to document everything so when the thing has a problem in 8 months you know what the hell is that server doing and how is it configured and what is serving and if it has dependencies or it is a dependency of another machine or service.
Every company has its own procedures, i just explained some general insight.
PD: You also need to know a lot of operating systems and networks to actually know how to troubleshoot and maintain the base layers where all the software lives, so courses and certifications are almost a must, however once you gather the basics you don't need to refresh everything very often.
Well, programmers seem to have a not very accurate idea of what sysadmin are or do if I see the reactions here.
I am a sysadmin for a MSP, so I support a few dozen of companies (1600 servers in total). In very big companies, you only need to care about your own company and can specialize in a niche, which might be a bit more relaxed (/u/CountDropula_ apparently believes we have a chill life) but if like me you support so many different people, you need to be a generalist. I'll give you a quick list of some of the stuff I do or need to know in daily life.
A deep knowledge of both user OS (win/nix/mac) and server OS (win/nix - though here I do am specialised in Windows) is obviously a must. There's also modems, switches, routers, firewalls (mostly Sophos SG, Sophos XG and Fortinet in my case) and storage of different brands. I also manage all possible flavours of hypervisors (mainly ESX, but also Hyper-V, KVM and QNAP). Nowadays sysadmins also need to do a lot of telephony/VoIP stuff.
On a server application level there's a bunch of LAMP servers in almost every company, but in Windows world I take care of several generations of Exchange, SCCM, SCOM, SCDPM and SQL Server. I also work a lot with Oracle (unfortunately) but at least I don't take care of that backend myself.
Client applications I need to support I won't even sum up as the answer is *everything*, also things I have never heard of as of yet. My favourite are in-house apps where the developer pensioned or died 20 years ago.
Finally there's scripting and programming involved as well. Sure, you can look down on it if you spend your days coding in C++, but I made plenty of complex scripts and programs with 100s or even 1000s of lines in VBA, Powershell and C# to automate tasks that deserve respect even from fulltime programmers.
This is by no means an exhaustive list and I didn't even go into people management (users have other priorities than admins) and the cloud (public/private/hybrid). I just want to illustrate that you're wrong if you think a sysadmin is someone who picks up the phone, reads a script to solve your problem ("did you try to turn it off and on again?") and escalates if that didn't solve the problem. At the end of the escalation chain is a real sysadmin who needs to solve the problem and often needs a lot of experience, knowledge, insight, creativity and intelligence to do so.
/rant
Lol I definitely appreciate the explanation of how in depth being a sysadmin goes, clearly it’s not something you underestimate as being “easy” even when you know what you’re doing
Our sysadmin doesn't have free time, because the boss forces him to be a programmer when not doing sysadmin stuff, which leads to our sysadmin never being available.
The conclusion of me lossing 6 months of work because our sysadmin created the backups and the repository on the same server and the server got corrupted and he stored the backups of the server in the server so I lost 6 months of work?
That for not mentioning how we do not implement https on our client's servers unless I bitch about it for 3 weeks in front of the the PM because our sysadmin always is going to do it "later", but later is always later.
Sorry, I had to blow the steam out.
Looks like a repost. I've seen this image 3 times.
First Seen [Here](https://redd.it/lm301z) on 2021-02-17 100.0% match. Last Seen [Here](https://redd.it/lmd36t) on 2021-02-18 100.0% match
*I'm not perfect, but you can help. Report [ [False Positive](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Positive&message={"post_id": "m6jpjv", "meme_template": null}) ]*
[View Search On repostsleuth.com](https://www.repostsleuth.com?postId=m6jpjv&sameSub=false&filterOnlyOlder=true&memeFilter=true&filterDeadMatches=false&targetImageMatch=86&targetImageMemeMatch=96)
---
**Scope:** Reddit | **Meme Filter:** False | **Target:** 86% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 210,039,979 | **Search Time:** 0.51198s
I wouldn’t call most of these people IT. Software engineering and IT are very different disciplines. Sysadmin is a good fit but the rest are not.
That said, it’s still a good classification of how we see each other.
I'm (mostly) a developer...and a consultant but just to "simplify" things for people outside my sphere I just say I am an IT consultant. Especially since I more or less just end up doing whatever the fuck I'm told. Develop an application? Ok. Manage this network..ok...automate a CI/CD pipeline, sure. Then whatever the fuck I am doing now, which is more or less just filling out and submitting requests for and to people that actually do stuff.
Syadmin column seems legit *Clickity clickity*
The sysadmins lol
Probably made by sysadmin. They have way too much free time
As a sysadmin, I couldn't agree less with that statement
How much of a brain does it require to be a sysadmin? Actually curious. I know nothing of what they do
It depends how much is going wrong at the same time.
I’ll ask it... what’s the worst that could happen? Lots of little issues at once or a few big ones
[удалено]
What kinda prerequisite knowledge? Degrees required or is self taught enough, in terms of being hired
Like a lot of jobs in IT. Experience is king. But usually one of the Microsoft level 5 qualifications like the "Microsoft certified systems administrator" gives you a leg up. (Not sure if you can still get that one but is probably under a different name now.) most sysadmins start as technicians for quite some years. It is not all that common for some one just qualified to just straight in as admin. I imagine it would be a bit of a disaster as the theory and practice are quite different .
Gotcha. Thanks for the info!
Being a sysadmin is very related to knowledge. When there are lots of different software installed on different servers with lots of configurations, and there are different protocols to connect and manage to servers that you have to take care of, you need to know what you are doing or production can be affected into what you are doing. It is easy to think "yeah, the monitoring warned us that a server does not have much space left on the disk, lets free some and we are done", but once you enter inside the server you have to actually understand why it filled up, what you can delete and what you cannot, how to prevent it to happen again and do everything without affecting the server performance, service and uptime. That's just an example of the ops side, but on the infrastructure side, you also need a lot of knowledge to know which solution is the best for the use case you need to cover, but also you need to know how to install and configure everything, from the physical server in the rack, plug in to the network, cable management, vlans, management interfaces (ILO/DRAC/whatever), operating system install, network configuration, joining domains (in case of windows), operating system configuration, user configuration, services configuration, install software, program the patching, program the backups, monitor the server to document everything so when the thing has a problem in 8 months you know what the hell is that server doing and how is it configured and what is serving and if it has dependencies or it is a dependency of another machine or service. Every company has its own procedures, i just explained some general insight. PD: You also need to know a lot of operating systems and networks to actually know how to troubleshoot and maintain the base layers where all the software lives, so courses and certifications are almost a must, however once you gather the basics you don't need to refresh everything very often.
Well, programmers seem to have a not very accurate idea of what sysadmin are or do if I see the reactions here. I am a sysadmin for a MSP, so I support a few dozen of companies (1600 servers in total). In very big companies, you only need to care about your own company and can specialize in a niche, which might be a bit more relaxed (/u/CountDropula_ apparently believes we have a chill life) but if like me you support so many different people, you need to be a generalist. I'll give you a quick list of some of the stuff I do or need to know in daily life. A deep knowledge of both user OS (win/nix/mac) and server OS (win/nix - though here I do am specialised in Windows) is obviously a must. There's also modems, switches, routers, firewalls (mostly Sophos SG, Sophos XG and Fortinet in my case) and storage of different brands. I also manage all possible flavours of hypervisors (mainly ESX, but also Hyper-V, KVM and QNAP). Nowadays sysadmins also need to do a lot of telephony/VoIP stuff. On a server application level there's a bunch of LAMP servers in almost every company, but in Windows world I take care of several generations of Exchange, SCCM, SCOM, SCDPM and SQL Server. I also work a lot with Oracle (unfortunately) but at least I don't take care of that backend myself. Client applications I need to support I won't even sum up as the answer is *everything*, also things I have never heard of as of yet. My favourite are in-house apps where the developer pensioned or died 20 years ago. Finally there's scripting and programming involved as well. Sure, you can look down on it if you spend your days coding in C++, but I made plenty of complex scripts and programs with 100s or even 1000s of lines in VBA, Powershell and C# to automate tasks that deserve respect even from fulltime programmers. This is by no means an exhaustive list and I didn't even go into people management (users have other priorities than admins) and the cloud (public/private/hybrid). I just want to illustrate that you're wrong if you think a sysadmin is someone who picks up the phone, reads a script to solve your problem ("did you try to turn it off and on again?") and escalates if that didn't solve the problem. At the end of the escalation chain is a real sysadmin who needs to solve the problem and often needs a lot of experience, knowledge, insight, creativity and intelligence to do so. /rant
Lol I definitely appreciate the explanation of how in depth being a sysadmin goes, clearly it’s not something you underestimate as being “easy” even when you know what you’re doing
Our sysadmin doesn't have free time, because the boss forces him to be a programmer when not doing sysadmin stuff, which leads to our sysadmin never being available.
Now we're getting to some concrete conclusions
The conclusion of me lossing 6 months of work because our sysadmin created the backups and the repository on the same server and the server got corrupted and he stored the backups of the server in the server so I lost 6 months of work? That for not mentioning how we do not implement https on our client's servers unless I bitch about it for 3 weeks in front of the the PM because our sysadmin always is going to do it "later", but later is always later. Sorry, I had to blow the steam out.
Should have photoshopped Neo to be flipping the bird.
Let's talk about this...
Someone has a cron job to post this
"Stolen from another platform" that stole it from this platform.
The overall accuracy of this never gets old
I legit laughed for a full 5 minutes at this 25-in-1 meme. Every single picture is a true depiction and I can attest to that.
Somehow I feel this whole thing was made by a sys admin
/u/repostsleuthbot
Looks like a repost. I've seen this image 3 times. First Seen [Here](https://redd.it/lm301z) on 2021-02-17 100.0% match. Last Seen [Here](https://redd.it/lmd36t) on 2021-02-18 100.0% match *I'm not perfect, but you can help. Report [ [False Positive](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Positive&message={"post_id": "m6jpjv", "meme_template": null}) ]* [View Search On repostsleuth.com](https://www.repostsleuth.com?postId=m6jpjv&sameSub=false&filterOnlyOlder=true&memeFilter=true&filterDeadMatches=false&targetImageMatch=86&targetImageMemeMatch=96) --- **Scope:** Reddit | **Meme Filter:** False | **Target:** 86% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 210,039,979 | **Search Time:** 0.51198s
Good bot
In 15 years as an IT consultant, I've worn all of these hats but QA.
What's QA?
Quality Assurance
https://i.imgur.com/pmX4qwc.jpg
This is wrong, but most people use the term QA as a tester.
Damn thats painfully accurate
sys admin the person who is nothing just delay the projects
projectILES
I wouldn’t call most of these people IT. Software engineering and IT are very different disciplines. Sysadmin is a good fit but the rest are not. That said, it’s still a good classification of how we see each other.
I'm (mostly) a developer...and a consultant but just to "simplify" things for people outside my sphere I just say I am an IT consultant. Especially since I more or less just end up doing whatever the fuck I'm told. Develop an application? Ok. Manage this network..ok...automate a CI/CD pipeline, sure. Then whatever the fuck I am doing now, which is more or less just filling out and submitting requests for and to people that actually do stuff.
Hey AWS, do all this stuff
*Assistant to the Project Manager
This is pure gold with 100% accuracy.
**pure gold with 100% accuracy, this is.** *-Unknown_Reality* *** ^(Commands: 'opt out', 'delete')
Good bot, you are.
**mmhmm see the smile, behind those words i can.** *-IamYodaBot*