mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jdshrs2
This commit is contained in:
jdeckerMS
7
devices/hololens/breadcrumb/toc.yml
Normal file
7
devices/hololens/breadcrumb/toc.yml
Normal file
@ -0,0 +1,7 @@
|
||||
- name: Docs
|
||||
tocHref: /
|
||||
topicHref: /
|
||||
items:
|
||||
- name: Hololens
|
||||
tocHref: /hololens
|
||||
topicHref: /hololens/index
|
||||
@ -3,7 +3,8 @@
|
||||
"content": [
|
||||
{
|
||||
"files": [
|
||||
"**/*.md"
|
||||
"**/*.md",
|
||||
"**/**.yml"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**",
|
||||
@ -27,7 +28,13 @@
|
||||
],
|
||||
"overwrite": [],
|
||||
"externalReference": [],
|
||||
"globalMetadata": {},
|
||||
"globalMetadata": {
|
||||
"uhfHeaderId": "MSDocsHeader-WindowsIT",
|
||||
"breadcrumb_path": "/hololens/breadcrumb/toc.json",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "jdecker"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [
|
||||
null
|
||||
|
||||
@ -62,15 +62,14 @@ Using Intune, you can also [monitor your app deployment](https://docs.microsoft.
|
||||
|
||||
|
||||
## Use the Windows Device Portal to install apps on HoloLens.
|
||||
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/mixed-reality/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
|
||||
|
||||
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/holographic/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
|
||||
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_usb).
|
||||
|
||||
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_usb).
|
||||
|
||||
3. [Create a user name and password](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
|
||||
3. [Create a user name and password](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
|
||||
|
||||
>[!TIP]
|
||||
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
|
||||
4. In the Windows Device Portal, click **Apps**.
|
||||
|
||||
|
||||
@ -15,17 +15,17 @@ localizationpriority: medium
|
||||
|
||||
Kiosk mode limits the user's ability to launch new apps or change the running app. When kiosk mode is enabled for HoloLens, the bloom gesture and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||
|
||||
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/holographic/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
|
||||
1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/mixed-reality/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>When you set up HoloLens to use the Device Portal, you must enable **Developer Mode** on the device. **Developer Mode** on a device that has been upgraded to Windows Holographic for Business enables side-loading of apps, which risks the installation of apps that have not been certified by the Microsoft Store. Administrators can block the ability to enable **Developer Mode** using the **ApplicationManagement/AllowDeveloper Unlock** setting in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). [Learn more about Developer Mode.](https://msdn.microsoft.com/windows/uwp/get-started/enable-your-device-for-development#developer-mode)
|
||||
|
||||
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#connecting_over_usb).
|
||||
2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_usb).
|
||||
|
||||
3. [Create a user name and password](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
|
||||
3. [Create a user name and password](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
|
||||
|
||||
>[!TIP]
|
||||
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/holographic/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||
|
||||
4. In the Windows Device Portal, click **Kiosk Mode**.
|
||||
|
||||
|
||||
@ -47,7 +47,7 @@ When you run ADKsetup.exe for Windows 10, version 1607, select **Configuration D
|
||||
7. Expand **Runtime settings** and customize the package with any of the settings [described below](#what-you-can-configure).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/holographic/reset_or_recover_your_hololens#perform_a_full_device_recovery).
|
||||
>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/mixed-reality/reset_or_recover_your_hololens#perform_a_full_device_recovery).
|
||||
|
||||
8. On the **File** menu, click **Save**.
|
||||
|
||||
@ -107,7 +107,7 @@ In Windows ICD, when you create a provisioning package for Windows Holographic,
|
||||
|
||||
| Setting | Description |
|
||||
| --- | --- |
|
||||
| **Accounts** | Create a local account. HoloLens currently supports a single user only. Creating multiple local accounts in a provisioning package is not supported. <br><br>**IMPORTANT**<br>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/holographic/reset_or_recover_your_hololens#perform_a_full_device_recovery). |
|
||||
| **Accounts** | Create a local account. HoloLens currently supports a single user only. Creating multiple local accounts in a provisioning package is not supported. <br><br>**IMPORTANT**<br>If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/mixed-reality/reset_or_recover_your_hololens#perform_a_full_device_recovery). |
|
||||
| **Certificates** | Deploy a certificate to HoloLens. |
|
||||
| **ConnectivityProfiles** | Deploy a Wi-Fi profile to HoloLens. |
|
||||
| **EditionUpgrade** | [Upgrade to Windows Holographic for Business.](hololens-upgrade-enterprise.md) |
|
||||
|
||||
@ -11,7 +11,7 @@ localizationpriority: medium
|
||||
|
||||
# Microsoft HoloLens in the enterprise: requirements
|
||||
|
||||
When you develop for HoloLens, there are [system requirements and tools](https://developer.microsoft.com/windows/holographic/install_the_tools) that you need. In an enterprise environment, there are also a few requirements to use and manage HoloLens which are listed below.
|
||||
When you develop for HoloLens, there are [system requirements and tools](https://developer.microsoft.com/windows/mixed-reality/install_the_tools) that you need. In an enterprise environment, there are also a few requirements to use and manage HoloLens which are listed below.
|
||||
|
||||
## General use
|
||||
- Microsoft account or Azure Active Directory (Azure AD) account
|
||||
|
||||
@ -11,7 +11,7 @@ localizationpriority: medium
|
||||
|
||||
# Unlock Windows Holographic for Business features
|
||||
|
||||
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the [Commercial Suite](https://developer.microsoft.com/windows/holographic/release_notes#introducing_microsoft_hololens_commercial_suite), which provides extra features designed for business.
|
||||
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the [Commercial Suite](https://developer.microsoft.com/windows/mixed-reality/release_notes#introducing_microsoft_hololens_commercial_suite), which provides extra features designed for business.
|
||||
|
||||
When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic for Business. This license can be applied to the device either through the organization's [mobile device management (MDM) provider](#edition-upgrade-using-mdm) or a [provisioning package](#edition-upgrade-using-a-provisioning-package).
|
||||
|
||||
|
||||
@ -33,8 +33,8 @@ localizationpriority: medium
|
||||
|
||||
- [Help for using HoloLens](https://support.microsoft.com/products/hololens)
|
||||
|
||||
- [Documentation for Holographic app development](https://developer.microsoft.com/windows/holographic/documentation)
|
||||
- [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/documentation)
|
||||
|
||||
- [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
|
||||
|
||||
- [HoloLens release notes](https://developer.microsoft.com/en-us/windows/holographic/release_notes)
|
||||
- [HoloLens release notes](https://developer.microsoft.com/en-us/windows/mixed-reality/release_notes)
|
||||
7
devices/surface-hub/breadcrumb/toc.yml
Normal file
7
devices/surface-hub/breadcrumb/toc.yml
Normal file
@ -0,0 +1,7 @@
|
||||
- name: Docs
|
||||
tocHref: /
|
||||
topicHref: /
|
||||
items:
|
||||
- name: Surface Hub
|
||||
tocHref: /surface-hub
|
||||
topicHref: /surface-hub/index
|
||||
@ -3,7 +3,7 @@
|
||||
"content":
|
||||
[
|
||||
{
|
||||
"files": ["**/**.md"],
|
||||
"files": ["**/**.md", "**/**.yml"],
|
||||
"exclude": ["**/obj/**"]
|
||||
}
|
||||
],
|
||||
@ -13,8 +13,16 @@
|
||||
"exclude": ["**/obj/**"]
|
||||
}
|
||||
],
|
||||
"globalMetadata": {
|
||||
"ROBOTS": "INDEX, FOLLOW"
|
||||
"globalMetadata": {
|
||||
"uhfHeaderId": "MSDocsHeader-WindowsIT",
|
||||
"breadcrumb_path": "/surface-hub/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.mktglfcycl": "manage",
|
||||
"author": "jdeckerms",
|
||||
"ms.sitesec": "library",
|
||||
"ms.author": "jdecker"
|
||||
},
|
||||
"externalReference": [
|
||||
],
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: On-premises deployment multi-forest (Surface Hub)
|
||||
description: This topic explains how you add a device account for your Microsoft Surface Hub when you have a multi-forest, on-premises deployment.
|
||||
ms.assetid: 80E12195-A65B-42D1-8B84-ECC3FCBAAFC6
|
||||
keywords: multi forest deployment, on prem deployment, device account, Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,10 +1,13 @@
|
||||
---
|
||||
title: Use fully qualified doman name with Surface Hub
|
||||
description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
|
||||
ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
|
||||
keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: support
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
---
|
||||
|
||||
# Configure domain name for Skype for Business
|
||||
@ -22,4 +25,4 @@ There are a few scenarios where you need to specify the domain name of your Skyp
|
||||
> [!TIP]
|
||||
> You can type multiple domain names, separated by commas. <br> For example: lync.com, outlook.com, lync.glbdns.microsoft.com
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
# [Surface](index.md)
|
||||
## [Deploy Surface devices](deploy.md)
|
||||
### [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md)
|
||||
### [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.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)
|
||||
|
||||
7
devices/surface/breadcrumb/toc.yml
Normal file
7
devices/surface/breadcrumb/toc.yml
Normal file
@ -0,0 +1,7 @@
|
||||
- name: Docs
|
||||
tocHref: /
|
||||
topicHref: /
|
||||
items:
|
||||
- name: Surface
|
||||
tocHref: /surface
|
||||
topicHref: /surface/index
|
||||
@ -11,6 +11,14 @@ author: jdeckerMS
|
||||
|
||||
This topic lists new and updated topics in the Surface documentation library.
|
||||
|
||||
|
||||
## April 2017
|
||||
|
||||
|New or changed topic | Description |
|
||||
| --- | --- |
|
||||
|[Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md) | New (supersedes [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md))|
|
||||
|
||||
|
||||
## January 2017
|
||||
|
||||
|New or changed topic | Description |
|
||||
|
||||
@ -16,7 +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. |
|
||||
| [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition. |
|
||||
| [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.|
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
"content":
|
||||
[
|
||||
{
|
||||
"files": ["**/**.md"],
|
||||
"files": ["**/**.md", "**/**.yml"],
|
||||
"exclude": ["**/obj/**"]
|
||||
}
|
||||
],
|
||||
@ -14,7 +14,12 @@
|
||||
}
|
||||
],
|
||||
"globalMetadata": {
|
||||
"ROBOTS": "INDEX, FOLLOW"
|
||||
"uhfHeaderId": "MSDocsHeader-WindowsIT",
|
||||
"breadcrumb_path": "/surface/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "jdecker"
|
||||
},
|
||||
"externalReference": [
|
||||
],
|
||||
|
||||
@ -10,6 +10,8 @@ author: jdeckerMS
|
||||
|
||||
# Long-Term Servicing Branch (LTSB) for Surface devices
|
||||
|
||||
>[!WARNING]
|
||||
>For updated information on this topic, see [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md). For additional information on this update, see the [Documentation Updates for Surface and Windows 10 LTSB Compatibility](https://blogs.technet.microsoft.com/surface/2017/04/11/documentation-updates-for-surface-and-windows-10-ltsb-compatibility) post on the Surface Blog for IT Pros.
|
||||
|
||||
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).
|
||||
|
||||
|
||||
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Surface device compatibility with Windows 10 Long-Term Servicing Branch (Surface)
|
||||
description: Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition.
|
||||
keywords: ltsb, update, surface servicing options
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: DavbeaMSFT
|
||||
---
|
||||
|
||||
# Surface device compatibility with Windows 10 Long-Term Servicing Branch (LTSB)
|
||||
|
||||
Surface devices are designed to provide best-in-class experiences in productivity and general-purpose scenarios. Regular updates enable Surface devices to bring to life new innovations and to evolve with the new capabilities delivered by Windows 10 Feature Updates. Feature Updates are available only in Windows 10 Pro or Windows 10 Enterprise editions that receive continuous updates through the Current Branch (CB) or Current Branch for Business (CBB) servicing options.
|
||||
|
||||
In contrast to the CB and CBB servicing options, you cannot select the Long-Term Servicing Branch (LTSB) option in Windows 10 settings. To use the LTSB servicing option, you must install a separate edition of Windows 10 Enterprise, known as *Windows 10 Enterprise LTSB*. In addition to providing an extended servicing model, the Windows 10 Enterprise LTSB edition also provides an environment with several Windows components removed. The core Surface experiences that are impacted by LTSB include:
|
||||
|
||||
* Windows Feature Updates, including enhancements such as:
|
||||
|
||||
* Improvements to Direct Ink and palm rejection provided in Windows 10, version 1607 (also referred to as the Anniversary Update)
|
||||
* Improved support for high DPI applications provided in Windows 10, version 1703 (also referred to as the Creators Update)
|
||||
|
||||
* Pressure sensitivity settings provided by the Surface app
|
||||
|
||||
* The Windows Ink Workspace
|
||||
|
||||
* Key touch-optimized in-box applications including Microsoft Edge, OneNote, Calendar, and Camera
|
||||
|
||||
The use of the Windows 10 Enterprise LTSB environment on Surface devices results in sub-optimal end-user experiences and you should avoid using it in environments where users want and expect a premium, up-to-date user experience.
|
||||
|
||||
The LTSB servicing option is designed for device types and scenarios where the key attribute is for features or functionality to never change. Examples include systems that power manufacturing or medical equipment, or embedded systems in kiosks, such as ATMs or airport ticketing systems.
|
||||
|
||||
>[!NOTE]
|
||||
>For general information about Windows servicing branches, including LTSB, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/update/waas-overview#long-term-servicing-branch).
|
||||
|
||||
>[!NOTE]
|
||||
>As a general guideline, devices that fulfill the following criteria are considered general-purpose devices and should be paired with Windows 10 Pro or Windows 10 Enterprise using the CB or CBB servicing option:
|
||||
|
||||
* Devices that run productivity software such as Microsoft Office
|
||||
|
||||
* Devices that use Windows Store applications
|
||||
|
||||
* Devices that are used for general Internet browsing (for example, research or access to social media)
|
||||
|
||||
Before you choose to use Windows 10 Enterprise LTSB edition on Surface devices, consider the following limitations:
|
||||
|
||||
* Driver and firmware updates are not explicitly tested against releases of Windows 10 Enterprise LTSB.
|
||||
|
||||
* If you encounter problems, Microsoft Support will provide troubleshooting assistance. However, due to the servicing nature of the Windows LTSB, issue resolution may require that devices be upgraded to a more recent version of Windows 10 Enterprise LTSB, or to Windows 10 Pro or Enterprise with the CB or CBB servicing option.
|
||||
|
||||
* Surface device replacements (for example, devices replaced under warranty) may contain subtle variations in hardware components that require updated device drivers and firmware. Compatibility with these updates may require the installation of a more recent version of Windows 10 Enterprise LTSB or Windows 10 Pro or Enterprise with the CB or CBB servicing option.
|
||||
|
||||
>[!NOTE]
|
||||
>Organizations that standardize on a specific version of Windows 10 Enterprise LTSB may be unable to adopt new generations of Surface hardware without also updating to a later version of Windows 10 Enterprise LTSB or Windows 10 Pro or Enterprise. For more information, see the **How will Windows 10 LTSBs be supported?** topic in the **Supporting the latest processor and chipsets on Windows** section of [Lifecycle Policy FAQ—Windows products](https://support.microsoft.com/help/18581/lifecycle-policy-faq-windows-products#b4).
|
||||
|
||||
Surface devices running Windows 10 Enterprise LTSB edition will not receive new features. In many cases these features are requested by customers to improve the usability and capabilities of Surface hardware. For example, new improvements for High DPI applications in Windows 10, version 1703. Customers that use Surface devices in the LTSB configuration will not see the improvements until they either update to a new Windows 10 Enterprise LTSB release or upgrade to a version of Windows 10 with support for the CB and CBB servicing options.
|
||||
|
||||
Devices can be changed from Windows 10 Enterprise LTSB to a more recent version of Windows 10 Enterprise, with support for the CB and CBB servicing options, without the loss of user data by performing an upgrade installation. You can also perform an upgrade installation on multiple devices by leveraging the Upgrade Task Sequence Templates available in the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager. For more information, see [Upgrade Surface devices to Windows 10 with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/upgrade-surface-devices-to-windows-10-with-mdt).
|
||||
@ -104,6 +104,33 @@ Microsoft Surface Dock Updater logs its progress into the Event Log, as shown in
|
||||
|
||||
*Figure 8. Surface Dock Updater events in Event Viewer*
|
||||
|
||||
## Changes and updates
|
||||
|
||||
Microsoft periodically updates Surface Dock Updater. To learn more about the application of firmware by Surface Dock Updater, see [Manage Surface Dock firmware updates](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-dock-firmware-updates).
|
||||
|
||||
>[!Note]
|
||||
>Each update to Surface Dock firmware is included in a new version of Surface Dock Updater. To update a Surface Dock to the latest firmware, you must use the latest version of Surface Dock Updater.
|
||||
|
||||
### Version 1.0.8.0
|
||||
|
||||
This version of Surface Dock Updater adds support for the following:
|
||||
|
||||
* Update for Surface Dock Main Chipset firmware
|
||||
* Update for Surface Dock DisplayPort firmware
|
||||
|
||||
### Version 2.0.22.0
|
||||
|
||||
This version of Surface Dock Updater adds support for the following:
|
||||
|
||||
* Update for Surface Dock USB firmware
|
||||
* Improved reliability of Ethernet, audio, and USB ports
|
||||
|
||||
### Version 2.1.6.0
|
||||
|
||||
This version of Surface Dock Updater adds support for the following:
|
||||
|
||||
* Updated firmware for Surface Dock DisplayPort
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
Reference in New Issue
Block a user