Windows Server 2016 or 2019
-
As @bnrstnr says, you always purchase the latest both out of logic and out of requirement. No one should sell you an out of date license.
Which you deploy is the choice here. But I'd deploy 2019 unless there was a very specific reason not to for the software that will run on it.
-
Makes sense, thanks.
-
I haven't looked at 2019 yet, I do defiantly need to take a look, I cannot imagine too many differences from 2016, apart from probably more Azure integration?
-
Well 2019 did suffer from the data loss bug that 1809 did, but not many people use servers as desktop, except for RD servers... and now that I type that - that could be really bad !
-
@StuartJordan said in Windows Server 2016 or 2019:
I haven't looked at 2019 yet, I do defiantly need to take a look, I cannot imagine too many differences from 2016, apart from probably more Azure integration?
It's the next generation of product. 2016 was quite a leap over 2012 R2, for example.
-
I am anxious to see if they fixed updating.
-
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
We already know that they didn't.
-
@scottalanmiller said in Windows Server 2016 or 2019:
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
We already know that they didn't.
Dammit.
-
@BRRABill said in Windows Server 2016 or 2019:
@scottalanmiller said in Windows Server 2016 or 2019:
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
We already know that they didn't.
Dammit.
Server 2019 is Windows 10 1809.
-
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
I'm clearly not up to date, what was the issue with updating?
-
@NashBrydges said in Windows Server 2016 or 2019:
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
I'm clearly not up to date, what was the issue with updating?
Takes forever, and then like one hour more.
Just awful.
-
@BRRABill said in Windows Server 2016 or 2019:
@NashBrydges said in Windows Server 2016 or 2019:
@BRRABill said in Windows Server 2016 or 2019:
I am anxious to see if they fixed updating.
I'm clearly not up to date, what was the issue with updating?
Takes forever, and then like one hour more.
Just awful.
That sucks.
-
@NashBrydges said in Windows Server 2016 or 2019:
Setting up a new server and new VM for a client and need to buy a new Windows Server license. I would usually go to the most recent but wondering if anyone here has had any experience that would suggest sticking with a previous version instead? The VM will host an application that only runs on Windows so any mention of Linux isn't an option.
We've been running Windows Server 2019 since GA with nary an issue. There are a lot of under the hood improvements in 2019 so I suggest running with it.
-
@PhlipElder said in Windows Server 2016 or 2019:
@NashBrydges said in Windows Server 2016 or 2019:
Setting up a new server and new VM for a client and need to buy a new Windows Server license. I would usually go to the most recent but wondering if anyone here has had any experience that would suggest sticking with a previous version instead? The VM will host an application that only runs on Windows so any mention of Linux isn't an option.
We've been running Windows Server 2019 since GA with nary an issue. There are a lot of under the hood improvements in 2019 so I suggest running with it.
No different than any other large OS dev cycle. Look at 2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2, 2016, 2019. Roughly equal leaps between them all. It's almost never about features, it is 2-4 years of additional fixes, research, improvements, advances, clean up, etc. Features do play a part, but the lesser part.
