commit 8329185a7e5119d2a43a9606a8e3476fba8a3846 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 21 09:08:15 2016 -0700 tweak commit 99d0961d0148578322908ade9862f8b45d045e32 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 21 09:04:55 2016 -0700 updates for pushing live commit affc30449b7656ed0871e106620d16a0c2ce9c06 Merge: 0dd8a59 1dce84a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 21 08:59:51 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit 0dd8a5995efdc62da387f53a141b021ebaccbf91 Merge: 2aceee2 cb28398 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 21 07:21:00 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit 2aceee2831067b9b338484d86ac7cdf5a25b0e58 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 12:58:03 2016 -0700 waas-wsus.fig9 commit 7a826aa540b40e69b9da963f486aecc3fdb3816a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 12:36:31 2016 -0700 re-save each image commit b700ba2cf3b70e49537b3dd313575aba90a448b6 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 12:18:34 2016 -0700 testing new fix commit 30c3353173ffcfd40affed79ceb74ce029a6492a Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 12:10:17 2016 -0700 rename images commit a7995ca7999303215616fc6c197677bfc91589e9 Merge: 4b77449 e262949 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 11:54:28 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit 4b77449f242ceb1a3bbd87cc8003ffa119b6b75d Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 11:52:21 2016 -0700 renamed image file commit 741fab2cf53e1558227a62c5b3422e472acab88d Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 11:42:33 2016 -0700 troubleshooting images commit 521cb7e1f9701b9de29414c12e918992d8afb7d5 Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 11:30:59 2016 -0700 add art commit d65533c3ac4c0880fa2f75030c9ec1bbc49c8840 Merge: d9f0c9c bd846ca Author: jdeckerMS <jdecker@microsoft.com> Date: Wed Sep 14 11:08:43 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit d9f0c9cd1acfc0caf3c94e62d23cefc38aa06dac Merge: 60cc5a5 ffab5db Author: Elizabeth Ross <lizross@microsoft.com> Date: Wed Sep 14 07:35:13 2016 -0700 Merge pull request #182 from mtniehaus/patch-5 Update waas-update-windows-10.md commit 60cc5a58149ffbb219b34a87eae3d67b132b45f5 Merge: 7efbed7 cd4c88a Author: Elizabeth Ross <lizross@microsoft.com> Date: Wed Sep 14 07:35:02 2016 -0700 Merge pull request #183 from mtniehaus/patch-6 Update waas-overview.md commit cd4c88aeebc893f64bf6517c23edff9516c8b94c Author: Michael Niehaus <niehaus@live.com> Date: Tue Sep 13 22:57:17 2016 -0700 Update waas-overview.md Fixed up wording, changed to "two to three times per year", added "minimum of 18 months" text. commit ffab5dbdf6ba91ae7bf271f6958aed0c5a116070 Author: Michael Niehaus <niehaus@live.com> Date: Tue Sep 13 21:19:42 2016 -0700 Update waas-update-windows-10.md Fixing the text in the first paragraph to remove PR objections and to make it sound less like "cheery marketing" content. commit 7efbed7a79b212cb04dcae298e0ab1da977b7c20 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Sep 13 10:27:36 2016 -0700 8807924 commit 27926055ea9eeb082d731dcb91cd043cd996ccbf Merge: 49b877a d048580 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Sep 13 10:03:31 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit 49b877aa73957f9aba369e0bb3d69c408200be18 Merge: 91dc45b 7d1348e Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Sep 13 07:24:02 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit 91dc45bcd571532aeddceff775a401d727ec74e6 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 11:21:52 2016 -0700 change pixel size commit f2aa45f0f1806a4d6208c2d66a1b897dfd5a9c85 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 11:19:23 2016 -0700 2d tweak commit fac4a1c9d58b7c176732235db37a2c4fa37d269d Merge: d05c373 d075214 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 11:15:10 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit d05c373be521d0b1a4f908ff34729e069d3783ee Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 11:13:57 2016 -0700 tweak width commit 7c5de66b7a7b5454bf49fed42ae0cc94ddc4f51a Merge: b71bfe5 decfdee Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 11:12:16 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit b71bfe57fe1d55e23e303d92f572d8c07c19ebb8 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 07:49:05 2016 -0700 add link to Upgrade Analytics commit 04fb2371a6be88f014f75bff39b263098f721170 Merge: b152ae6 1995a49 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 07:36:48 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas commit b152ae60eceefd237984a8acbdc8a6a7bd3f2dae Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Sep 1 07:22:09 2016 -0700 add LTSB note commit ef94546e0e457ad86bbbfb77432be2dae5896de5 Merge: ba5399a 48b4b10 Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Aug 30 17:51:03 2016 -0700 Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas # Conflicts: # windows/manage/index.md commit ba5399abc0161d877650915e326e70bdeef7309f Author: jdeckerMS <jdecker@microsoft.com> Date: Tue Aug 30 17:28:17 2016 -0700 put waas content back in
8.4 KiB
title, description, ms.assetid, keywords, ms.prod, ms.mktglfcycl, ms.pagetype, ms.sitesec, author, redirect_url
title | description | ms.assetid | keywords | ms.prod | ms.mktglfcycl | ms.pagetype | ms.sitesec | author | redirect_url |
---|---|---|---|---|---|---|---|---|---|
Windows 10 servicing overview (Windows 10) | Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. | 6EF0792C-B587-497D-8489-4A7F5848D92A | deploy, upgrade, update, servicing | w10 | plan | servicing | library | jdeckerMS | https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview |
Windows 10 servicing overview
Applies to
- Windows 10
- Windows 10 Mobile
This topic provides an overview of the new servicing model for Windows 10. For more detailed information about this model, refer to Windows 10 servicing options.
The Windows servicing model
Traditionally, new versions of Windows have been released every few years. The deployment of those new versions within an organization would then become a project, either by leveraging a "wipe and load" process to deploy the new operating system version to existing computers, or by migrating to the new operating system version as part of the hardware replacement cycle. Either way, a significant amount of time and effort was required to complete these tasks.
With Windows 10, a new model is being adopted. This new model, referred to as "Windows as a service," requires organizations to rethink how they deploy and upgrade Windows. It is no longer a project that happens every few years, it is a continual process.
Windows as a service
Instead of new features being added only in new releases that happen every few years, the goal of Windows as a service is to continually provide new capabilities. New features are provided or updated two to three times per year, while maintaining a high level of hardware and application compatibility.
This new model uses simpler deployment methods, reducing the overall amount of effort required for Windows servicing. By combining these simpler methods (such as in-place upgrade) with new techniques to deploy upgrades in phases to existing devices, the effort that used to be performed as part of a traditional deployment project is spread across a broad period of time.
Windows 10 servicing branches
The concept of branching goes back many years, and represents how Windows has traditionally been written and serviced. Each release of Windows was from a particular branch of the Windows code, and updates would be made to that release for the lifecycle of that release. This concept still applies now with Windows 10, but is much more visible because it is incorporated directly into the servicing model.
Microsoft has implemented the following new servicing options in Windows 10:
Windows Insider Program: To see new features before they are released, to provide feedback on those new features, and to initially validate compatibility with existing applications and hardware, a small number of PCs can leverage the Windows Insider Program branch. These are typically dedicated lab machines used for IT testing, secondary PCs used by IT administrators, and other non-critical devices.
Current Branch (CB): For early adopters, IT teams, and other broader piloting groups, the Current Branch (CB) can be used to further validate application compatibility and newly-released features.
Current Branch for Business (CBB). For the majority of people in an organization, the Current Branch for Business (CBB) allows for a staged deployment of new features over a longer period of time.
Long-Term Servicing Branch (LTSB): For critical or specialized devices (for example, operation of factory floor machinery, point-of-sale systems, automated teller machines), the Long-Term Servicing Branch (LTSB) provides a version of Windows 10 Enterprise that receives no new features, while continuing to be supported with security and other updates for a long time. (Note that the Long-Term Servicing Branch is a separate Windows 10 Enterprise image, with many in-box apps, including Microsoft Edge, Cortana, and Windows Store, removed.)
These servicing options provide pragmatic solutions to keep more devices more current in enterprise environments than was previously possible. Most organizations will leverage all of these choices, with the mix determined by how individual PCs are used. Some examples are shown in the table below:
Industry | Windows Insider Program | Current Branch | Current Branch for Business | Long-Term Servicing Branch |
---|---|---|---|---|
Retail | <1% | 10% | 60% | 30% |
Manufacturing | <1% | 10% | 55% | 45% |
Pharmaceuticals | <1% | 10% | 50% | 40% |
Consulting | 10% | 50% | 35% | 5% |
Software developer | 30% | 60% | 5% | 5% |
Because every organization is different, the exact breakdown will vary even within a specific industry. The examples shown above should not be taken as specific recommendations. To determine the appropriate mix for a specific organization, profile how individual PCs are used within the organization, and target them with the appropriate branch. |
-
Retailers often have critical devices (for example, point-of-sale systems) in stores which results in higher percentages of PCs on the Long-Term Servicing Branch. But those used by information workers in support of the retail operations would leverage Current Branch for Business to receive new features.
-
Manufacturers typically have critical devices (for example, control systems) in factories; these are also good candidates for the Long-Term Servicing Branch. But as with retailers, information workers that support those factories are better suited to the Current Branch for Business.
-
Pharmaceutical firms often have regulatory requirements for PCs used for the development of their products, which are best satisfied by using Long-Term Servicing Branch. But not all PCs are subject to these regulatory requirements; those that are not can use the Current Branch for Business.
-
Consulting firms want their employees to have the latest functionality so they can be as productive as possible. They also want to develop expertise with new capabilities as soon as possible, hence more emphasis on Current Branch. But they also have information workers that provide services to the consultants; these workers can leverage Current Branch for Business.
-
Software developers typically work on software that will release in conjunction with a new Windows upgrade. To enable that, a significant percentage of developers may use the Windows Insider Program preview branch for initial efforts, which shifts to Current Branch as development progresses.
Note that there are few, if any, scenarios where an entire organization would use the Long-Term Servicing Branch for all PCs – or even for a majority of them.
With these new servicing options, Microsoft streamlined the Windows product engineering and release cycle so that Microsoft can deliver new features, experiences, and functionality more quickly than ever. Microsoft also created new ways to deliver and install feature upgrades and servicing updates that simplify deployments and on-going management, broaden the base of employees who can be kept current with the latest Windows capabilities and experiences, and lower total cost of ownership.
Windows 10 enables organizations to fulfill the desire to provide users with the latest features while balancing the need for manageability and cost control. To keep pace with technology, there are good business reasons to keep a significant portion of your enterprise's devices current with the latest release of Windows.
Related topics
Windows 10 release information
Windows 10 deployment considerations
Windows 10 compatibility
Windows 10 infrastructure requirements