What does it take to become a system admin? Are certs a good way to get a job after finishing high school?
> What does it take to become a system admin?
Patience and lack of self-love.
> Are certs a good way to get a job after finishing high school?
The ideal. You should aim for them ASAP since they'll help you develop experience.
A local computer shop had their certs listed and I looked them up, he had an expired Windows 2000 Systems Engeneer cert (or something like that) I asked him to remove it as it was legacy and potentially misleading. Needless to say he didn't and I'm not welcome there anymore.
Do most sys admins actually have to do more complex stuff like planning a whole intranet for a business or something?
Or are most just there like cheap apes that are there to replace failed HDDs?
Maybe if the company is really small they'd have their sysadmin take care of basic network maintenance, but for actual planning and implementation they'd contract it out to someone who knows what they're doing. Any decently sized company will have dedicated network admins.
Funnily most system admins I heard talking about their job said that they sit in front of the computer all day in a basement, browse the internet, eat cheap food and all that while getting fat and never seeing sunlight.
Oh and sometimes they have to work some plugs and cables, apparently.
>Patience and lack of self-love.
Well I sorta got that down, good thing I'm already aiming for that field, right guys?
I'm not miserable for no reason?
I'm doing it to myself, that's the only conclusion I can come up with.
>image new systems
>eat lots of peanut butter
>order some hardware
>fix gruntilda's keyboard
>jack off in the nice cool server room
>order some ergonomic keyboards
>ride around on the equipment dolly
>plug bob's speakers back in
>boss some interns around
>replace shannon's monitor
>make interns load old servers into your SUV
>clean birdshit off of nichole's laptop
>give interns your keys to dispose of garbage servers
>mail nichole's laptop back to her in the middle of bumfuck, nowhere
>get mad at people who using your office as a hallway
>restart the mail server
>complain to building manager steve about the
flickering light in the hallway
>change the tapes
>get called in the middle of the night
that's what mine does.
I graduated along with one of the two sysadmins at my company, he just recently graduated from the dusty storage room to a room with a door code, half of that is true, the other half isn't.
but seriously, we have a remote tech support rep who has something like 3 parrots, and there was bird shit literally covering her keyboard. she mailed it to us because it was broken, we get it, it's covered in shit.
if there was someone else with her knowledge willing to be a support bitch, she'd be gone by now.
oh, also, one time she went to australia, came back, and then was complaining that her internet was slow. something like 3 months later, she sends her system in, and she has her system pointing to an australian proxy server.
she's tech support in a nutshell, from the color of her skin to her level of sanity.
Network Engineer reporting in:
Applications for open system administrator positions, some industry experience and a few certifications if you work for anybody who is worth a damn, but good experience trumps everything.
Anybody you want to work for is going to research your educational and professional background. No, expired certifications are not worth anything in and of themselves, but if you have current ones of a higher level or in a different area, it's always a plus to have them for historical purposes.
All four of my IT employers have checked my certification status, as well as requested at least unofficial transcripts.
A system administrator should never be "planning" an intranet. That is not their job or their area of expertise. You're probably getting hung up on job descriptions in the SMB, where "System Administrator" is tossed around as frequently as "IT Technician" and means about as much.
In the "real" world, system administrators have a quite specific role, which is to administer the systems of that business. This should include all servers and perhaps some other things, like security cameras or something. Beyond that it's a different job.
The sysadmins I work with have no experience or skill with networks, that's my job or the job of a network administrator. Often both good network and system administrators will have some programming experience but by and large we're not at a professional level for that. You should never see a system or network administrator replacing HDD's unless it's in a server...that's tech support or desktop services work.
I'd like to say that network engineering, or even just administration, is an arcane magic. It's not, I happen to be good at it and have a lot of hard-earned experience in the field. A system administrator could not simply step in and do my job, at all. The same applies in reverse.
holy shit i just realized what a horror it must be working from home as a tech support rep while owning parrots
those fucking birds must be saying nothing but 'NICHOLE, SPEAKING, HOW MAY I HELP YOU' SQUAAAWK
im not in tech support, but you're right, im not a sysadmin. i'm friends with the sysadmin guys though. they don't talk to end users, but they do do tech support our office systems.
Then your friends need to get a better job. Replacing monitors, cleaning and ordering fucking keyboards?
They better be making the combined salary of an office manager, tier-1 technical support guy and a sysadmin if that's what they're doing...
our office isn't that big, we're a satellite office of a pretty big company.
yes, some things are handled remotely, and we couldn't operate properly if head office was suddenly nuked, but they're in control of the local office network and the upkeep of the servers that run here. that's close enough to sysadmin for me.
my friend's boss must have been out of his mind busy every day until my friend was hired to more or less do the bitch work for him.
>I'd like to say that network engineering, or even just administration, is an arcane magic. It's not, I happen to be good at it and have a lot of hard-earned experience in the field. A system administrator could not simply step in and do my job, at all. The same applies in reverse.
>my internet is down
ping the place the person is trying to go, if it does not work reset or fix it
Network engineer reporting in again:
When I was first starting in IT, as a computer tech, I once imaged over thirty PC's as they were being used...
Just last week I sent a script to an unsuspecting network admin who ran it without first reviewing. I made a typo on a single line; effectively mistyped a subnet mask in an ACL entry. The effect was that the traffic of several hundred users at a single site was redirected to a firewall when it should have been limited to a single office. It's always an interesting day when you see your resource monitors spike from maybe 15% utilization to nearly 90% in the span of a few minutes.
Most of my mistakes, even the horrible ones, have been fixed before a single end-user noticed. The same goes for the sysadmins I know and work with; that's why we often spend as much time planning for a rollback as we do for the actual change.
network engineers are typically designing and implementing networks, hence the name "network ENGINEER"
there's a surprising amount of shit going on inside your average switch/router nowadays, they're running applications and services just like servers and you have to know how to work their operating systems just like linux/winblows/whatever else sysadmins are fucking with
>why would you need a call manager?
>what is information securty?
>why would a datacenter care about throughput?
there's more to network design and administration than just pinging shit.
you're going to fuck something up in the field eventually
the absolute best way to handle it other than not wrecking shit in the first place is to accept responsibility for it and help do whatever you can to get it fixed.
people make HUGE mistakes that they should probably never touch a live system again after making and keep their jobs if they fess up and get help fixing it. others will get fired over something silly and simple to fix just because they wasted everyone elses time trying to hunt down the root cause while they could have just accepted responsibility and had it fixed in 5 minutes.
And that's why you're not a system administrator, network administrator or engineer in either discipline.
>And that's why you're not a system administrator, network administrator or engineer in either discipline.
oh boo hoo im not some faggot that nobody likes
do you think any real person wants that job?
cisco switchport configured with port security, sticky MAC addresses and restrict violation.
IP phone is replaced. how do you go about fixing?
there's nothing wrong with the 3,000$ switch and the phone has just been replaced
this is CCENT level shit right here you'd better be able to figure it out.
in general IT jobs are considered fairly lucrative. upon hearing the terms "network engineer" most people assume I'm doing pretty well. you can't say that about many professions.
You know what, you're absolutely correct. Who in their right mind would want to own a three bedroom, two bathroom single-family home in their late twenties? It's absolutely disgusting that my student loan has been paid off and my infant daughter already has $2,500 in her college fund.
Man, it sure does suck to be offered a blank check and a pen when some tech support ass-clown reboots a core switch that hasn't been backed up, with hundreds of changes made since the last write to startup config. It's absolutely not a good feeling when you save a small business from bankruptcy and come away with a nice deposit and yet another letter of reference.
I truly cannot fathom why somebody would like to go to work every day, being very good at something they've worked hard to be very good at.
Stay mad nigger, enjoy your latest iPhone.
>You know what, you're absolutely correct. Who in their right mind would want to own a three bedroom, two bathroom single-family home in their late twenties?
OMG DO YOU HAVE BRAND NAME FURNITURE TOO
fitter happier and more productive
Sorry friend, haven't made it to Ikea yet this week since I'm so busy being awesome.
If you give me your address, I'll send you some cash for the gym where you can pretend to be happy with your pasty gut and more productive on the Stair Master.
Pretty much, yes. But a CS degree will mainly just involve programming and theory. Funny thing is that once you have that degree you can pretty much do whatever after that, but not exactly vice versa. But actually you can do literally anything so long as you have experience and or hookups and or both.
(I wasn't referring to money made vs other degree like hurr durr math phd 300k starting vs IT 30k/yr, just saying.)
yeah or he could have had no degree at all, and just gotten a hookup somewhere and done the same thing. His brother works IT and has nothing but a realtor's license. The point is laughing about it is stupid, because in reality they are just pieces of paper and dont exactly dictate what you can and cannot do.
sociology is just applied psychology is just applied biology is just applied chemistry is just applied physics is just applied mathematics is just applied logic is just applied philosophy