Hey, everyone, welcome back to the course in this video. We're gonna talk about the system administrator job role so we'll talk about what a system administrator is. We'll talk about some of the common job responsibilities that you might do as a system admin. We'll also talk about some of the common skills that you're gonna need to be successful at the job.
We'll talk about common certifications that a sys admin might have,
and we'll also talk about the general salary range forces sad mons with salary range on all of these videos. I just want to make note that these can vary and they can vary significantly based off where you live in the world, as well as where you live in your country and the particular company, as well as
the particular responsibilities of the job role. So you'll see kind of a bigger range
for is this admin on the salary and just know that it doesn't mean that you're going to get a salary in that range. You could get less. You could even get Mawr. It's just kind of a guideline for you to understand how lucrative this particular job role might be if you're interested in it.
So what is this system administrator or sys? Admin will basically thes air the individuals that are responsible for the infrastructure of the organization's technology so they're responsible for things like the configuration of different systems maintaining those systems on a day to day basis. In some instances, a sys admin might also be doing
some help desk type of work, depending on the size of the organization. But generally speaking, there, the server people there, the people in there doing the infrastructure type of work and not necessarily answering the phone for the help desk roles.
These also working with different endpoints besides just servers.
So what are some of the common responsibilities you might have as a sys? Admin? Well, number one being automation. So you don't want to do every single task possible manually. So you're gonna be responsible for figuring out what you can actually automate. Thio either speed things up or to save your time where you could go work on other things.
Patch management is a very, very important part of it, making sure that you're keeping software up to date, making sure that you're identifying once if you've got a security team and your organization making sure that once they identify vulnerabilities and they say, Hey, update this software, apply these patches that you actually do it as this assignment.
And if you're in a smaller company where you're kind of handling all that stuff, where you that sort of Jack or Jane of all trades?
Making sure that you have a good patch management process in place, performing things like server health checks, just making sure that there's no maintenance needed and making sure if something needs replaced that it is getting replaced. Same thing if you're using the cloud environment that your organization, making sure that you're checking all your cloud infrastructure and making sure things are up to date
performing backups of systems and being able to restore from backup, especially when we're talking about things like disaster recovery,
making sure that the applications are compatible with other
applications as well as the infrastructure if you have in place. An example of this is a health care company. I used to work at a long time ago. They were a smaller organization and they were looking to move to the cloud and what they found was that one of the applications, which was a pharmacy application, wasn't compatible with
later versions of Windows Server in the later versions of Windows Server were required
to actually implement the cloud environment. So
they had to figure out a new solution for the pharmacy software. And that way they could actually transition most of their infrastructure to the cloud. So as a salmon. Interesting to make sure that you're testing and identifying if there's any compatibility issues of those different applications and then, of course, hardening systems, right, So going back to things like patch management
removing services, we don't need removing processes. We don't need locking down user accounts. So if we don't need someone to have administrative access, we make sure they don't have administrative access. So all of these air, some common responsibilities for us, a sad, been.
So what about skills?
What are some common skills? Well, it's good to have an understanding of networking. You don't have to be at the level of like a network architect necessarily is a statement, but you really need to understand how data is flowing across the network so you can identify how you can best help protect it and, again, a smaller organizations.
I worked in a blended role. Where was Sys admin work network and engineer
slash admin work slash architect work.
It was also security work as an analyst work
as well as pen testing like it was kind of a jack of all trades, so to speak, role so at a smaller company might be doing a lot of this stuff. So it's important to build that skill set
for yourself so you could be more successful in the role.
Also, we talk about Patch management, right? So you need to be comfortable with implementing patches both on a test network and then also rolling about to production and identifying if there's any issues with the patch in the production environment being comfortable performing backups and also recovering from those backups
being comfortable with different operating systems. So things like Lennox Windows to some extent Mac, but primarily in the enterprise environment, Windows and Lennox,
some scripting skills, air helpful for the automation part of things so you can automate different task you're doing, It's It's also good to have experience in the command line as well as experience of power shelves. If you're gonna be working with Windows Server, which a lot of bigger companies are working with. In fact, most companies I know of off the top of my head are working with
Windows server environments, at least in some capacity.
So power show is gonna be an important part of that as well and understanding. Virtual ization. That building a skill set?
probably not so much with, like, virtual box, but mostly with VM ware in the in the typical enterprise environment as well as in some instances, hyper V
and then understanding
mawr cloud related things. The building skill sets in that so things like containers, kubernetes, etcetera and understanding different cloud environments like a W s is your and even Google Cloud
depending the size of your organization. It's a good idea for you to build some skill set and intrusion detection, monitoring and, you know, intrusion detection, prevention, firewalls, etcetera, etcetera. So kind of more of the security side of things.
We're just understanding how those things work can really help us assist admin.
So what about certifications? Well, there's a whole lot of different ones you might see SS admin get,
including a place which I don't have listed here. But that's typically more help desk type of thing. And that's why it's not on my list.
So is your administrator Associate is a cloud cert
for, uh, where Microsoft kind of went. Is there on more of the job rule certifications now? So they've taken away things like the M. C s A. Which was the Microsoft Certified Systems admin. Or they also took away the M. C S C, which was the, uh to a systems engineer, the Microsoft Certified Systems engineer.
So they've taken away. Those have gone from or more of the work role type of thing. So is your administrator associate is one search you might want to get as a sys admin. And, of course, some of your fundamental search like network plus Lennox, plus even security Plus to understand from the security side of things.
working with a lot of virtualization and you're interested in
getting a certification around that VM, where does have a certified professional assert and there are some people that get that as well that work is too sad Mons
And then, of course, red hat Linux certifications. So the Red Hat certified system administrators. Another one is well again for most tech rules. You don't have to have certifications,
but some of these are good toe. Have to kind of get your foot in the door and get past that HR filter that we usually see.
So let's talk about salary now. So you noticed a range here in the U. S. Is pretty wide, right? 50,000
up to over 160,000. In fact, there's a few
sys admin is I know that they're very experienced, so these were not entry level. They're very experienced, and they're making a little over 2 20 base salary right now. So, yes, you could make its lucrative. You could make a good amount of money. Realistically, starting out, you're probably looking at
the 50,000 range. Maybe 40,000, depending on the size of the company, may be up to like 60 or 70 if it's a larger enterprise. So again, it's a big range. A lot depends on your skill set,
your experience and also your ability to negotiate in an interview. So don't forget about those soft skills and any of these roles that we discussed in this course,
soft skills like negotiation skills, negotiating your salary,
vacate extra vacation time. Whatever those things are important. Communication skills are very important as well.
So just a quick, quick question here for you. Common skills that are needed as a sys admin include which of the following ones is that networking? Is it hardening of systems or is a disaster recovery?
All right, so you get all of them, you are correct. Right again. You wanna have a good understanding of networking and how data flows across a network. You also want to be able to harden systems and make them stronger against attack to help try to mitigate some of the attacks you might face. And also you need to understand how to both perform backups and restore from backups in the context of disaster recovery.
So in this video, we talked about what assists admin is. We also talked about some of the comments, skill set and common responsibilities you may have as a sys admin. We also talked about some of the common certifications, and we talked about the general salary range for assists, admin role as well