Is Windows Server 2019 a good starting point?

[ukesilkeris6]

Hello,

I've recently begun my trip into IT. I've passed my A+ and I've read time and time again how important Powershell and Active Directory are in most businesses, and so that's where I'm aiming my focus when I'm feeling burnt out from CCENT study. I see many tutorials and documents about Windows Server 2012 and 2016, but not a lot yet on Server 2019. In addition I see many businesses don't focus on updating unless it would fix some problem or go in hand with a planned upgrade, and still use the older server operating systems (I believe I saw a recent post about upgrading from 08 while searching this subreddit). Would it be wise to start with the newest release for my virtual labs, or stick with the well-documented 16 or 12?

Thank you for your time.

[dmartin1018]

From a practical perspective, you tend to see businesses with many bespoke applications (and some schools) reluctantly upgrade their operating systems, usually as they approach end of life. Server 2008 and Windows 7 only really disappeared when Microsoft forced peoples hands and the same will be true of server 2012 and 2016. Personally, I needed to rebuild the server infrastructure when I arrived here and I did so with 2019 to future proof us. Plus, someone's gotta take the plunge to identify any bugs. Luckily, server 2019 is based loosely on 2016, there isn't a great deal of difference and I've had no issues (touch wood!).

 

From an exam perspective, Microsoft had MCSAs for 2012 and 2016 but they've changed their entire certification tracks last year and as a result there isn't one for server 2019. It's all rolled into the MS azure content allegedly so if you want to certify in 2019 content then that's the way to go.

[Michael]

For the purpose of testing, you won't really notice anything different between Server 2016 and Server 2019. In a live environment however, I still run Server 2016.

 

The code base is more mature than Server 2019, but it's still supported for many years to come. I guess it's a matter of preference and although someone needs to take the plunge and identify issues, it's also preferable not to run into such issues in a live environment.

 

Likewise monthly patches/security updates - even on Server 2016, you should approach with caution as Microsoft do release bad updates.

[free780]

I've found 2019 to be better quality than 2016. Just see how long updates take. 2016 is effectively Win10 1607 which has been greatly improved on. Usually Cisco etc take a while for new server OS' to be supported. Anything new I'd use 2019 as it's based in Windows 10 1809.

[mavhc]

It's pretty much the same as 2016, this is what's changed https://docs.microsoft.com/en-us/windows-server/get-started-19/whats-new-19

[Tefters]

2019 all the way hands down.

 

This business model of staying on old OS is going the way of the dodo and is simply old school IT thinking, I argue this with any software vendor that say 'we don't fully support 2019 as we haven't tested our software on it'. my usual response to that is you will support it and pull your finger out.

 

Failover clustering is sooooo much better in 2019 along with S2D.

Same goes for WAP proxy and modern authentication methods.

Dedup and Compressions also runs smoother on it too.

 

On the surface it might not seem much but under the hood the difference at high availability level are quite noticeable.

 

I feel half the battle/fun nowadays for IT is trying to stay up to date with new tech and be ready to recommend/test/implement things at the click of a finger as there are a lot of cost savings to be had nowadays but you do have to propose them right as they cost upfront to save in the long run.

[dmj]

It has to be 2019 because that's the only windows that supports kubernetes, which is what all the cool kids are doing.

[ukesilkeris6]

Hello,

I've recently begun my trip into IT. I've passed my A+ and I've read time and time again how important Powershell and Active Directory are in most businesses, and so that's where I'm aiming my focus when I'm feeling burnt out from CCENT study. I see many tutorials and documents about Windows Server 2012 and 2016, but not a lot yet on Server 2019. In addition I see many businesses don't focus on updating unless it would fix some problem or go in hand with a planned upgrade, and still use the older server operating systems (I believe I saw a recent post about upgrading from 08 while searching this subreddit). Would it be wise to start with the newest release for my virtual labs, or stick with the well-documented 16 or 12?

Thank you for your time.

 

