Come on! Grandma tested it. Look Facebook loads just fine on her Acer. Go release server 2016 as we had 2 million testers and no telemetry of a single NIC teaming failure!
I know MS is bashed here often but server 2008 r2 thru 2012 r2 are actually Ok and .... RELIABLE. Yes you heard that. But without a QA department I do not know what to do when Server 2012 R2 goes EOL?
I hate being those old whippersnappers afraid of change that scatter the IT community, but with more Oracle like per core licensing of 2016 and this shitware with 10 I am afraid to move forward. If Windows 8.1 had a start menu for my users I wouldn't mind upgrading 7 to that when EOL hits soon.
But I will be fired if I deploy 10 or server in it's current state. I cannot have only 3 months to stop a feature update that breaks something??!! Worse cumulative security updates means I can't ever run legacy software and stay secure?? If one bad update from 2014 breaks a website ActiveX control I cannot have a cumulative update as it will break that control etc.
Time to think long and hard about my career as I will be fired anyway when I can't meet my 97.97% uptime required by my annual performance evaluation. Thanks Microsoft