Kitz Forum
Computer Software => Windows 10 => Topic started by: g3uiss on October 30, 2019, 03:22:57 PM
-
Apologies if I’ve posted in the wrong section but as Server2016 is based on W10 I thought a good start.
Has anyone experience with Server 2016 and the time it takes to install Cumulative updates ?
I’ve just built one and it seems to take about 3 hrs to download / install. There are various posts on various boards but no solution.
Tony
-
Hi gu3ise
3 hours is too long unless it’s the first grab of updates
I think a lot depends upon the server hardware and some updates only install using PowerShell install
I like server 2012 better
Many thanks
John
-
Hi John
Yes it was the first update since the build. I had intended to put 2012R2 on this box, but thought it was time to move on to 2016, 2019 I believe isn’t that stable. On my VM,s 20 mins is about the max for a normal month. That includes a 2012 server. This is on the tin.
I think, as it’s not yet a production server I can wait and see what the November CU does. It’s no software on yet, so if it’s a long time I will rebuild under 2012R2.
Thanks
Tony
-
My experience with Server 2016 is that it is inherently slow to apply cumulative updates.
I initially thought VMs were broken they took so long to install, followed by a lifetime waiting for a reboot...
Many threads about it online. https://community.spiceworks.com/topic/2162701-cumulative-patches-for-server-2016-take-hours-to-install (https://community.spiceworks.com/topic/2162701-cumulative-patches-for-server-2016-take-hours-to-install) is a good one.
2012 R2 VMs running on same hypervisors apply the same updates in minutes, 2016 though...hours.
Better off to skip to 2019 should your applications support it, as the bug is not present due to MS re-writing the update engine.
-
Thanks that’s what I expected and I had seen some threads but not that one. Thanks for the link. I’m going to try 2019 I don’t see any applications that would have an issue there.
Tony
-
@d2d4j. John I’m trying to sort a HPE Microserver G10 solely as a additional DC. This HPE box isn’t rated for Server 2919 only #2012R2 and 2016. Given its really just a build update would you expect it to work with 2019, or should I stop wasting time and use 2012R2.
Client is trying to reduce local hardware and the plan would be to sunset the existing now old DC’s which are on a older HP box’s using Server2008R2 and use the Microserver and an Azure DC.
The progress of theses issues is surpassing my age related learning :(
-
Hi tony
To be honest, I’d go with 2012R2 and review in year 3 (as it nears EOL)
Cost wise verse ROI makes sense and you have a known working solution
Others may not agree but cost/time constraints dictate a medium resolution
Also, as server is not rated for 2019, you could be in for a hiding to nothing and lose a client if it fails
Just be honest with client and give them an option for server 2019 @ a cost with suitable hardware verse current option @ server 2012r2
I think I know which they’ll go with unless budgets not an issue - when has that ever happened!
Many thanks
John
-
John
That’s the view I came to I think. It’s interesting that very few main line servers ( HPE or Dell) are 2019 rated. I guess either the vendors haven’t tested or they don’t view it stable. At least least 2012R2 is a know and in basic terms a “normal” piece of software ! And of course tried and tested.
3 years + to EOL now they extended it in the big picture is quite a while !
Tony