Hi all, I would like to ask here an opinion for a serious thing, because for me Yea Forums is a serious business

Thank you user

>Are you familiar with subnetting?
>Switch/Router CLI config?(If not i'd recommend packet tracer)
>telnet/ftp/ssh
>hierarchical network model
>ip classes
Just to get you started
Also probably a good idea to familiarise your self with network troubleshooting tools such as -nmap or wireshark

I know well telnet, ftp and ssh, and nmap.
I looked a bit of wireshark, and I'm learning about switch/router CLI just in these weeks with the ccna r&s.
Thanks for the tips user

But don't stress too much user, i don't work in networking anymore as i've moved onto software engineering but you learn a lot from the people around you. A lot of Sys Admins i ran into didn't have any form of qualification. If you'd like to shoot me an email i can send you some resources for study etc ([email protected])

how does he get his first role looking after 50 PCs, from looking after 4-5 PCs?

Maybe Im wrong but I think you either go to sysadmin or to Networking. Latest probably needs a lot more knowledge, but not 100% sure. Suggestiin for sysadmin: Im not sure the situation there (check job descriptions) but here for sysadmin roles they dont really require certs and what is really need you start to play with related things at home and mention this in your CV and have some decent basic knowledge. So if they ask you will able to talk about what you have tried which difficulties you had, or just answer some tech questions.

From my experience you go in as a junior network administrator, then from there you would shadow a senior sys admin, and they will get you to perform small task that gradually increase in difficulty and importance example configuring group policies for users. Not sure how much python automation companies use now so can't really comment on that

also google for questions for job interviews of .....
In smaller companies you have chance to work with network sometime while you are mainly sysadmin. In larger companies you either in network or sysadmin role

That is true to some extent, i've known people who take on both roles, for example in a small company. But some network engineers move around and configure business networks.

But feel free to shoot me an email if you need text books [email protected]

network engineers never working with sysadmin things. but yes agree on that mainly smaller companies gives you chance to work with network and sysadmin too but mainly you never touch networking much only if there is some new config or upgrade. So basically you are working with networking painlessly little bit.

if you are ok with windows sysadmin role (seems you had more knowledge about windows) than do different AD related tasks, if possible learn some powershell, have practical knowledge about what some windows cert cover. Go with one windows server line. If they want to know how you do this and that some other windows server version than you can tell how you need to do that for the windows server X which you had practiced with and you can tell that for windows server Y you can check if that works similar or you google the difference when you need it.

don't waste your time with networking and sysadmin bs.
learn how to program instead.

this

think programming bootcamp would be sufficient or cs degree is a must?

twitch.tv/gentlemandogg
8

I actually dont think many people use Hyper-V. We actually have one but just for some experimenting cases. V-Sphere seems like the better solution, VM-Ware you know?
You should know your share of setting up and configuring firewalls. Sometimes this cam be really tricky, especially in networks where specified computers are only alowed to communicate through specified protocols with other specified computers. "Server A only gets traffic from Server C via HTTPS(443).
Domaincontroller configuration should be also pretty important. I think most companies use a Windows Server with Active Directory, but knowing LDAP should also be helpful.
While you're at it you may also be able to read intoi Citrix solutions, XEN-Server and stuff.

enough bump OP? Looks like the thread is going, remember to thank the faggots replying to you

i don't think a computer science degree is a must, but a deeper understanding of how computers work, software design principles and a little bit of math is a must.
i've seen people without a cs degree who knew their shit better than anyone with a cs degree because they had a passion for what they were doing.

Sorry for the late, I would thank all of you for the advice.
II will put together what you have advised me with what is required in job advertisements, and I will start studying.

Attached: 17795763_1490950587613691_9008904495538339476_n.jpg (960x521, 74K)

I don't think programmer role would be superior than networking or sysadmin. But true that machine learning may be a big impact for these roles in future, changing a lot of thing.
Choose any direction you like, check job requirements for get more and more clear picture which knowledge would be great but try to narrow your focus, try to learn one or two thing at once only. Do as much practical exercise as you can. Ppl are more often employ someone who has some experience behind what he/she learnt and met with some difficulties and they see how it got solved. Which means you interested to learn and practice even by yourself, not only if you are forced to do so.

Just get an AWS cert and you are good to go anywhere.

Scaramouch, Scaramouch will you do the Fandango?

This, installing and setting up AWS shit is a fucking goldmine, 2 grand a day in the UK on a consultancy basis

A cert does not really get you anywhere. And seems more company using Asure than Amazon cloud. Getting practical knowledge first and cert is ok later too if you really want one. If you lucky the company even paying for your future certs.

I have to correct myself. Some country really into certs. If you live in one of those then yes you may really need a cert or two for able to get some decent job. But someone from UK may able to refer to this.

You have to put the time in is all. I worked in enterprise IT for several years but started at small shops like you. Best way in is to work either for a consulting business or learn and master a specific skillset. I hired a dozen guys like you over the years, it just takes time. Certs are pretty useless these days. Every IT leader hates when a person gets a cisco cert but can't trunk two 2960s together outside of a lab. Experience is king, hang in there.