That said, please experiment. I have a homelab that I have some backups of, but I will tend to blow up and rebuild on a 3-month basis. Change the hypervisor this time, convert some web servers from NGINX to IIS, etc. Things like that. It again, keeps me up to date on the core technologies, and not the specific tooling, since it forces me into a different mindset. I don't think about "ok, how do I make my website https://nox.tips/ https://xender.vip https://testmyspeed.onlaccessible from the internal network in Windows", I think "Oh, I need a PTR record. How do I add that?"

 

 

 

 

 

 

 

 

 

 

That said, please experiment. I have a homelab that I have some backups of, but I will tend to blow up and rebuild on a 3-month basis. Change the hypervisor this time, convert some web servers from NGINX to IIS, etc. Things like that. It again, keeps me up to date on the core technologies, and not the specific tooling, since it forces me into a different mindset. I don't think about "ok, how do I make my website accessible from the internal network in Windows", I think "Oh, I need a PTR record. How do I add that?"

 

 

 

 

 

 

 

 

[Davit2005]

Virtualisation has made homelabs much simpler and need not cost anything to get started. Back in the days I was doing a CCNA I had a 2m tall rack with a few desktop PCs Cisco switches and routers. Nowadays I can open Virtual Box or VMWare workstation and spin up a whole domain with a workstation and even connect it to a completely separate vlan on my home network if I want to do some isolated network labs or testing.

 

I would look Azure AD though if you can (Microsoft 365 etc) or other cloud services.

Edited August 18, 2020 by Davit2005

[mavhc]

It has to be 2019 because that's the only windows that supports kubernetes, which is what all the cool kids are doing.

 

But windows 10 has k8s, so just install wsl2 on all your desktop client machines and don't have a server, distribute the load

[dmj]

But windows 10 has k8s, so just install wsl2 on all your desktop client machines and don't have a server, distribute the load

 

oh that's interesting. Does windows desktop edition still have the license limit that prevents more than 20* external connections, forcing people to buy server edition? Or is that all a think of the past now?

 

*Edit: 20 connections as explained in the post below.

Edited August 20, 2020 by dmj

[Michael]

Windows 10 allows 20 concurrent connections.

[dmj]

ok so a cluster of 100 windows 10 clients would only be good as a server with 2000 connections, sounds like too few to be worth considering unless it was only serving a local area network for some basic services.

Might be an option for those who want a 'serverless' school without the overhead of a cloud infrastructure.

[mavhc]

What kind of connection? AFAIK the limits were about File Sharing, not TCP connections

 

"SP2 removes the limit of 10 half open outbound TCP connections. By default, SP2 has no limit on the number of half open outbound TCP connections."

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd335036(v=ws.10)?redirectedfrom=MSDN

Edited August 20, 2020 by mavhc

[dmj]

What kind of connection? AFAIK the limits were about File Sharing, not TCP connections

 

"SP2 removes the limit of 10 half open outbound TCP connections. By default, SP2 has no limit on the number of half open outbound TCP connections."

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd335036(v=ws.10)?redirectedfrom=MSDN

 

yes it looks like the restrictions are for specific services. I can't see any restrictions on using W10 as a kubernetes server cluster unless you want to offer the windows services above

https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/UseTerms_Retail_Windows_10_English.htm

 

"(iii) Device connections. You may allow up to 20 other devices to access the software installed on the licensed device for the purpose of using the following software features: file services, print services, Internet information services, and Internet connection sharing and telephony services on the licensed device. You may allow any number of devices to access the software on the licensed device to synchronize data between devices. This section does not mean, however, that you have the right to install the software, or use the primary function of the software (other than the features listed in this section), on any of these other devices."

[mavhc]

and in that "the software" means Windows features, not "whatever software is installed on your computer"

[Donna45]

How about Windows Server 2019 Standard Edition? Those of you building a smaller development environment might consider Windows Server 2019 Standard Edition instead.