Windows 2016 auto install updates and auto reboot - bad idea, pretty much guarantees some dataloss

As for automatic updates, I have seen as recent as a few weeks ago, where Microsoft's updates in conjunction with an antivirus application rendered a group of Windows 10 machines unusable

What was the antivirus?  I have not seen this myself or at any client. We use Symantec Endpoint at all clients.

Sadly, I see this all the time in several sites where users leave their files open, may not save them, and if a file server is rebooted oopsy, just lost all their work

We insist users log off end of day. That prevents this kind of problem. In this environment, a user leaves files open once and then knows better.

All our servers at this point are Server 2012 R2 and we control the update sequence. We have not yet tested Server 2016.

Phew, well. First, I have to mention that your post comes across more like a rant than a real question, so with that in mind, it seems your mind is already made up.   But for anybody who cares, there is a lot to unpack here....

"Is it true that there isn't a supported means of disabling automatic installation of updates, or automatic reboots on Wink216?  "

The options are fundamentally the same as they were in 2012/win8, 2012 R2/win 8.1, and on.  Microsoft made the drastic change back then and has been iterative since.  If you want general controls, you have windows update for business. If you want granular control, you have WSUS (or SCCM or 3rd party.)   So this *isn't* new, and with you mentioning sticking with 2012 (not 2008 R2), you have similar challenges.

"I have seen as recent as a few weeks ago, where Microsofts updates in conjunction with an antivirus application rendered a group of Windows 10 machines unusable."

....and that can happen with win95,98,2000,XP,7,8....if vendors use bad code, patches can break things.  Using pilot rings has been a best practice for a LLLLLOOOOONNNNNGGGGG time, and win10/2016 doesn't change this.  WUfB still gives you loose control to create rings too.

"Secondly - auto-reboots? Auto-reboots=guaranteed dataloss.  Sadly, I see this all the time in several sites where users leave their files open, may not save them, and if a file server is rebooted oopsy, just lost all their work."

That's nonsense.  IF the file is unsaved then it is on the client, not on the file server and the file server can reboot without any issue. The *only* time this is true is if this is a remote desktop session. In which case, best practices have again had automatic logouts after idle sessions hit a time limit.  And how do "automatic" patches change this?  Even if you patch manually, do you want your reboot held hostage because one user didn't log out of the terminal server?!?  Would you even know if they had unsaved work??? If you reboot manually...same data loss risk.  There is a point where that is on the user. You declare maintenance windows and stick to them.  Done. 2016 DOES NOT CHANGE THIS!!

"That being said, doing a new install at a site of half a doz servers, I think I will keep it to 2012.    Unless of course there is a way to do this in a controlled fashion."

As mentioned above, Microsoft's patching strategy changed with 2012.  And there are still controlled options. So sticking with 2012 gains you nothing.  Nothing.

"With server updates, on Vms, actually not a bad idea to do a snapshot first."

Before 2016, snapshots (checkpoints) were NOT supported in production. Not even with VMWare (VMWare may support it, but the underlying OS and applications still don't.)  Even *with* 2016, production checkpoints should be used sparingly. And are *NOT*  *NOT*  *NOT* a replacement for backups.  *THAT'S* a mistake that is often seen at many sites, enough so that Microsoft Premiere Support has written multiple blog posts on the subject.

"With Microsoft deciding when they do things, good luck in having the luxury of recovering from their often undertested updates."

Thus the random rant I mentioned.  Not a good look when asking for help....

Gents

Thanks for your response.  Sorry if it came across like a rant.  In the real world, it is difficult to explain to even high level management, and yes of course they should not be leaving their files open, but it happens quite often  Some I see would need to change their dynamics of working.  I agree that files should be saved frequently.  As for snapshots not being supported, that is interesting, I will have to look into that further. I do not recall them not being supported.  I agree snapshots are not a replacement for backups, however, perhaps they are useful for a restore point in time. I haven't had to use one in Prod in years, but it worked when needed.   It was a question as to whether you can set it for check for updates, or check and download, and install when you wish, as well as reboot in a controlled manner.   Actually you are able to do that within Win2k12,  so I guess I have to dig further to see how it is done in Win2k16.

I incorrectly gathered the info from a prior post, which I thought stated you cannot disable updates/or auto reboots.
Thanks again

it is difficult to explain to even high level management.....   <-- Work on that angle. I explain to all level of staff what may happen if they leave files open overnight. They usually accept this.

Hey Jeremy

Excellent - thank you!!  I have forgotten about sconfig!  I did install the gui on these servers. Can do a # of things from sconfig, good stuff, thanks so much!! Enjoy your weekend! Nice if MS had the same feature for windows 10

Glad to help. :)

Jeremy

Thanks again! Exactly what I needed!
Be well