The reaction on the net has been mixed thus far. Quite a few bloggers were quick to complain that Microsoft has lost it's way and everything was better in the olden days and why can't everything be like it was in 2001 and bla bla bla. I am not going to link articles in question, because those articles and user comments especially are so bizarrely and needlessly contrary they will literally make your brain hurt. I have looked at them, so you don't have to.
Yes, the terminology is changing. However, if you are aligned to the previous update model and are using Windows Update for Business, Windows Server Update Services or some other way to control how feature updates are being delivered to your end users, Windows servicing remains largely the same - as Michael Niehaus outlined here:
- Previously, new Windows 10 releases were initially considered "Current Branch" releases, to be used for piloting. After a period of about four months, Microsoft did declare the release as a "Current Branch for Business" release, ready for broad deployment.
- New Windows 10 releases in the Semi-Annual Channel are initially to be used for pilot deployments. After about four months, Microsoft will declare that the release is ready for broad deployment.
The big change here is that under the new model there is no 60-day "grace period", as that is being removed with implementation of this new servicing schedule.
These changes will go into effect right away.
