should i take Server 2012 or 2016 classes?

at my local community colleges, only Server 2012 classes are offered. Is Server 2012 knowledge still in demand from employers?

Find more posts tagged with

Comments

poolmanjim

I think it makes sense to take 2016 classes. The differences between 2012 R2 and 2016 aren't so dramatic that the stuff you learn won't translate between the two. It generally makes sense to future proof as much as you can by grabbing the most current training available.

If you can only find 2012 classes, then they should be fine. Companies are still using 2012 R2.

NetworkNewb

I second the 2016 classes

malachi1612

2016 classes, no point starting Server 2012 now when you have Server 2019 due out at then end of this year. Server 2016 will be more future proof.

blargoe

Skip 2012.

shihku7

well then, i may wait and hope that Server 2016 classes are introduced at school soon

shihku7

Also, I just got my CCNA a few weeks ago. Should I get MCSA Server 2016 or CCNP R&S next? I'm leaning towards Server 2016.

poolmanjim

shihku7 wrote: »

Also, I just got my CCNA a few weeks ago. Should I get MCSA Server 2016 or CCNP R&S next? I'm leaning towards Server 2016.

A couple of things to consider with that kind of question.
1. What is your interest? Are you interested in Networking or being a System Admin/Engineer?

I work as a System Engineer and I know of only one guy in my group who has a CCNA (and its expired at that). On the flip side, I know a ton of Network Engineers and most of them don't have a lot of experience in the Microsoft side. You want to try to come up with a focus.

2. Gauge this against your experience. If you don't have much workplace experience, you can have a dozen fancy certs and all that means if you can pass tests. Certifications only go so far and at some point you have to have some experience to back it up.

3. Don't over qualify yourself. This follows up on Number 2. If you are applying for help desk jobs and you come in with a CCNA and MCSA that may actually disqualify you as being too experienced for the role (I realize this is a bit of a catch-22 with my previous comments).