Moving up to Server 2016

[Moltuae]

I've held-off doing Server 2016 installations so far but I'm thinking the OS is probably mature enough to start using now. Or, perhaps more importantly, Server 2012 is getting a little too long in the tooth to continue using it on new installations.

Any thoughts/experiences on this point?


Also, has anyone successfully converted Server 2016 from evaluation version to Volume or OEM (as per the info below)? I'm planning to take it for a test drive by installing and configuring the evaluation version on a new server. It would be good not to have to re-install if everything works as planned ...


https://docs.microsoft.com/en-us/windows-server/get-started/supported-upgrade-paths

Converting a current evaluation version to a current retail version
You can convert the evaluation version of Windows Server 2016 Standard to either Windows Server 2016 Standard (retail) or Datacenter (retail). Similarly, you can convert the evaluation version of Windows Server 2016 Datacenter to the retail version.

At any time after installing Windows Server 2016, you can freely convert it between a retail version, a volume-licensed version, or an OEM version. The edition remains the same during this conversion. If you are starting with an evaluation version, convert it to the retail version first, and then you can inter-convert as described here.

To do this, from an elevated command prompt, run: slmgr /ipk <key>

Where <key> is the appropriate volume-license, retail, or OEM product key.

 

[mdownes]

I converted from eval version to volume and it was exactly as easy as it should be.

 

[RCHavok797]

I certainly wouldn't be installing Server 2012 any longer but 2012R2 is still my go to. I have a few installs of Server 2016 but mostly to test new features such as ADFS 2016.

 

[Sky-Knight]

I've just started using it internally mid May, thus far I'm not seeing a whole lot of difference between 2016 and 2012R2. Sure new features, but the platform has done exactly what I've asked it every time.

The additional OS support in Hyper-V is nice.

 

[NYJimbo]

I do Plesk hosting w 2012R2 and for some reason our provider (Softlayer) keeps pushing us to upgrade to 2016. I want to put it off for another year because there are quirks between Plesk and 2016, but they keep pushing us. They never did that with 2008 or 2012.

 

[Moltuae]

On the whole, I'm finding Server 2016 very similar to 2012 R2.

That is of course with the exception of the Windows 10 features, like the usual Fisher-Price Start menu and the forced updates.

I mean, seriously Microsoft!? Forced updates and reboots on a feckin' server!?

I wouldn't mind the forced updates so much if it were possible to indefinitely postpone the reboots, or at least postpone them for a few weeks. A 12 hour 'active-hours' window is simply not enough. The server I'm working on is destined to be an SQL server, with client connections that must be closed before rebooting to prevent data corruption.

For now, I'm implementing this tweak to prevent automatic reboots:
https://docs.ukfast.co.uk/operatingsystems/windows/server2016/windowsupdate.html

 

[PcTek9]

Let's tie the train wheels back on with fishing line, and while we are at it add forced server unmanned reboots. Don't worry, everything will be fine.

 

[Sergey]

I have two servers running 2016 and one of them crashes at almost always the same time, shortly after 11pm... Happens almost every week quite randomly. Same hardware ran 2012 R2 without any issues.

 

[cyabro]

One thing to note with Server 2016 is that Windows Defender AV does not automatically disable if you put your own AV software on.
Not sure why Microsoft thought that was a good idea?!

 

[G8racingfool]

On the whole, I'm finding Server 2016 very similar to 2012 R2.

That is of course with the exception of the Windows 10 features, like the usual Fisher-Price Start menu and the forced updates.

I mean, seriously Microsoft!? Forced updates and reboots on a feckin' server!?

I wouldn't mind the forced updates so much if it were possible to indefinitely postpone the reboots, or at least postpone them for a few weeks. A 12 hour 'active-hours' window is simply not enough. The server I'm working on is destined to be an SQL server, with client connections that must be closed before rebooting to prevent data corruption.

For now, I'm implementing this tweak to prevent automatic reboots:
https://docs.ukfast.co.uk/operatingsystems/windows/server2016/windowsupdate.html

I'm still testing to see if it works (has so far!) but there's a group policy:

Local Computer Policy > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates

Setting that to "disabled" prevents the system from even checking for updates, allowing you to do so manually. There's also a bunch of other settings you can use by setting it to "enabled".