mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Squashed commit of the following:
commit 56ff8d363e5ea3910234748513a21f2e5775a806
Author: jdeckerMS <jdecker@microsoft.com>
Date: Fri Dec 2 10:09:43 2016 -0800
change to Dec
commit 6a62b1eea5b4398cb06cda27d294f7d31bf52395
Merge: 2dbc37f db6b38d
Author: jdeckerMS <jdecker@microsoft.com>
Date: Fri Dec 2 10:07:41 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit 2dbc37f6e06f7a026232028323b59aaf8c371c89
Merge: a58d803 00309f9
Author: jdeckerMS <jdecker@microsoft.com>
Date: Wed Nov 30 13:03:55 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit a58d80301355b4fa13e6d68d94c03d87c5d73a5d
Merge: b8bef24 944e6ba
Author: jdeckerMS <jdecker@microsoft.com>
Date: Tue Nov 29 07:09:23 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit b8bef24f96185da3f3402bb5afa8d40bcf8e7c92
Author: jdeckerMS <jdecker@microsoft.com>
Date: Mon Nov 28 10:25:11 2016 -0800
fix link
commit c75d6156023d9197a63d1e4dce3d26be40765bf8
Merge: 2429802 22fc1f5
Author: jdeckerMS <jdecker@microsoft.com>
Date: Mon Nov 28 10:24:20 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit 2429802eebcfa883c214bb53a2b0e6b8dde7003e
Author: jdeckerMS <jdecker@microsoft.com>
Date: Mon Nov 28 10:16:06 2016 -0800
format
commit 8fbbfa0ba9603deb7b39a4ea37da531bc990010e
Author: jdeckerMS <jdecker@microsoft.com>
Date: Mon Nov 28 08:58:44 2016 -0800
add new topic
commit b7b228764dd7756f6fcecf9e297a129c7679a158
Merge: 16210de bec858b
Author: jdeckerMS <jdecker@microsoft.com>
Date: Mon Nov 28 08:42:37 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit 16210dec9bd564f32ecb911d7405539e04c2a1fe
Merge: 862c7d4 a2b26d9
Author: jdeckerMS <jdecker@microsoft.com>
Date: Tue Nov 22 09:03:58 2016 -0800
Merge remote-tracking branch 'refs/remotes/origin/master' into jdwaas2
commit 862c7d497f325a52fa769902436e94c8cf660236
Author: jdeckerMS <jdecker@microsoft.com>
Date: Tue Nov 22 08:51:02 2016 -0800
tweak
This commit is contained in:
jdeckerMS
parent
db6b38de7f
commit
07236f6b93
@ -2,6 +2,7 @@
|
||||
## [Administrative Tools in Windows 10](administrative-tools-in-windows-10.md)
|
||||
## [Cortana integration in your business or enterprise](manage-cortana-in-enterprise.md)
|
||||
## [Update Windows 10 in the enterprise](waas-update-windows-10.md)
|
||||
### [Quick guide to Windows as a service](waas-quick-start.md)
|
||||
### [Overview of Windows as a service](waas-overview.md)
|
||||
### [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
|
||||
### [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
|
||||
|
||||
@ -12,6 +12,12 @@ author: jdeckerMS
|
||||
|
||||
This topic lists new and updated topics in the [Manage and update Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
|
||||
|
||||
## December 2016
|
||||
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Quick guide to Windows as a service](waas-quick-start.md) | New |
|
||||
|
||||
## November 2016
|
||||
|
||||
| New or changed topic | Description |
|
||||
|
||||
76
windows/manage/waas-quick-start.md
Normal file
76
windows/manage/waas-quick-start.md
Normal file
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Quick guide to Windows as a service (Windows 10)
|
||||
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Quick guide to Windows as a service
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Windows 10 IoT Mobile
|
||||
|
||||
Windows as a service is a new concept, introduced with the release of Windows 10. While [an extensive set of documentation](waas-update-windows-10.md) is available explaining all the specifics and nuances, here is a quick guide to the most important concepts.
|
||||
|
||||
## Definitions
|
||||
|
||||
Some new terms have been introduced as part of Windows as a service, so you should know what these terms mean.
|
||||
- **Feature updates** will be released two to three times per year. As the name suggests, these will add new features to Windows 10, delivered in bite-sized chunks compared to the previous practice of Windows releases every 3-5 years.
|
||||
- **Quality updates** are released monthly, delivering both security and non-security fixes. These are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update.
|
||||
- **Insider Preview** builds are made available during the development of the features that will be shipped in the next feature update, enabling organizations to validate new features as well as compatibility with existing apps and infrastructure, providing feedback to Microsoft on any issues encountered.
|
||||
- **Servicing branches** allow organizations to choose when to deploy new features. Current Branch (CB) deploys the fastest, soon after a feature update is released. Current Branch for Business (CBB) defers the installation of the same feature update by about four months, until that feature update is considered ready for broad deployment. Long Term Servicing Branch (LTSB) is different, used only for specialized devices (which typically don’t run Office) such as those that control medical equipment or ATM machines that need to be kept stable and secure.
|
||||
- **Deployment rings** are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization.
|
||||
|
||||
See [Overview of Windows as a service](waas-overview.md) for more information.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
New feature update releases are initially considered **Current Branch (CB) releases**; organizations will use these for pilot deployments to ensure compatibility with existing apps and infrastructure. After about four months, the feature update will be declared as **Current Branch for Business (CBB)**, indicating that it is ready for broad deployment.
|
||||
|
||||
Each Windows 10 feature update (which initially begins as CB and then is declared as CBB) will be serviced with quality updates for a minimum of 18 months after it is released. The total length of time can be longer, as there will be two CBB releases serviced at all times. There will be a minimum of 60 days advanced notice (a grace period) after a CBB declaration occurs before an older feature update is no longer serviced.
|
||||
|
||||
Windows 10 Enterprise LTSB is a separate **Long Term Servicing Branch (LTSB)** version. Each release is supported for a total of 10 years (five years standard support, five years extended support). New releases are expected about every three years.
|
||||
|
||||
See [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) for more information.
|
||||
|
||||
## Staying up to date
|
||||
|
||||
The process for keeping Windows 10 up to date involves deploying a feature update, at an appropriate time after its release. A variety of tools management and patching tools such as Windows Update, Windows Update for Business, Windows Server Update Services, System Center Configuration Manager, and third-party products) can be used to help with this process. [Windows Upgrade Analytics](https://www.microsoft.com/en-us/WindowsForBusiness/upgrade-analytics), a free tool to streamline Windows upgrade projects, is another important tool to help.
|
||||
|
||||
Because app compatibility, both for desktop apps and web apps, is outstanding with Windows 10, extensive advanced testing isn’t required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps and CBB has been declared, broad deployment can begin.
|
||||
|
||||
This process repeats with each new feature update, two to three times per year. These are small deployment projects, compared to the big projects that were necessary with the old three-to-five-year Windows release cycles.
|
||||
|
||||
Additional technologies such as BranchCache and Delivery Optimization, both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||
|
||||
See [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) and [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) for more information.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Update Windows 10 in the enterprise](waas-update-windows-10.md)
|
||||
- [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md)
|
||||
- [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md)
|
||||
- [Configure BranchCache for Windows 10 updates](waas-branchcache.md)
|
||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
||||
- [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md)
|
||||
- [Walkthrough: use Intune to configure Windows Update for Business](waas-wufb-intune.md)
|
||||
- [Manage device restarts after updates](waas-restart.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -127,7 +127,7 @@ During the life of a device, it may be necessary or desirable to switch between
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Not directly possible, because Windows Insider Program machines are automatically upgraded to the Current Branch release at the end of the development cycle.</td>
|
||||
<td align="left">Not directly possible, because Windows Insider Program devices are automatically upgraded to the Current Branch release at the end of the development cycle.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
@ -153,7 +153,7 @@ During the life of a device, it may be necessary or desirable to switch between
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Disable the <strong>Defer upgrade</strong> setting, or move the PC to a target group or flight that will receive the latest Current Branch release.</td>
|
||||
<td align="left">Disable the <strong>Defer upgrade</strong> setting, or move the device to a target group or flight that will receive the latest Current Branch release.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
|
||||
@ -27,6 +27,7 @@ Windows as a service provides a new way to think about building, deploying, and
|
||||
|
||||
| Topic | Description|
|
||||
| --- | --- |
|
||||
| [Quick guide to Windows as a service](waas-quick-start.md) | Provides a brief summary of the key points for the new servicing model for Windows 10. |
|
||||
| [Overview of Windows as a service](waas-overview.md) | Explains the differences in building, deploying, and servicing Windows 10; introduces feature updates, quality updates, and the different servicing branches; compares servicing tools. |
|
||||
| [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) | Explains the decisions you need to make in your servicing strategy. |
|
||||
| [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) | Explains how to make use of servicing branches and update deferrals to manage Windows 10 updates. |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user