mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 06:47:21 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-7542905
This commit is contained in:
LizRoss
commit
44a88ed13a
@ -31,8 +31,16 @@ Initiating a reset will return the device to the last cumulative Windows update,
|
||||
|
||||
**To reset a Surface Hub**
|
||||
1. On your Surface Hub, open **Settings**.
|
||||
|
||||
|
||||
|
||||
2. Click **Update & Security**.
|
||||
3. Click **Recovery**, and then click **Reset Device**.
|
||||
|
||||
|
||||
|
||||
3. Click **Recovery**, and then click **Get started**.
|
||||
|
||||
|
||||
|
||||
**Important Note**</br>
|
||||
Performing a device reset may take up to 6 hours. Do not interrupt the reset process. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
|
||||
BIN
devices/surface-hub/images/sh-settings-reset-device.png
Normal file
BIN
devices/surface-hub/images/sh-settings-reset-device.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
devices/surface-hub/images/sh-settings-update-security.png
Normal file
BIN
devices/surface-hub/images/sh-settings-update-security.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
devices/surface-hub/images/sh-settings.png
Normal file
BIN
devices/surface-hub/images/sh-settings.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
@ -81,6 +81,8 @@ Figure 5 shows the required frameworks for the Surface app.
|
||||
|
||||
*Figure 5. Required frameworks for the Surface app*
|
||||
|
||||
>**Note:** The version numbers of the Surface app and required frameworks will change as the apps are updated. Check for the latest version of Surface app and each framework in Windows Store for Business. Always use the Surface app and recommended framework versions as provided by Windows Store for Business. Using outdated frameworks or the incorrect versions may result in errors or application crashes.
|
||||
|
||||
To download the required frameworks for the Surface app, follow these steps:
|
||||
1. Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
2. Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
|
||||
@ -1,4 +1,5 @@
|
||||
# [Deploy Windows 10](index.md)
|
||||
## [Deploy Windows 10 in a test lab](windows-10-poc.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
### [Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)
|
||||
|
||||
BIN
windows/deploy/images/PoC.png
Normal file
BIN
windows/deploy/images/PoC.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 95 KiB |
@ -16,6 +16,7 @@ Learn about deploying Windows 10 for IT professionals.
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) |This topic lists new and updated topics in the Deploy Windows 10 documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
|
||||
|[Deploy Windows 10 in a test lab](windows-10-poc.md) |This guide provides instructions for setting up a proof of concept (PoC) lab using Hyper-V and a minimum amount of resources. |
|
||||
|[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) |To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task. |
|
||||
|[Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) |This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 specifically. |
|
||||
|[Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md) |If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or, more specifically, MDT 2013 Update 2. |
|
||||
|
||||
28
windows/deploy/windows-10-poc-mdt.md
Normal file
28
windows/deploy/windows-10-poc-mdt.md
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Placeholder (Windows 10)
|
||||
description: Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
## In this guide
|
||||
|
||||
## Related Topics
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
28
windows/deploy/windows-10-poc-sccm.md
Normal file
28
windows/deploy/windows-10-poc-sccm.md
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Placeholder (Windows 10)
|
||||
description: Deploy Windows 10 in a test lab using System Center Configuration Manager
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Deploy Windows 10 in a test lab using System Center Configuration Manager
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
## In this guide
|
||||
|
||||
## Related Topics
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
193
windows/deploy/windows-10-poc.md
Normal file
193
windows/deploy/windows-10-poc.md
Normal file
@ -0,0 +1,193 @@
|
||||
---
|
||||
title: Deploy Windows 10 in a test lab (Windows 10)
|
||||
description: Concepts and procedures for deploying Windows 10 in a proof of concept lab environment.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Step by step guide: Demonstrate Windows 10 deployment in a test lab
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
## In this guide
|
||||
|
||||
This guide provides instructions for configuring a test lab to be used as a proof of concept (PoC) environment where you can deploy Windows 10. The PoC enviroment is configured using Hyper-V and a minimum amount of resources. Additional guides leverage the PoC environment and provide detailed steps for deploying Windows 10 under common scenarios with current deployment tools. The following topics are available in this guide:
|
||||
|
||||
<table border="0" cellpadding="2">
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Topic</td>
|
||||
<td BGCOLOR="#a0e4fa">Description</td>
|
||||
<tr>
|
||||
<td>[Hardware and software requirements](#hardware-and-software-requirements)</td>
|
||||
<td>Prerequisites to configure the PoC environment.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>[Lab setup](#lab-setup)</td>
|
||||
<td>A summary of the PoC environment.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>[Configure the PoC environment](#configure-the-poc-environment)</td>
|
||||
<td>Step by step instructions to configure the PoC environment.</td>
|
||||
</tr>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>[Step by step: Deploy Windows 10](#windows-10-poc-guides)</td>
|
||||
<td>Child topics that provide step by step instructions to deploy Windows 10 using the PoC environment.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
## Hardware and software requirements
|
||||
|
||||
Two computers are required to complete this guide:
|
||||
|
||||
<table border="1" cellpadding="2">
|
||||
<tr>
|
||||
<td></td>
|
||||
<td BGCOLOR="#a0e4fa">**Computer 1**</td>
|
||||
<td BGCOLOR="#a0e4fa">**Computer 2**</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Role</td>
|
||||
<td>Hyper-V host</td>
|
||||
<td>Client</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Description</td>
|
||||
<td>This computer will run Hyper-V, the Hyper-V management tools, and the Hyper-V Windows PowerShell module.</td>
|
||||
<td>This computer is a test system on your corporate network that will be converted to a VHD.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">OS</td>
|
||||
<td>Windows 8/8.1/10 or Windows Server 2012/2012 R2/2016</td>
|
||||
<td>Windows 7 or a later</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Edition</td>
|
||||
<td>Enterprise, Professional, or Education</td>
|
||||
<td>Any</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Architecture</td>
|
||||
<td>64-bit</td>
|
||||
<td>Any*</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">RAM</td>
|
||||
<td>8 GB RAM (16 GB recommended)</td>
|
||||
<td>Any</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Disk</td>
|
||||
<td>50 GB available hard disk space (100 GB recommended)</td>
|
||||
<td>Any</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">CPU</td>
|
||||
<td>SLAT-Capable CPU</td>
|
||||
<td>Any</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">Network</td>
|
||||
<td>Internet connection</td>
|
||||
<td>Any</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
>*Retaining applications and settings during the upgrade process requires that architecture (32 or 64-bit) is the same before and after the upgrade.
|
||||
|
||||
## Lab setup
|
||||
|
||||
The Hyper-V host computer is configured to host four VMs on a private, proof of concept network. Links are provided to download trial versions of Windows Server 2012 and all deployment tools necessary to complete the lab.
|
||||
- Two VMs are running Windows Server 2012 R2 with required network services and tools installed.
|
||||
- Two VMs are client systems: One VM is intended to mirror a host on your corporate network and one VM is running Windows 10 to demonstrate the hardware replacement scenario.
|
||||
|
||||
See the following diagram:
|
||||
|
||||
|
||||
|
||||
**Note**:
|
||||
>If you have an existing Hyper-V host, you can use this host if desired and skip the Hyper-V installation section in this guide. If your Hyper-V host is running Windows Server 2008 R2, you must enable PowerShell functionality to complete the steps in this guide.
|
||||
|
||||
>The two Windows Server VMs can be combined into a single VM to conserve RAM and disk space if required. However, instructions in this guide assume two server systems are used. Using two servers enables Active Directory Domain Services and DHCP to be installed on a server that is not directly connected to the corporate network. This mitigates the risk of clients on the corporate network receiving DHCP leases from the PoC network (i.e. "rogue" DHCP), and limits NETBIOS service broadcasts to the corporate network.
|
||||
|
||||
## Configure the PoC environment
|
||||
|
||||
### In this section
|
||||
|
||||
[Install Hyper-V](#install-hyper-v)<BR>
|
||||
[Download VHDs](#download-vhds)<BR>
|
||||
[Configure Hyper-V](#configure-hyper-v)<BR>
|
||||
[Configure VHDs](#configure-vhds)<BR>
|
||||
[Verify the configuration](#verify-the-configuration)
|
||||
|
||||
### Install Hyper-V
|
||||
|
||||
Use one of the following procedures to install Hyper-V on the Hyper-V host computer:
|
||||
|
||||
- [Install Hyper-V on a computer running Windows 8/8.1/10](#to-install-hyper-v-on-a-computer-running-windows-8-8-1-10)<BR>
|
||||
- [Install Hyper-V on a computer running Windows Server 2012/2012 R2/2016](#to-install-hyper-v-on-a-computer-running-windows-server-2012-2012-r2-2016)
|
||||
|
||||
####To install Hyper-V on a computer running Windows 8/8.1/10
|
||||
|
||||
1. Verify that the computer supports Hyper-V.
|
||||
|
||||
Starting with Windows 8, the host computer’s microprocessor must support second level address translation (SLAT) to install Hyper-V. See [Hyper-V: List of SLAT-Capable CPUs for Hosts](http://social.technet.microsoft.com/wiki/contents/articles/1401.hyper-v-list-of-slat-capable-cpus-for-hosts.aspx) for more information. To verify your computer supports SLAT, open an administrator command prompt, type systeminfo, press ENTER, and review the section displayed at the bottom of the output, next to Hyper-V Requirements.
|
||||
|
||||
See the following example:
|
||||
|
||||
```
|
||||
C:\>systeminfo
|
||||
...
|
||||
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
|
||||
Virtualization Enabled In Firmware: Yes
|
||||
Second Level Address Translation: Yes
|
||||
Data Execution Prevention Available: Yes
|
||||
```
|
||||
In this example, the computer supports SLAT and Hyper-V.
|
||||
|
||||
If one or more requirements are evaluated as "No" then the computer does not support installing Hyper-V. However, if only the virtualization setting is incompatible, you might be able to enable virtualization in the BIOS and change the "Virtualization Enabled In Firmware" setting from "No" to "Yes." The location of this setting will depend on the manufacturer and BIOS version, but is typically found associated with the BIOS security settings.
|
||||
|
||||
Note: A 64-bit operating system is requried to run Hyper-V.
|
||||
|
||||
2. Enable Hyper-V.
|
||||
|
||||
The Hyper-V feature is not installed by default. To get it, open an elevated Windows PowerShell window and type the following command:
|
||||
|
||||
```
|
||||
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
|
||||
```
|
||||
When you are prompted to restart the computer, choose Yes. The computer might restart more than once.
|
||||
|
||||
You can also install Hyper-V using the Control Panel in Windows, under Turn Windows features on or off, as shown below:
|
||||
|
||||
|
||||
|
||||
####To install Hyper-V on a computer running Windows Server 2012/2012 R2/2016
|
||||
|
||||
### Download VHDs
|
||||
|
||||
### Configure Hyper-V
|
||||
|
||||
### Configure VHDs
|
||||
|
||||
## Windows 10 PoC guides
|
||||
|
||||
- [Step by step: Deploy Windows 10 PoC with System Center Configuration Manager](windows-10-poc-sccm.md)
|
||||
- [Step by step: Deploy Windows 10 PoC with the Microsoft Deployment Toolkit](windows-10-poc-mdt.md)
|
||||
|
||||
## Related Topics
|
||||
|
||||
[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.pagetype: security
|
||||
|
||||
This topic for the IT professional explains how a Microsoft account works to enhance security and privacy for users, and how you can manage this consumer account type in your organization.
|
||||
|
||||
Microsoft sites, services, and properties such as Windows Live, MSN, Xbox LIVE, Zune, Windows Phone, and computers running Windows 8.1, Windows 8, and Windows RT use a Microsoft account as a mean of identifying users. Microsoft account is the name for what was previously called Windows Live ID. It has user-defined secrets associated with it, and it consists of a unique email address and a password.
|
||||
Microsoft sites, services, and properties such as Windows Live, MSN, Xbox LIVE, Zune, Windows Phone, and computers running Windows 10, Windows 8.1, Windows 8, and Windows RT use a Microsoft account as a mean of identifying users. Microsoft account is the name for what was previously called Windows Live ID. It has user-defined secrets associated with it, and it consists of a unique email address and a password.
|
||||
|
||||
There are some benefits and considerations when using Microsoft accounts in the enterprise. For more information, see [Microsoft account in the enterprise](#bkmk-msaccountintheenterprise) later in this topic.
|
||||
|
||||
@ -82,11 +82,11 @@ Although the Microsoft account was designed to serve consumers, you might find s
|
||||
|
||||
- **Download Windows Store apps**:
|
||||
|
||||
If your enterprise chooses to distribute software through the Windows Store, your users can use their Microsoft accounts to download and use them on up to five devices running any version of Windows 8.1, Windows 8, or Windows RT.
|
||||
If your enterprise chooses to distribute software through the Windows Store, your users can use their Microsoft accounts to download and use them on up to five devices running any version of Windows 10, Windows 8.1, Windows 8, or Windows RT.
|
||||
|
||||
- **Single sign-on**:
|
||||
|
||||
Your users can use Microsoft account credentials to sign in to devices running Windows 8.1, Windows 8 or Windows RT. When they do this, Windows works with your Windows Store app to provide authenticated experiences for them. Users can associate a Microsoft account with their sign-in credentials for Windows Store apps or websites, so that these credentials roam across any devices running these supported versions.
|
||||
Your users can use Microsoft account credentials to sign in to devices running Windows 10, Windows 8.1, Windows 8 or Windows RT. When they do this, Windows works with your Windows Store app to provide authenticated experiences for them. Users can associate a Microsoft account with their sign-in credentials for Windows Store apps or websites, so that these credentials roam across any devices running these supported versions.
|
||||
|
||||
- **Personalized settings synchronization**:
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ author: brianlic-msft
|
||||
|
||||
Microsoft is dedicated to provide our customers with a secure operating system, such as Windows 10 and Windows Server, as well as secure apps, such as Microsoft Edge. In addition to the security assurance of its products, Microsoft also enables you to have fine control of your environments by providing various configuration capabilities. Even though Windows and Windows Server are designed to be secure out-of-the-box, a large number of organizations still want more granular control of their security configurations. To navigate these large number of controls, organizations need guidance for configuring various security features. Microsoft provides this guidance in the form of security baselines.
|
||||
|
||||
We recommend implementing an industry-standard configuration that is broadly known and well-tested, such as a Mirosoft security baseline, as opposed to creating one yourself. This helps increase flexibility and reduce costs.
|
||||
We recommend implementing an industry-standard configuration that is broadly known and well-tested, such as a Microsoft security baseline, as opposed to creating one yourself. This helps increase flexibility and reduce costs.
|
||||
|
||||
## What are security baselines?
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@
|
||||
### [Reset a Windows 10 Mobile device](reset-a-windows-10-mobile-device.md)
|
||||
## [Join Windows 10 Mobile to Azure Active Directory](join-windows-10-mobile-to-azure-active-directory.md)
|
||||
## [Configure devices without MDM](configure-devices-without-mdm.md)
|
||||
## [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md)
|
||||
## [Windows 10 servicing options](introduction-to-windows-10-servicing.md)
|
||||
## [Application development for Windows as a service](application-development-for-windows-as-a-service.md)
|
||||
## [Windows Store for Business](windows-store-for-business.md)
|
||||
### [Sign up and get started](sign-up-windows-store-for-business-overview.md)
|
||||
|
||||
|
Before Width: | Height: | Size: 78 KiB After Width: | Height: | Size: 78 KiB |
|
Before Width: | Height: | Size: 92 KiB After Width: | Height: | Size: 92 KiB |
|
Before Width: | Height: | Size: 8.4 KiB After Width: | Height: | Size: 8.4 KiB |
@ -57,7 +57,7 @@ Learn about managing and updating Windows 10.
|
||||
<td align="left"><p>Create a runtime provisioning package to apply settings, profiles, and file assets to a device running Windows 10 Pro, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile, or Windows 10 Mobile Enterprise.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md)</p></td>
|
||||
<td align="left"><p>[Windows 10 servicing options](introduction-to-windows-10-servicing.md)</p></td>
|
||||
<td align="left"><p>This article describes the new servicing options available in Windows 10, Windows 10 Mobile, and Windows 10 IoT Core (IoT Core) and how they enable enterprises to keep their devices current with the latest feature upgrades. It also covers related topics, such as how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
|
||||
@ -10,27 +10,46 @@ ms.pagetype: security, servicing
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Windows 10 servicing options for updates and upgrades
|
||||
# Windows 10 servicing options
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10 IoT Core (IoT Core)
|
||||
|
||||
This article describes the new servicing options available in Windows 10 and IoT Core and how they enable enterprises to keep their devices current with the latest feature upgrades. It also covers related topics, such as how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles.
|
||||
This article provides detailed information about new servicing options available in Windows 10 and IoT Core. It also provides information on how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles. Before reading this article, you should understand the new Windows 10 servicing model. For an overview of this servicing model, see: [Windows 10 servicing overview](../plan/windows-10-servicing-options.md).
|
||||
|
||||
For Windows 10 current version numbers by servicing option see: [Windows 10 release information](https://technet.microsoft.com/en-us/windows/mt679505.aspx).
|
||||
|
||||
**Note**
|
||||
Several of the figures in this article show multiple feature upgrades of Windows being released by Microsoft over time. Be aware that these figures were created with dates that were chosen for illustrative clarity, not for release roadmap accuracy, and should not be used for planning purposes.
|
||||
|
||||
## Introduction
|
||||
## Key terminology
|
||||
|
||||
In enterprise IT environments, the desire to provide users with the latest technologies needs to be balanced with the need for manageability and cost control. In the past, many enterprises managed their Windows deployments homogeneously and performed large-scale upgrades to new releases of Windows (often in parallel with large-scale hardware upgrades) about every three to six years. Today, the rapid evolution of Windows as a platform for device-like experiences is causing businesses to rethink their upgrade strategies. Especially with the release of Windows 10, there are good business reasons to keep a significant portion of your enterprise's devices *current* with the latest release of Windows. For example, during the development of Windows 10, Microsoft:
|
||||
- Streamlined the Windows product engineering and release cycle so that Microsoft can deliver the features, experiences, and functionality customers want, more quickly than ever.
|
||||
- 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.
|
||||
- Implemented new servicing options – referred to as Current Branch (CB), Current Branch for Business (CBB), and Long-Term Servicing Branch (LTSB) – that provide pragmatic solutions to keep more devices more current in enterprise environments than was previously possible.
|
||||
The following terms are used When discussing the new Windows 10 servicing model:
|
||||
|
||||
The remainder of this article provides additional information about each of these areas. This article also provides an overview of the planning implications of the three Windows 10 servicing options (summarized in Table 1) so that IT administrators can be well-grounded conceptually before they start a Windows 10 deployment project.
|
||||
<table border="1" cellpadding="2">
|
||||
<tr>
|
||||
<td BGCOLOR="#a0e4fa">**Term**</td>
|
||||
<td BGCOLOR="#a0e4fa">**Description**</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Upgrade</td>
|
||||
<td>A new Windows 10 release that contains additional features and capabilities, released two to three times per year.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Update</td>
|
||||
<td>Packages of security fixes, reliability fixes, and other bug fixes that are released periodically, typically once a month on Update Tuesday (sometimes referred to as Patch Tuesday). With Windows 10, these are cumulative in nature.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Branch</td>
|
||||
<td>The windows servicing branch is one of four choices: Windows Insider, Current Branch, Current Branch for Business, or Long-Term Servicing Branch. Branches are determined by the frequency with which the computer is configured to receive feature updates.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Ring</td>
|
||||
<td>A ring is a groups of PCs that are all on the same branch and have the same update settings. Rings can be used internally by organizations to better control the upgrade rollout process.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
## Windows 10 servicing
|
||||
|
||||
The following table provides an overview of the planning implications of the three Windows 10 servicing options so that IT administrators can be well-grounded conceptually before they start a Windows 10 deployment project.
|
||||
|
||||
Table 1. Windows 10 servicing options
|
||||
|
||||
@ -91,7 +110,7 @@ At the end of each approximately four month period, Microsoft executes a set of
|
||||
|
||||
Although Windows 10 will enable IT administrators to defer installation of new feature upgrades using Windows Update, enterprises may also want additional control over how and when Windows Update installs releases. With this need in mind, Microsoft [announced Windows Update for Business](http://go.microsoft.com/fwlink/p/?LinkId=624798) in May of 2015. Microsoft designed Windows Update for Business to provide IT administrators with additional Windows Update-centric management capabilities, such as the ability to deploy updates to groups of devices and to define maintenance windows for installing releases. This article will be updated with additional information about the role of Windows Update for Business in servicing Windows 10 devices as it becomes available.
|
||||
|
||||
## Windows 10 servicing options
|
||||
## Windows 10 servicing branches
|
||||
|
||||
Historically, because of the length of time between releases of new Windows versions, and the relatively low number of enterprise devices that were upgraded to newer versions of Windows during their deployment lifetimes, most IT administrators defined servicing as installing the updates that Microsoft published every month. Looking forward, because Microsoft will be publishing new feature upgrades on a continual basis, *servicing* will also include (on some portion of an enterprise's devices) installing new feature upgrades as they become available.
|
||||
In fact, when planning to deploy Windows 10 on a device, one of the most important questions for IT administrators to ask is, “What should happen to this device when Microsoft publishes a new feature upgrade?” This is because Microsoft designed Windows 10 to provide businesses with multiple servicing options, centered on enabling different rates of feature upgrade adoption. In particular, IT administrators can configure Windows 10 devices to:
|
||||
@ -100,6 +119,144 @@ In fact, when planning to deploy Windows 10 on a device, one of the most import
|
||||
- Receive only servicing updates for the duration of their Windows 10 deployment in order to reduce the number of non-essential changes made to the device. For more information, see [Install servicing updates only by using Long-Term Servicing Branch (LTSB) servicing](#install-updates-ltsb).
|
||||
The breakout of a company’s devices by the categories above is likely to vary significantly by industry and other factors. What is most important is that companies can decide what works best for them and can choose different options for different devices.
|
||||
|
||||
## Current Branch versus Current Branch for Business
|
||||
|
||||
When the development of a new Windows 10 feature upgrade is complete, it is initially offered to Current Branch computers; those computers configured for Current Branch for Business will receive the feature upgrade (with additional fixes) at a later date, generally at least four months later. An additional deferral of at least eight months is available to organizations that use tools to control the update process. During this time, monthly security updates will continue to be made available to machines not yet upgraded.
|
||||
|
||||
The process to configure a PC for Current Branch for Business is simple. The **Defer upgrades** setting needs to be configured, either manually (through the Settings app), by using Group Policy, or by using mobile device management (MDM).
|
||||
|
||||
|
||||
|
||||
Figure 1. Configure the **Defer upgrades** setting
|
||||
|
||||
Most organizations today leverage Windows Server Update Services (WSUS) or System Center Configuration Manager to update their PCs. With Windows 10, this does not need to change; all updates are controlled through approvals or automatic deployment rules configured in those products, so new upgrades will not be deployed until the organization chooses. The **Defer upgrades** setting can function as an additional validation check, so that Current Branch for Business machines that are targeted with a new upgrade prior to the end of the initial four-month deferral period will decline to install it; they can install the upgrade any time within the eight-month window after that initial four-month deferral period.
|
||||
|
||||
For computers configured to receive updates from Windows Update directly, the **Defer upgrades** setting directly controls when the PC will be upgraded. Computers that are not configured to defer upgrades will be upgraded at the time of the initial Current Branch release; computers that are configured to defer upgrades will be upgraded four months later.
|
||||
|
||||
With Windows 10 it is now possible to manage updates for PCs and tablets that have a higher degree of mobility and are not joined to a domain. For these PCs, you can leverage mobile device management (MDM) services or Windows Update for Business to provide the same type of control provided today with WSUS or Configuration Manager.
|
||||
|
||||
For PCs enrolled in a mobile device management (MDM) service, Windows 10 provides new update approval mechanisms that could be leveraged to delay the installation of a new feature upgrade or any other update. Windows Update for Business will eventually provide these and other capabilities to manage upgrades and updates; more details on these capabilities will be provided when they are available later in 2015.
|
||||
|
||||
With the release of each Current Branch feature update, new ISO images will be made available. You can use these images to upgrade existing machines or to create new custom images. These feature upgrades will also be published with WSUS to enable simple deployment to devices already running Windows 10.
|
||||
|
||||
Unlike previous versions of Windows, the servicing lifetime of Current Branch or Current Branch for Business is finite. You must install new feature upgrades on machines running these branches in order to continue receiving monthly security updates. This requires new ways of thinking about software deployment. It is best to align your deployment schedule with the Current Branch release schedule:
|
||||
|
||||
- Begin your evaluation process with the Windows Insider Program releases.
|
||||
- Perform initial pilot deployments by using the Current Branch.
|
||||
- Expand to broad deployment after the Current Branch for Business is available.
|
||||
- Complete deployments by using that release in advance of the availability of the next Current Branch.
|
||||
|
||||
|
||||
|
||||
Figure 2. Deployment timeline
|
||||
|
||||
Some organizations may require more than 12 months to deploy Windows 10 to all of their existing PCs. To address this, it may be necessary to deploy multiple Windows 10 releases, switching to these new releases during the deployment project. Notice how the timelines can overlap, with the evaluation of one release happening during the pilot and deployment of the previous release:
|
||||
|
||||
|
||||
|
||||
Figure 3. Overlapping releases
|
||||
|
||||
As a result of these overlapping timelines, organizations can choose which release to deploy. Note though that by continuing for longer with one release, that gives you less time to deploy the subsequent release (to both existing Windows 10 PCs as well as newly-migrated ones), so staying with one release for the full lifetime of that release can be detrimental overall.
|
||||
|
||||
## Long-Term Servicing Branch
|
||||
|
||||
For specialized devices, Windows 10 Enterprise Long Term Servicing Branch (LTSB) ISO images will be made available. These are expected to be on a variable schedule, less often than CB and CBB releases. Once released, these will be supported with security and reliability fixes for an extended period; no new features will be added over its servicing lifetime. Note that LTSB images will not contain most in-box Universal Windows Apps (for example, Microsoft Edge, Cortana, the Windows Store, the Mail and Calendar apps) because the apps or the services that they use will be frequently updated with new functionality and therefore cannot be supported on PCs running the LTSB OS.
|
||||
|
||||
These LTSB images can be used to upgrade existing machines or to create new custom images.
|
||||
|
||||
Note that Windows 10 Enterprise LTSB installations fully support the Universal Windows Platform, with the ability to run line-of-business apps created using the Windows SDK, Visual Studio, and related tools capable of creating Universal Windows apps. For apps from other ISVs (including those published in the Windows Store), contact the ISV to confirm if they will provide long-term support for their specific apps.
|
||||
|
||||
As mentioned previously, there are few, if any, scenarios where an organization would use the Long-Term Servicing Branch for every PC – or even for a majority of them.
|
||||
|
||||
## Windows Insider Program
|
||||
|
||||
During the development of a new Windows 10 feature update, preview releases will be made available to Windows Insider Program participants. This enables those participants to try out new features, check application compatibility, and provide feedback during the development process.
|
||||
|
||||
To obtain Windows Insider Program builds, the Windows Insider Program participants must opt in through the Settings app, and specify their Microsoft account.
|
||||
|
||||
Occasionally (typically as features are made available to those in the Windows Insider Program “slow” ring), new ISO images will be released to enable deployment validation, testing, and image creation.
|
||||
|
||||
## Switching between branches
|
||||
|
||||
During the life of a particular PC, it may be necessary or desirable to switch between the available branches. Depending on the branch you are using, the exact mechanism for doing this can be different; some will be simple, others more involved.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">For a PC that uses…</th>
|
||||
<th align="left">Changing to…</th>
|
||||
<th align="left">You need to:</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left">Windows Insider Program</td>
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Wait for the final Current Branch release.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<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>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use the Settings app to enroll the device in the Windows Insider Program.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Select the <strong>Defer upgrade</strong> setting, or move the PC to a target group or flight that will not receive the next upgrade until it is business ready. Note that this change will not have any immediate impact; it only prevents the installation of the next Current Branch release.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use the Settings app to enroll the device in the Windows Insider Program.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<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>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use media to upgrade to the latest Windows Insider Program build.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Use media to upgrade to a later Current Branch build. (Note that the Current Branch build must be a later build.)</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Use media to upgrade to a later Current Branch for Business build (Current Branch build plus fixes). Note that it must be a later build.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Plan for Windows 10 deployment
|
||||
|
||||
The remainder of this article focuses on the description of the three options outlined above, and their planning implications, in more detail. In practice, IT administrators have to focus on two areas when planning a Windows 10 device deployment:
|
||||
@ -111,19 +268,21 @@ The content that follows will provide IT administrators with the context needed
|
||||
|
||||
**How Microsoft releases Windows 10 feature upgrades**
|
||||
|
||||
When it is time to release a build as a new feature upgrade for Windows 10, Microsoft performs several processes in sequence. The first process involves creating either one or two servicing branches in a source code management system. These branches (shown in Figure 1) are required to produce feature upgrade installation media and servicing update packages that can be deployed on different Windows 10 editions, running in different configurations.
|
||||
>Some figures in this article show multiple feature upgrades of Windows being released by Microsoft over time. Be aware that these figures were created with dates that were chosen for illustrative clarity, not for release roadmap accuracy, and should not be used for planning purposes.
|
||||
|
||||
|
||||
When it is time to release a build as a new feature upgrade for Windows 10, Microsoft performs several processes in sequence. The first process involves creating either one or two servicing branches in a source code management system. These branches (shown in Figure 4) are required to produce feature upgrade installation media and servicing update packages that can be deployed on different Windows 10 editions, running in different configurations.
|
||||
|
||||
Figure 1. Feature upgrades and servicing branches
|
||||
|
||||
|
||||
In all cases, Microsoft creates a servicing branch (referred to in Figure 1 as Servicing Branch \#1) that is used to produce releases for approximately one year (although the lifetime of the branch will ultimately depend on when Microsoft publishes subsequent feature upgrade releases). If Microsoft has selected the feature upgrade to receive long-term servicing-only support, Microsoft also creates a second servicing branch (referred to in Figure 1 as Servicing Branch \#2) that is used to produce servicing update releases for up to 10 years.
|
||||
Figure 4. Feature upgrades and servicing branches
|
||||
|
||||
As shown in Figure 2, when Microsoft publishes a new feature upgrade, Servicing Branch \#1 is used to produce the various forms of media needed by OEMs, businesses, and consumers to install Windows 10 Home, Pro, Education, and Enterprise editions. Microsoft also produces the files needed by Windows Update to distribute and install the feature upgrade, along with *targeting* information that instructs Windows Update to only install the files on devices configured for *immediate* installation of feature upgrades.
|
||||
In all cases, Microsoft creates a servicing branch (referred to in Figure 4 as Servicing Branch \#1) that is used to produce releases for approximately one year (although the lifetime of the branch will ultimately depend on when Microsoft publishes subsequent feature upgrade releases). If Microsoft has selected the feature upgrade to receive long-term servicing-only support, Microsoft also creates a second servicing branch (referred to in Figure 4 as Servicing Branch \#2) that is used to produce servicing update releases for up to 10 years.
|
||||
|
||||
|
||||
As shown in Figure 5, when Microsoft publishes a new feature upgrade, Servicing Branch \#1 is used to produce the various forms of media needed by OEMs, businesses, and consumers to install Windows 10 Home, Pro, Education, and Enterprise editions. Microsoft also produces the files needed by Windows Update to distribute and install the feature upgrade, along with *targeting* information that instructs Windows Update to only install the files on devices configured for *immediate* installation of feature upgrades.
|
||||
|
||||
Figure 2. Producing feature upgrades from servicing branches
|
||||
|
||||
|
||||
Figure 5. Producing feature upgrades from servicing branches
|
||||
|
||||
Approximately four months after publishing the feature upgrade, Microsoft uses Servicing Branch \#1 again to *republish* updated installation media for Windows 10 Pro, Education, and Enterprise editions. The updated media contains the exact same feature upgrade as contained in the original media except Microsoft also includes all the servicing updates that were published since the feature upgrade was first made available. This enables the feature upgrade to be installed on a device more quickly, and in a way that is potentially less obtrusive to users.
|
||||
|
||||
@ -131,15 +290,15 @@ Concurrently, Microsoft also changes the way the feature upgrade is published in
|
||||
|
||||
**How Microsoft publishes the Windows 10 Enterprise LTSB Edition**
|
||||
|
||||
If Microsoft has selected the feature upgrade to receive long-term servicing support, Servicing Branch \#2 is used to publish the media needed to install the Windows 10 Enterprise LTSB edition. The time between releases of feature upgrades with long-term servicing support will vary between one and three years, and is strongly influenced by input from customers regarding the readiness of the release for long-term enterprise deployment. Figure 2 shows the Windows 10 Enterprise LTSB edition being published at the same time as the other Windows 10 editions, which mirrors the way editions were actually published for Windows 10 in July of 2015. It is important to note that this media is never published to Windows Update for deployment. Installations of the Enterprise LTSB edition on devices must be performed another way.
|
||||
If Microsoft has selected the feature upgrade to receive long-term servicing support, Servicing Branch \#2 is used to publish the media needed to install the Windows 10 Enterprise LTSB edition. The time between releases of feature upgrades with long-term servicing support will vary between one and three years, and is strongly influenced by input from customers regarding the readiness of the release for long-term enterprise deployment. Figure 5 shows the Windows 10 Enterprise LTSB edition being published at the same time as the other Windows 10 editions, which mirrors the way editions were actually published for Windows 10 in July of 2015. It is important to note that this media is never published to Windows Update for deployment. Installations of the Enterprise LTSB edition on devices must be performed another way.
|
||||
|
||||
**How Microsoft releases Windows 10 servicing updates**
|
||||
|
||||
As shown in Figure 3, servicing branches are also used by Microsoft to produce servicing updates containing fixes for security vulnerabilities and other important issues. Servicing updates are published in a way that determines the Windows 10 editions on which they can be installed. For example, servicing updates produced from a given servicing branch can only be installed on devices running a Windows 10 edition produced from the same servicing branch. In addition, because Windows 10 Home does not support deferred installation of feature upgrades, servicing updates produced from Servicing Branch \#1 are targeted at devices running Windows 10 Home only until Microsoft publishes feature upgrades for deferred installation.
|
||||
As shown in Figure 6, servicing branches are also used by Microsoft to produce servicing updates containing fixes for security vulnerabilities and other important issues. Servicing updates are published in a way that determines the Windows 10 editions on which they can be installed. For example, servicing updates produced from a given servicing branch can only be installed on devices running a Windows 10 edition produced from the same servicing branch. In addition, because Windows 10 Home does not support deferred installation of feature upgrades, servicing updates produced from Servicing Branch \#1 are targeted at devices running Windows 10 Home only until Microsoft publishes feature upgrades for deferred installation.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 3. Producing servicing updates from servicing branches
|
||||
Figure 6. Producing servicing updates from servicing branches
|
||||
|
||||
**Release installation alternatives**
|
||||
|
||||
@ -162,24 +321,24 @@ Because there is a one-to-one mapping between servicing options and servicing br
|
||||
|
||||
Although Microsoft is currently planning to release approximately two to three feature upgrades per year, the actual frequency and timing of releases will vary. Because the servicing lifetimes of feature upgrades typically end when the servicing lifetimes of other, subsequent feature upgrades begin, the lengths of servicing lifetimes will also vary.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 4. Example release cadence across multiple feature upgrades
|
||||
Figure 7. Example release cadence across multiple feature upgrades
|
||||
|
||||
To show the variability of servicing lifetimes, and show the paths that feature upgrade installations will take when Windows Update and Windows Server Update Services are used for deployments, Figure 4 contains three feature upgrade releases (labeled *X*, *Y*, and *Z*) and their associated servicing branches. The time period between publishing X and Y is four months, and the time period between publishing Y and Z is six months. X and Z have long-term servicing support, and Y has shorter-term servicing support only.
|
||||
|
||||
The same underlying figure will be used in subsequent figures to show all three servicing options in detail. It is important to note that Figure 4 is provided for illustration of servicing concepts only and should not be used for actual Windows 10 release planning.
|
||||
The same underlying figure will be used in subsequent figures to show all three servicing options in detail. It is important to note that Figure 7 is provided for illustration of servicing concepts only and should not be used for actual Windows 10 release planning.
|
||||
|
||||
To simplify the servicing lifetime and feature upgrade behavior explanations that follow, this document refers to branch designations for a specific feature upgrade as the +0 versions, the designations for the feature upgrade after the +0 version as the +1 (or successor) versions, and the designation for the feature upgrade after the +1 version as the +2 (or second successor) versions.
|
||||
|
||||
### <a href="" id="immediate-upgrade-cb"></a>
|
||||
|
||||
**Immediate feature upgrade installation with Current Branch (CB) servicing**
|
||||
As shown in Figure 5, the Current Branch (CB) designation refers to Servicing Branch \#1 during the period that starts when Microsoft publishes a feature upgrade targeted for devices configured for *immediate* installation and ends when Microsoft publishes the *successor* feature upgrade targeted for devices configured for *immediate* installation.
|
||||
As shown in Figure 8, the Current Branch (CB) designation refers to Servicing Branch \#1 during the period that starts when Microsoft publishes a feature upgrade targeted for devices configured for *immediate* installation and ends when Microsoft publishes the *successor* feature upgrade targeted for devices configured for *immediate* installation.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 5. Immediate installation with Current Branch Servicing
|
||||
Figure 8. Immediate installation with Current Branch Servicing
|
||||
|
||||
The role of Servicing Branch \#1 during the CB period is to produce feature upgrades and servicing updates for Windows 10 devices configured for *immediate* installation of new feature upgrades. Microsoft refers to devices configured this way as being *serviced from CBs*. The Windows 10 editions that support servicing from CBs are Home, Pro, Education, and Enterprise. The Current Branch designation is intended to reflect the fact that devices serviced using this approach will be kept as current as possible with respect to the latest Windows 10 feature upgrade release.
|
||||
Windows 10 Home supports Windows Update for release deployment. Windows 10 editions (Pro, Education, and Enterprise) support Windows Update, Windows Server Update Services, Configuration Manager, and other configuration management systems:
|
||||
@ -191,11 +350,11 @@ It is important to note that devices serviced from CBs must install two to three
|
||||
### <a href="" id="deferred-upgrade-cbb"></a>
|
||||
|
||||
**Deferred feature upgrade installation with Current Branch for Business (CBB) servicing**
|
||||
As shown in Figure 6, the Current Branch for Business (CBB) designation refers to Servicing Branch \#1 during the period that starts when Microsoft republishes a feature upgrade targeted for devices configured for *deferred* installation and ends when Microsoft republishes the *second successor* feature upgrade targeted for devices configured for *deferred* installation.
|
||||
As shown in Figure 9, the Current Branch for Business (CBB) designation refers to Servicing Branch \#1 during the period that starts when Microsoft republishes a feature upgrade targeted for devices configured for *deferred* installation and ends when Microsoft republishes the *second successor* feature upgrade targeted for devices configured for *deferred* installation.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 6. Deferred installation with Current Branch for Business Servicing
|
||||
Figure 9. Deferred installation with Current Branch for Business Servicing
|
||||
|
||||
The role of Servicing Branch \#1 during the CBB period is to produce feature upgrades and servicing updates for Windows 10 devices configured for *deferred* installation of new feature upgrades. Microsoft refers to devices configured this way as being *serviced from CBBs*. The Windows 10 editions that support servicing from CBBs are Pro, Education, and Enterprise. The Current Branch for Business designation is intended to reflect the fact that many businesses require IT administrators to test feature upgrades prior to deployment, and servicing devices from CBBs is a pragmatic solution for businesses with testing constraints to remain as current as possible.
|
||||
Windows 10 (Pro, Education, and Enterprise editions) support release deployment by using Windows Update, Windows Server Update Services, Configuration Manager, and other configuration management systems:
|
||||
@ -208,11 +367,11 @@ Microsoft designed Windows 10 servicing lifetime policies so that CBBs will rec
|
||||
|
||||
**Install servicing updates only by using Long-Term Servicing Branch (LTSB) servicing**
|
||||
|
||||
As shown in Figure 7, the Long-Term Servicing Branch (LTSB) designation refers to Servicing Branch \#2 from beginning to end. LTSBs begin when a feature upgrade with long-term support is published by Microsoft and end after 10 years. It is important to note that only the Windows 10 Enterprise LTSB edition supports long-term servicing, and there are important differences between this edition and other Windows 10 editions regarding upgradability and feature set (described below in the [Considerations when configuring devices for servicing updates only](#servicing-only) section).
|
||||
As shown in Figure 10, the Long-Term Servicing Branch (LTSB) designation refers to Servicing Branch \#2 from beginning to end. LTSBs begin when a feature upgrade with long-term support is published by Microsoft and end after 10 years. It is important to note that only the Windows 10 Enterprise LTSB edition supports long-term servicing, and there are important differences between this edition and other Windows 10 editions regarding upgradability and feature set (described below in the [Considerations when configuring devices for servicing updates only](#servicing-only) section).
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 7. Servicing updates only using LTSB Servicing
|
||||
Figure 10. Servicing updates only using LTSB Servicing
|
||||
|
||||
The role of LTSBs is to produce servicing updates for devices running Windows 10 configured to install servicing updates only. Devices configured this way are referred to as being *serviced from LTSBs*. The Long-Term Servicing Branch designation is intended to reflect the fact that this servicing option is intended for scenarios where changes to software running on devices must be limited to essential updates (such as those for security vulnerabilities and other important issues) for the duration of deployments.
|
||||
Windows 10 Enterprise LTSB supports release deployment by using Windows Update, Windows Server Update Services, Configuration Manager, and other configuration management systems:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# [Plan for Windows 10 deployment](index.md)
|
||||
## [Change history for Plan for Windows 10 deployment](change-history-for-plan-for-windows-10-deployment.md)
|
||||
## [Windows 10 servicing options](windows-10-servicing-options.md)
|
||||
## [Windows 10 servicing overview](windows-10-servicing-options.md)
|
||||
## [Windows 10 deployment considerations](windows-10-deployment-considerations.md)
|
||||
## [Windows 10 compatibility](windows-10-compatibility.md)
|
||||
## [Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
|
||||
@ -16,7 +16,7 @@ Windows 10 provides new deployment capabilities, scenarios, and tools by buildi
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Change history for Plan for Windows 10 deployment](change-history-for-plan-for-windows-10-deployment.md) |This topic lists new and updated topics in the Plan for Windows 10 deployment documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
|
||||
|[Windows 10 servicing options](windows-10-servicing-options.md) |Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. |
|
||||
|[Windows 10 servicing overview](windows-10-servicing-options.md) |Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. |
|
||||
|[Windows 10 deployment considerations](windows-10-deployment-considerations.md) |There are new deployment options in Windows 10 that help you simplify the deployment process and automate migration of existing settings and applications. |
|
||||
|[Windows 10 compatibility](windows-10-compatibility.md) |Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10. |
|
||||
|[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md) |There are specific infrastructure requirements to deploy and manage Windows 10 that should be in place prior to significant Windows 10 deployments within your organization. |
|
||||
|
||||
@ -7,56 +7,43 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: servicing
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Windows 10 servicing options
|
||||
|
||||
# Windows 10 servicing overview
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process.
|
||||
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](../manage/introduction-to-windows-10-servicing.md).
|
||||
|
||||
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 machines, or by migrating to the new operating system version as part of the hardware replacement cycle. Either way, organizations would invest significant time and effort to complete the required tasks.
|
||||
## The Windows servicing model
|
||||
|
||||
With Windows 10, a new model is being adopted. Instead of new features being added only in new releases that happen every few years, the goal is to provide new features two to three times per year, continually providing new capabilities while maintaining a high level of hardware and application compatibility. 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.
|
||||
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.
|
||||
|
||||
To support this process, you need to use simpler deployment methods. By combining these simpler methods (for example, in-place upgrade) with new techniques to deploy in phases to existing devices, you can reduce the amount of effort required overall, by taking the effort that used to be performed as part of a traditional deployment project and spreading it across a broad period of time.
|
||||
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.
|
||||
|
||||
## Key terminology
|
||||
## 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.
|
||||
|
||||
With the shift to this new Windows as a service model, it is important to understand the distinction between two key terms:
|
||||
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.
|
||||
|
||||
- **Upgrade**. A new Windows 10 release that contains additional features and capabilities, released two to three times per year.
|
||||
## Windows 10 servicing branches
|
||||
|
||||
- **Update**. Packages of security fixes, reliability fixes, and other bug fixes that are released periodically, typically once a month on Update Tuesday (sometimes referred to as Patch Tuesday). With Windows 10, these are cumulative in nature.
|
||||
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.
|
||||
|
||||
In addition to these terms, some additional concepts need to be understood:
|
||||
|
||||
- **Branches**. The concept of “branching” goes back many years, and represents how Windows has traditionally been written and serviced: Each release 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 of the increased frequency of upgrades.
|
||||
|
||||
- **Rings**. The concept of “rings” defines a mechanism for Windows 10 deployment to targeted groups of PCs; each ring represents another group. These are used as part of the release mechanism for new Windows 10 upgrades, and should be used internally by organizations to better control the upgrade rollout process.
|
||||
|
||||
## Windows 10 branch overview
|
||||
|
||||
|
||||
To support different needs and use cases within your organization, you can select among different branches:
|
||||
During the development of Windows 10, Microsoft implemented the following new servicing options:
|
||||
|
||||
|
||||
|
||||
- **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, small numbers of PCs can leverage the Windows Insider Program branch. These would typically be dedicated lab machines used for IT testing, secondary PCs used by IT administrators, and other non-critical devices.
|
||||
**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.)<BR>
|
||||
|
||||
- **Current Branch**. 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**. 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**. 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.)
|
||||
|
||||
Most organizations will leverage all of these choices, with the mix determined by how individual PCs are used. Some examples:
|
||||
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 |
|
||||
|--------------------|-------------------------|----------------|-----------------------------|----------------------------|
|
||||
@ -66,8 +53,6 @@ Most organizations will leverage all of these choices, with the mix determined b
|
||||
| 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; these should be considered only examples, not 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.
|
||||
@ -82,169 +67,12 @@ Because every organization is different, the exact breakdown will vary even with
|
||||
|
||||
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.
|
||||
|
||||
For more information about the Windows as a service model, refer to [Windows 10 servicing options for updates and upgrades](../manage/introduction-to-windows-10-servicing.md).
|
||||
In addition to implementing 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.
|
||||
|
||||
## Current Branch versus Current Branch for Business
|
||||
|
||||
|
||||
When the development of a new Windows 10 feature upgrade is complete, it is initially offered to Current Branch computers; those computers configured for Current Branch for Business will receive the feature upgrade (with additional fixes) at a later date, generally at least four months later. An additional deferral of at least eight months is available to organizations that use tools to control the update process. During this time, monthly security updates will continue to be made available to machines not yet upgraded.
|
||||
|
||||
The process to configure a PC for Current Branch for Business is simple. The **Defer upgrades** setting needs to be configured, either manually (through the Settings app), by using Group Policy, or by using mobile device management (MDM).
|
||||
|
||||
|
||||
|
||||
Figure 1. Configure the **Defer upgrades** setting
|
||||
|
||||
Most organizations today leverage Windows Server Update Services (WSUS) or System Center Configuration Manager to update their PCs. With Windows 10, this does not need to change; all updates are controlled through approvals or automatic deployment rules configured in those products, so new upgrades will not be deployed until the organization chooses. The **Defer upgrades** setting can function as an additional validation check, so that Current Branch for Business machines that are targeted with a new upgrade prior to the end of the initial four-month deferral period will decline to install it; they can install the upgrade any time within the eight-month window after that initial four-month deferral period.
|
||||
|
||||
For computers configured to receive updates from Windows Update directly, the **Defer upgrades** setting directly controls when the PC will be upgraded. Computers that are not configured to defer upgrades will be upgraded at the time of the initial Current Branch release; computers that are configured to defer upgrades will be upgraded four months later.
|
||||
|
||||
With Windows 10 it is now possible to manage updates for PCs and tablets that have a higher degree of mobility and are not joined to a domain. For these PCs, you can leverage mobile device management (MDM) services or Windows Update for Business to provide the same type of control provided today with WSUS or Configuration Manager.
|
||||
|
||||
For PCs enrolled in a mobile device management (MDM) service, Windows 10 provides new update approval mechanisms that could be leveraged to delay the installation of a new feature upgrade or any other update. Windows Update for Business will eventually provide these and other capabilities to manage upgrades and updates; more details on these capabilities will be provided when they are available later in 2015.
|
||||
|
||||
With the release of each Current Branch feature update, new ISO images will be made available. You can use these images to upgrade existing machines or to create new custom images. These feature upgrades will also be published with WSUS to enable simple deployment to devices already running Windows 10.
|
||||
|
||||
Unlike previous versions of Windows, the servicing lifetime of Current Branch or Current Branch for Business is finite. You must install new feature upgrades on machines running these branches in order to continue receiving monthly security updates. This requires new ways of thinking about software deployment. It is best to align your deployment schedule with the Current Branch release schedule:
|
||||
|
||||
- Begin your evaluation process with the Windows Insider Program releases.
|
||||
|
||||
- Perform initial pilot deployments by using the Current Branch.
|
||||
|
||||
- Expand to broad deployment after the Current Branch for Business is available.
|
||||
|
||||
- Complete deployments by using that release in advance of the availability of the next Current Branch.
|
||||
|
||||
|
||||
|
||||
Figure 2. Deployment timeline
|
||||
|
||||
Some organizations may require more than 12 months to deploy Windows 10 to all of their existing PCs. To address this, it may be necessary to deploy multiple Windows 10 releases, switching to these new releases during the deployment project. Notice how the timelines can overlap, with the evaluation of one release happening during the pilot and deployment of the previous release:
|
||||
|
||||
|
||||
|
||||
Figure 3. Overlapping releases
|
||||
|
||||
As a result of these overlapping timelines, organizations can choose which release to deploy. Note though that by continuing for longer with one release, that gives you less time to deploy the subsequent release (to both existing Windows 10 PCs as well as newly-migrated ones), so staying with one release for the full lifetime of that release can be detrimental overall.
|
||||
|
||||
## Long-Term Servicing Branch
|
||||
|
||||
|
||||
For specialized devices, Windows 10 Enterprise Long Term Servicing Branch (LTSB) ISO images will be made available. These are expected to be on a variable schedule, less often than CB and CBB releases. Once released, these will be supported with security and reliability fixes for an extended period; no new features will be added over its servicing lifetime. Note that LTSB images will not contain most in-box Universal Windows Apps (for example, Microsoft Edge, Cortana, the Windows Store, the Mail and Calendar apps) because the apps or the services that they use will be frequently updated with new functionality and therefore cannot be supported on PCs running the LTSB OS.
|
||||
|
||||
These LTSB images can be used to upgrade existing machines or to create new custom images.
|
||||
|
||||
Note that Windows 10 Enterprise LTSB installations fully support the Universal Windows Platform, with the ability to run line-of-business apps created using the Windows SDK, Visual Studio, and related tools capable of creating Universal Windows apps. For apps from other ISVs (including those published in the Windows Store), contact the ISV to confirm if they will provide long-term support for their specific apps.
|
||||
|
||||
As mentioned previously, there are few, if any, scenarios where an organization would use the Long-Term Servicing Branch for every PC – or even for a majority of them.
|
||||
|
||||
## Windows Insider Program
|
||||
|
||||
|
||||
During the development of a new Windows 10 feature update, preview releases will be made available to Windows Insider Program participants. This enables those participants to try out new features, check application compatibility, and provide feedback during the development process.
|
||||
|
||||
To obtain Windows Insider Program builds, the Windows Insider Program participants must opt in through the Settings app, and specify their Microsoft account.
|
||||
|
||||
Occasionally (typically as features are made available to those in the Windows Insider Program “slow” ring), new ISO images will be released to enable deployment validation, testing, and image creation.
|
||||
|
||||
## Switching between branches
|
||||
|
||||
|
||||
During the life of a particular PC, it may be necessary or desirable to switch between the available branches. Depending on the branch you are using, the exact mechanism for doing this can be different; some will be simple, others more involved.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">For a PC that uses…</th>
|
||||
<th align="left">Changing to…</th>
|
||||
<th align="left">You need to:</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left">Windows Insider Program</td>
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Wait for the final Current Branch release.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<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>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use the Settings app to enroll the device in the Windows Insider Program.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Select the <strong>Defer upgrade</strong> setting, or move the PC to a target group or flight that will not receive the next upgrade until it is business ready. Note that this change will not have any immediate impact; it only prevents the installation of the next Current Branch release.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use the Settings app to enroll the device in the Windows Insider Program.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<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>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Not directly possible (requires wipe-and-load).</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left">Long-Term Servicing Branch</td>
|
||||
<td align="left">Insider</td>
|
||||
<td align="left">Use media to upgrade to the latest Windows Insider Program build.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch</td>
|
||||
<td align="left">Use media to upgrade to a later Current Branch build. (Note that the Current Branch build must be a later build.)</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"></td>
|
||||
<td align="left">Current Branch for Business</td>
|
||||
<td align="left">Use media to upgrade to a later Current Branch for Business build (Current Branch build plus fixes). Note that it must be a later build.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
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 deployment considerations](windows-10-deployment-considerations.md)
|
||||
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)
|
||||
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)<BR>
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)<BR>
|
||||
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user