Tuesday, April 25, 2017

Microsoft addresses IT professionals stability concerns with new update model for Windows 10

Microsoft simplified the update process with the release of Windows 10 by moving to cumulative updates once a month. Most enterprises deploy the cumulative updates released by Microsoft when they are released on the Update Tuesday (second Tuesday of every month). Based on the feedback from enterprise customers, Microsoft is today announcing changes to the updates they are releasing for Windows 10, version 1703, which is popularly referred to as Windows 10 Creators Update.

Based on the new changes, Microsoft will now routinely offer one (or sometimes more than one) additional update each month. These additional cumulative updates will contain only new non-security updates, they will be labelled as "Updates" in WSUS and Configuration Manager. Microsoft may occasionally identify non-security fixes that address more critical issues that could be affecting organizations. In those cases, a cumulative update would be labelled as "Critical Updates" in WSUS and Configuration Manager.

Organizations now have the following flexibility to choose what do to with these new non-security cumulative updates:

  • Deploy each of them just like the updates on "Update Tuesday." This enables the organization's PCs to get the latest fixes more quickly.
  • Deploy each of them to a subset of devices. This enables the organization to ensure that these new non-security fixes work well, prior to those same fixes being included in the next "Update Tuesday" cumulative update which will be deployed throughout the organization.
  • Selectively deploy them, based on whether they address specific issues affecting the organization, ahead of the next "Update Tuesday" cumulative update.
  • Don't deploy them at all. There is no harm in doing this since the same fixes will be included in the "Update Tuesday" cumulative update (along with all the new security fixes).

Learn more about it here.



from MSPoweruser http://ift.tt/2osKDVZ
via IFTTT

No comments:

Post a Comment