Squashed commit of the following:

commit 3239ec9cfd2799bc557da4a5fbcf836b422338ac
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 07:01:00 2016 -0700

    LTSB

commit 12d2e63b50aa32f23c5bbd331311630fd4d303c3
Merge: 8ca56df bbea844
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Oct 21 06:59:08 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 8ca56df779611a9f0362b9cd59fb53a65db9fa2a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 12:52:30 2016 -0700

    change note format

commit 2acbacbeaf0361ed32107a71087bf00a99f1ea80
Merge: 79fc385 2c7daec
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 10:56:25 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 79fc385e7e0d2bec1c41479a5473f81e28f16b6a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 09:52:36 2016 -0700

    Adrienne feedback

commit d4d628c509c2594d3e6359324d5d164fa3c49f8b
Merge: 337815c d726120
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Oct 20 09:51:48 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 337815c59081c9fca9a8a674bb3af363cd5bd6a3
Merge: 615d187 e7f5095
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 09:22:25 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 615d18796d855992db06b340e433a5c3ef3ea0bb
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 08:47:20 2016 -0700

    tweak

commit c0880b278097a04e5a8ac7f516d329f6f6928b82
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 08:35:05 2016 -0700

    remove edit

commit a199d2c58a18c7037ef65f5c0d408d6ea2d3ba5c
Merge: 35ef393 464227c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Oct 19 08:29:59 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 35ef393d724a9ada6f21024c7addfc2ebaff2d55
Merge: 535eac9 bd40ef2
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 13:36:27 2016 -0700

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdltsb

commit 535eac959f575813729f33659af25bf6aa2c627d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 10:36:31 2016 -0700

    add change history to index

commit 7bf8ed5ec05537b09a153cab897a982ec7b48275
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 10:35:15 2016 -0700

    fix change history

commit 5e71fc2cb3a36d2813144c2f5d76711e4be8a75f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 10:20:19 2016 -0700

    add change hsitory

commit c07f9ac004d876a02417c4d418ac949f7b4a1c9d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Oct 17 09:25:51 2016 -0700

    add new topic
This commit is contained in:
jdeckerMS
2016-10-21 07:37:08 -07:00
parent bbea8448d1
commit ad3156ea57
6 changed files with 73 additions and 1 deletions

View File

@ -1,5 +1,6 @@
# [Surface](index.md)
## [Deploy Surface devices](deploy.md)
### [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md)
### [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md)
### [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)
### [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
@ -21,5 +22,6 @@
### [Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
## [Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)
## [Surface Data Eraser](microsoft-surface-data-eraser.md)
## [Change history for Surface documentation](change-history-for-surface.md)

View File

@ -28,7 +28,8 @@ To update the UEFI on Surface Pro 3, you can download and install the Surface UE
## Manually configure additional security settings
>**Note:**&nbsp;&nbsp;To enter firmware setup on a Surface device, begin with the device powered off, press and hold the **Volume Up** button, then press and release the **Power** button, then release the **Volume Up** button after the device has begun to boot.
>[!NOTE]
>To enter firmware setup on a Surface device, begin with the device powered off, press and hold the **Volume Up** button, then press and release the **Power** button, then release the **Volume Up** button after the device has begun to boot.
After the v3.11.760.0 UEFI update is installed on a Surface device, an additional UEFI menu named **Advanced Device Security** becomes available. If you click this menu, the following options are displayed:

View File

@ -0,0 +1,23 @@
---
title: Change history for Surface documentation (Windows 10)
description: This topic lists new and updated topics in the Surface documentation library.
ms.prod: w10
ms.mktglfcycl: manage
ms.sitesec: library
author: jdeckerMS
---
# Change history for Surface documentation
This topic lists new and updated topics in the Surface documentation library.
## October 2016
| New or changed topic | Description |
| --- | --- |
| [Long-term servicing branch for Surface devices](ltsb-for-surface.md) | New |
 

View File

@ -16,6 +16,7 @@ Get deployment guidance for your Surface devices including information about MDT
| Topic | Description |
| --- | --- |
| [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md) | Explains that LTSB is not supported for general-purpose Surface devices and should be used for specialized devices only. |
| [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md) | Walk through the recommended process of how to deploy Windows 10 to your Surface devices with the Microsoft Deployment Toolkit.|
| [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)| Find out how to perform a Windows 10 upgrade deployment to your Surface devices. |
| [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)| Walk through the process of customizing the Surface out-of-box experience for end users in your organization.|

View File

@ -29,6 +29,7 @@ For more information on planning for, deploying, and managing Surface devices in
| [Surface Enterprise Management Mode](surface-enterprise-management-mode.md) | See how this feature of Surface devices with Surface UEFI allows you to secure and manage firmware settings within your organization. |
| [Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md) | Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device. |
| [Surface Data Eraser](microsoft-surface-data-eraser.md) | Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices. |
| [Change history for Surface documentation](change-history-for-surface.md) | This topic lists new and updated topics in the Surface documentation library. |

View File

@ -0,0 +1,44 @@
---
title: Long-Term Servicing Branch for Surface devices (Surface)
description: LTSB is not supported for general-purpose Surface devices and should be used for specialized devices only.
ms.prod: w10
ms.mktglfcycl: manage
ms.pagetype: surface, devices
ms.sitesec: library
author: jdeckerMS
---
# Long-Term Servicing Branch (LTSB) for Surface devices
General-purpose Surface devices running Long-Term Servicing Branch (LTSB) are not supported. As a general guideline, if a Surface device runs productivity software, such as Microsoft Office, it is a general-purpose device that does not qualify for LTSB and should instead run Current Branch (CB) or Current Branch for Business (CBB).
>[!NOTE]
>For more information about the servicing branches, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/manage/waas-overview).
LTSB prevents Surface devices from receiving critical Windows 10 feature updates and certain non-security servicing updates. Customers with poor experiences using Surface devices in the LTSB configuration will be instructed to upgrade to CB or CBB. Furthermore, the Windows 10 Enterprise LTSB edition removes core features of Surface devices, including seamless inking and touch-friendly applications. It does not contain key in-box applications including Microsoft Edge, OneNote, Calendar or Camera. Therefore, productivity is impacted and functionality is limited. LTSB is not supported as a suitable servicing solution for general-purpose Surface devices.
General-purpose Surface devices are intended to run CB or CBB to receive full servicing and firmware updates and forward compatibility with the introduction of new Surface features. With CB, feature updates are available as soon as Microsoft releases them. Customers in the CBB servicing model receive the same build of Windows 10 as those in CB, at a later date.
Surface devices in specialized scenarios such as PCs that control medical equipment, point-of-sale systems, and ATMs may consider the use of LTSB. These special-purpose systems typically perform a single task and do not require feature updates as frequently as other devices in the organization.
## Related topics
- [Surface TechCenter](https://technet.microsoft.com/windows/surface)
- [Surface for IT pros blog](http://blogs.technet.com/b/surface/)