From 190429710f113d52351c6b4f572d21ae1282d54d Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 21 May 2018 09:41:25 -0700 Subject: [PATCH 1/9] added explanatory material about servicing stack updates --- windows/deployment/TOC.md | 1 + .../update/servicing-stack-updates.md | 41 +++++++++++++++++++ windows/deployment/update/waas-quick-start.md | 4 +- 3 files changed, 44 insertions(+), 2 deletions(-) create mode 100644 windows/deployment/update/servicing-stack-updates.md diff --git a/windows/deployment/TOC.md b/windows/deployment/TOC.md index 322fa570ca..8557a91510 100644 --- a/windows/deployment/TOC.md +++ b/windows/deployment/TOC.md @@ -213,6 +213,7 @@ ## [Update Windows 10](update/index.md) ### [Quick guide to Windows as a service](update/waas-quick-start.md) +#### [Servicing stack updates](update/servicing-stack-updates.md) ### [Overview of Windows as a service](update/waas-overview.md) ### [Prepare servicing strategy for Windows 10 updates](update/waas-servicing-strategy-windows-10-updates.md) ### [Build deployment rings for Windows 10 updates](update/waas-deployment-rings-windows-10-updates.md) diff --git a/windows/deployment/update/servicing-stack-updates.md b/windows/deployment/update/servicing-stack-updates.md new file mode 100644 index 0000000000..add2afba22 --- /dev/null +++ b/windows/deployment/update/servicing-stack-updates.md @@ -0,0 +1,41 @@ +--- +title: Servicing stack updates (Windows 10) +description: Servicing stack updates improve the code that installs the other updates. +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +author: Jaimeo +ms.localizationpriority: high +ms.author: jaimeo +ms.date:05/27/2018 +--- + +# Servicing stack updates + + +**Applies to** + +- Windows 10 +- Windows 10 Mobile +- Windows 10 IoT Mobile + +## What is a servicing stack update? +The "servicing stack" is the code that installs other operating system updates. Additionally, it contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month. + +## Why should servicing stack updates be installed and kept up to date? + +Having the latest servicing stack update is a prerequisite to reliably installing the latest quality updates and feature updates. + +## When are they released? + +Currently, the servicing stack update releases are aligned with the monthly quality update release date, though sometimes they are released on a separate date if required. + +## Is there any special guidance? + +Typically, the improvements are reliability, security, and performance improvements that do not require any specific special guidance. If there is any significant impact is will be present in the release notes. + +## Installation notes + +• Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system. +• Installing servicing stack update does not require restarting the device, so installation should not be disruptive. +• Servicing stack update releases are specific to the operating system version (build number), much like quality updates. diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index 8ea214bbb5..28a55e6865 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date: 02/09/2018 +ms.date:05/27/2018 --- # Quick guide to Windows as a service @@ -25,7 +25,7 @@ Windows as a service is a new concept, introduced with the release of Windows 10 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 twice per year, around March and September. 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. +- **Quality updates** are released monthly, delivering both security and non-security fixes. Typically released the second Tuesday of each month (though they can be released at any time), these include security updates, critical updates, servicing stack updates, and driver updates. The "servicing stack" is the code that installs other updates, so they are especially important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md) Quality updates 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 channels** allow organizations to choose when to deploy new features. - The **Semi-Annual Channel** receives feature updates twice per year. From 34ebdceddb54ff1de20f116085c39848db2afd66 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Tue, 22 May 2018 13:14:03 -0700 Subject: [PATCH 2/9] safety commit --- windows/deployment/update/servicing-stack-updates.md | 2 +- windows/deployment/update/waas-quick-start.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/servicing-stack-updates.md b/windows/deployment/update/servicing-stack-updates.md index add2afba22..ccd64c9f27 100644 --- a/windows/deployment/update/servicing-stack-updates.md +++ b/windows/deployment/update/servicing-stack-updates.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date:05/27/2018 +ms.date: 05/27/2018 --- # Servicing stack updates diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index 28a55e6865..cc6fc2c319 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date:05/27/2018 +ms.date: 05/27/2018 --- # Quick guide to Windows as a service From e1e751c9cd4837b4b2728889311882a19c766d2d Mon Sep 17 00:00:00 2001 From: D76C6399A0F334216B3A58BE07C3C3137D5E14542BC13CA38EB0800D9FFC1FE6 Date: Thu, 24 May 2018 11:40:58 -0400 Subject: [PATCH 3/9] Fix heading levels Fix heading level for Microsoft.Windows.Inventory.Core.InventoryApplicationDriverStartSync in 1709 documentation Fix heading level for Common data extensions heading in 1709 documentation to match other documentation --- ...basic-level-windows-diagnostic-events-and-fields-1709.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709.md b/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709.md index 06874ee41a..32579a1856 100644 --- a/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709.md +++ b/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709.md @@ -36,7 +36,7 @@ You can learn more about Windows functional and diagnostic data through these ar -# Common data extensions +## Common data extensions ### Common Data Extensions.App @@ -346,7 +346,7 @@ The following fields are available: - **Programids** The unique program identifier the driver is associated with. -## Microsoft.Windows.Inventory.Core.InventoryApplicationDriverStartSync +### Microsoft.Windows.Inventory.Core.InventoryApplicationDriverStartSync This event indicates that a new set of InventoryApplicationDriverStartAdd events will be sent. @@ -4738,4 +4738,4 @@ The following fields are available: - **scheduledRebootTime** Time of the scheduled reboot - **updateId** ID of the update that is getting installed with this reboot - **wuDeviceid** Unique device ID used by Windows Update -- **scheduledRebootTimeInUTC** Time of the scheduled reboot in Coordinated Universal Time \ No newline at end of file +- **scheduledRebootTimeInUTC** Time of the scheduled reboot in Coordinated Universal Time From 3c5d4f201ce84ff6f7c1cbdf5e33b8df602fe55e Mon Sep 17 00:00:00 2001 From: jaimeo Date: Fri, 25 May 2018 10:05:49 -0700 Subject: [PATCH 4/9] fixing stuff per Amitabh --- windows/deployment/update/servicing-stack-updates.md | 6 ++---- windows/deployment/update/waas-quick-start.md | 4 ++-- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/windows/deployment/update/servicing-stack-updates.md b/windows/deployment/update/servicing-stack-updates.md index ccd64c9f27..f356277c28 100644 --- a/windows/deployment/update/servicing-stack-updates.md +++ b/windows/deployment/update/servicing-stack-updates.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date: 05/27/2018 +ms.date: 05/25/2018 --- # Servicing stack updates @@ -16,8 +16,6 @@ ms.date: 05/27/2018 **Applies to** - Windows 10 -- Windows 10 Mobile -- Windows 10 IoT Mobile ## What is a servicing stack update? The "servicing stack" is the code that installs other operating system updates. Additionally, it contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month. @@ -32,7 +30,7 @@ Currently, the servicing stack update releases are aligned with the monthly qual ## Is there any special guidance? -Typically, the improvements are reliability, security, and performance improvements that do not require any specific special guidance. If there is any significant impact is will be present in the release notes. +Typically, the improvements are reliability, security, and performance improvements that do not require any specific special guidance. If there is any significant impact, it will be present in the release notes. ## Installation notes diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index cc6fc2c319..94c2bf0cba 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date: 05/27/2018 +ms.date: 05/25/2018 --- # Quick guide to Windows as a service @@ -25,7 +25,7 @@ Windows as a service is a new concept, introduced with the release of Windows 10 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 twice per year, around March and September. 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. Typically released the second Tuesday of each month (though they can be released at any time), these include security updates, critical updates, servicing stack updates, and driver updates. The "servicing stack" is the code that installs other updates, so they are especially important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md) Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. +- **Quality updates** are released monthly, delivering both security and non-security fixes. Typically released the second Tuesday of each month (though they can be released at any time), these include security updates, critical updates, servicing stack updates, and driver updates. Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. The "servicing stack" is the code that installs other updates, so they are important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md). - **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 channels** allow organizations to choose when to deploy new features. - The **Semi-Annual Channel** receives feature updates twice per year. From 6429e0cbc875c815af09e26ea4854fd6c9133d2e Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Tue, 29 May 2018 19:19:57 +0000 Subject: [PATCH 5/9] Merged PR 8589: Fix for bug 17310408 Added an MDM policy to let Windows apps access trusted devices --- ...system-components-to-microsoft-services.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index d80ca22032..7a736f508b 100644 --- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -1403,12 +1403,13 @@ To turn off **Let apps automatically share and sync info with wireless devices t -or- -- Apply the Privacy/LetAppsSyncWithDevices MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappssyncwithdevices), where: +- Apply the Privacy/LetAppsSyncWithDevices MDM policy from the [Policy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#privacy-letappssyncwithdevices), where: - - **0**. User in control - - **1**. Force allow - - **2**. Force deny + - **0**. User in control + - **1**. Force allow + - **2**. Force deny + -or- - Create a REG\_DWORD registry setting named **LetAppsSyncWithDevices** in **HKEY\_LOCAL\_MACHINE\\Policies\\Microsoft\\Windows\\AppPrivacy** with a value of 2 (two). @@ -1423,6 +1424,16 @@ To turn off **Let your apps use your trusted devices (hardware you've already co - Set the **Select a setting** box to **Force Deny**. + -or- + +- Apply the **Privacy/LetAppsAccessTrustedDevices** MDM policy from the [Policy CSP](/windows/client-management/mdm/policy-csp-privacy.md#privacy-letappsaccesstrusteddevices +), where: + + - **0**. User in control + - **1**. Force allow + - **2**. Force deny + + ### 17.16 Feedback & diagnostics In the **Feedback & Diagnostics** area, you can choose how often you're asked for feedback and how much diagnostic and usage information is sent to Microsoft. From bb028147d6514cc9d7b4e76e5f72f29bf0445ef7 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 29 May 2018 19:46:22 +0000 Subject: [PATCH 6/9] Merged PR 8591: Removed Win8.0 as valid upgrade source, added support statement, fixed msdate Removed Win8.0 as valid upgrade source, added support statement, fixed msdate --- .../deployment/deploy-enterprise-licenses.md | 2 +- .../upgrade/windows-10-upgrade-paths.md | 84 +------------------ 2 files changed, 4 insertions(+), 82 deletions(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 9e9b4bdb87..dd0540a540 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -7,7 +7,7 @@ ms.mktglfcycl: deploy localizationpriority: high ms.sitesec: library ms.pagetype: mdt -ms.date: 10/18/2017 +ms.date: 05/25/2018 author: greg-lindsay --- diff --git a/windows/deployment/upgrade/windows-10-upgrade-paths.md b/windows/deployment/upgrade/windows-10-upgrade-paths.md index e6f428797e..9b8d7a8ea6 100644 --- a/windows/deployment/upgrade/windows-10-upgrade-paths.md +++ b/windows/deployment/upgrade/windows-10-upgrade-paths.md @@ -7,7 +7,7 @@ ms.sitesec: library ms.localizationpriority: high ms.pagetype: mobile author: greg-lindsay -ms.date: 05/18/2018 +ms.date: 05/29/2018 --- # Windows 10 upgrade paths @@ -28,6 +28,8 @@ This topic provides a summary of available upgrade paths to Windows 10. You can >**Windows N/KN**: Windows "N" and "KN" SKUs follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process. +>**Windows 8.0**: You cannot upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the [Windows 8.1 update](https://support.microsoft.com/help/15356/windows-8-install-update-kb-2919355). + ✔ = Full upgrade is supported including personal data, settings, and applications.
D = Edition downgrade; personal data is maintained, applications and settings are removed. @@ -114,86 +116,6 @@ D = Edition downgrade; personal data is maintained, applications and settings ar - - Windows 8 - - - (Core) - ✔ - ✔ - ✔ - ✔ - - - - - - - Professional - D - ✔ - ✔ - ✔ - ✔ - - - - - - Professional WMC - D - ✔ - ✔ - ✔ - ✔ - - - - - - Enterprise - - - - ✔ - ✔ - - - - - - Embedded Industry - - - - - ✔ - - - - - - Windows RT - - - - - - - - - - - Windows Phone 8 - - - - - - - - - Windows 8.1 From 12144eff09a9cd796f0f03506d9c77055b35c462 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 29 May 2018 13:37:21 -0700 Subject: [PATCH 7/9] remove au from proxy list --- ...y-internet-windows-defender-advanced-threat-protection.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md index 8de9ab0c90..02ecae6123 100644 --- a/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md @@ -94,12 +94,9 @@ Common URLs for all locations | ```*.blob.core.windows.net```
```crl.microso US | ```us.vortex-win.data.microsoft.com```
```us-v20.events.data.microsoft.com```
```winatp-gw-cus.microsoft.com```
```winatp-gw-eus.microsoft.com``` Europe | ```eu.vortex-win.data.microsoft.com```
```eu-v20.events.data.microsoft.com```
```winatp-gw-neu.microsoft.com```
```winatp-gw-weu.microsoft.com``` UK | ```uk.vortex-win.data.microsoft.com```
```uk-v20.events.data.microsoft.com```
```winatp-gw-uks.microsoft.com```
```winatp-gw-ukw.microsoft.com``` -AU | ```au.vortex-win.data.microsoft.com```
```au-v20.events.data.microsoft.com```
```winatp-gw-aue.microsoft.com```
```winatp-gw-aus.microsoft.com``` - - - If a proxy or firewall is blocking anonymous traffic, as Windows Defender ATP sensor is connecting from system context, make sure anonymous traffic is permitted in the above listed URLs. +If a proxy or firewall is blocking anonymous traffic, as Windows Defender ATP sensor is connecting from system context, make sure anonymous traffic is permitted in the above listed URLs. ## Verify client connectivity to Windows Defender ATP service URLs From f67f059b37e21a725ce8be304f88676b87de160d Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 29 May 2018 13:41:45 -0700 Subject: [PATCH 8/9] date --- ...roxy-internet-windows-defender-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md index 02ecae6123..3e89ac6e0a 100644 --- a/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection.md @@ -10,7 +10,7 @@ ms.pagetype: security ms.author: macapara author: mjcaparas ms.localizationpriority: high -ms.date: 05/03/2018 +ms.date: 05/29/2018 --- From 4978f52090d37fc7f2827cb7e968a1b84db95353 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Tue, 29 May 2018 13:42:48 -0700 Subject: [PATCH 9/9] slight updates from tech review --- .../update/servicing-stack-updates.md | 6 +++--- windows/deployment/update/waas-quick-start.md | 20 +++++++++---------- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/windows/deployment/update/servicing-stack-updates.md b/windows/deployment/update/servicing-stack-updates.md index f356277c28..196ca53038 100644 --- a/windows/deployment/update/servicing-stack-updates.md +++ b/windows/deployment/update/servicing-stack-updates.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date: 05/25/2018 +ms.date: 05/29/2018 --- # Servicing stack updates @@ -22,7 +22,7 @@ The "servicing stack" is the code that installs other operating system updates. ## Why should servicing stack updates be installed and kept up to date? -Having the latest servicing stack update is a prerequisite to reliably installing the latest quality updates and feature updates. +Having the latest servicing stack update is a prerequisite to reliably installing the latest quality updates and feature updates. ## When are they released? @@ -35,5 +35,5 @@ Typically, the improvements are reliability, security, and performance improveme ## Installation notes • Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system. -• Installing servicing stack update does not require restarting the device, so installation should not be disruptive. +• Installing servicing stack update does not require restarting the device, so installation should not be disruptive. • Servicing stack update releases are specific to the operating system version (build number), much like quality updates. diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index 94c2bf0cba..1f5292084f 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -7,7 +7,7 @@ ms.sitesec: library author: Jaimeo ms.localizationpriority: high ms.author: jaimeo -ms.date: 05/25/2018 +ms.date: 05/29/2018 --- # Quick guide to Windows as a service @@ -19,38 +19,38 @@ ms.date: 05/25/2018 - 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](index.md) is available explaining all the specifics and nuances, here is a quick guide to the most important concepts. +Windows as a service is a new concept, introduced with the release of Windows 10. While [an extensive set of documentation](index.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 twice per year, around March and September. 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. Typically released the second Tuesday of each month (though they can be released at any time), these include security updates, critical updates, servicing stack updates, and driver updates. Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. The "servicing stack" is the code that installs other updates, so they are important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md). +- **Feature updates** will be released twice per year, around March and September. 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** deliver both security and non-security fixes. They are typically released on the second Tuesday of each month ("Patch Tuesday"), though they can be released at any time. Quality updates include security updates, critical updates, servicing stack updates, and driver updates. Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. The "servicing stack" is the code that installs other updates, so they are important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md). - **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 channels** allow organizations to choose when to deploy new features. - The **Semi-Annual Channel** receives feature updates twice per year. - The **Long Term Servicing Channel**, which is designed to be used only for specialized devices (which typically don't run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years. -- **Deployment rings** are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization. +- **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 -Windows 10 gains new functionality with twice-per-year feature update releases. Initially, organizations will use these feature update releases for pilot deployments to ensure compatibility with existing apps and infrastructure. After a period of time, typically about four months after the feature update release, broad deployment throughout the organization can begin. The exact timeframe is determined by feedback from customers, ISVs, OEMs, and others, with an explicit "ready for broad deployment" declaration signaling this to customers. +Windows 10 gains new functionality with twice-per-year feature update releases. Initially, organizations will use these feature update releases for pilot deployments to ensure compatibility with existing apps and infrastructure. After a period of time, typically about four months after the feature update release, broad deployment throughout the organization can begin. The exact timeframe is determined by feedback from customers, ISVs, OEMs, and others, with an explicit "ready for broad deployment" declaration signaling this to customers. Each Windows 10 feature update will be serviced with quality updates for 18 months from the date of the feature update release. -Windows 10 Enterprise LTSB is a separate **Long Term Servicing Channel** 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. +Windows 10 Enterprise LTSB is a separate **Long Term Servicing Channel** 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 channels for Windows 10 updates](waas-servicing-channels-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 Analytics Upgrade Readiness](https://www.microsoft.com/en-us/WindowsForBusiness/windows-analytics), a free tool to streamline Windows upgrade projects, is another important tool to help. +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 Analytics Upgrade Readiness](https://www.microsoft.com/en-us/WindowsForBusiness/windows-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, broad deployment can begin. +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, broad deployment can begin. -This process repeats with each new feature update, twice 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. +This process repeats with each new feature update, twice 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.