Merge branch 'public' of https://github.com/MicrosoftDocs/windows-itpro-docs into public
@ -86,6 +86,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/guidance-and-best-practices-wip",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure",
|
||||
"redirect_document_id": false
|
||||
@ -757,17 +762,17 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings",
|
||||
"redirect_url": "hhttps://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-available-settings",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview",
|
||||
"redirect_url": "https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-set-individual-device.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-set-individual-device",
|
||||
"redirect_url": "https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -996,6 +1001,11 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-devicefilecertificateinfobeta-table.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-devicefilecertificateinfo-table",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-alertevents-table.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-devicealertevents-table",
|
||||
"redirect_document_id": true
|
||||
@ -7827,11 +7837,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit",
|
||||
"redirect_document_id": true
|
||||
@ -7882,16 +7887,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/integrate-configuration-manager-with-mdt-2013.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt-2013",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/introduction-vamt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/volume-activation/introduction-vamt",
|
||||
"redirect_document_id": true
|
||||
@ -13103,7 +13098,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/keep-secure/windows-defender-smartscreen-available-settings.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings",
|
||||
"redirect_url": "https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-available-settings",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -13113,7 +13108,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/keep-secure/windows-defender-smartscreen-set-individual-device.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-set-individual-device",
|
||||
"redirect_url": "https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -15773,7 +15768,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/deploy-windows-10-with-configuration-manager",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -15787,18 +15782,8 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-mdt/deploy-windows-10-with-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/get-started-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -15870,6 +15855,10 @@
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/deploy-windows-10-with-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/get-started-with-configuraton-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager#integrate-configuration-manager-with-mdt", "redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
@ -17,7 +17,7 @@ ms.date: 10/02/2018
|
||||
---
|
||||
|
||||
# Microsoft Edge system and language requirements
|
||||
>Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
|
||||
> Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
|
||||
|
||||
> [!NOTE]
|
||||
> You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).
|
||||
@ -25,8 +25,8 @@ ms.date: 10/02/2018
|
||||
Microsoft Edge is the new, default web browser for Windows 10, helping you to experience modern web standards, better performance, improved security, and increased reliability. Microsoft Edge lets you stay up-to-date through the Microsoft Store and to manage your enterprise through Group Policy or your mobile device management (MDM) tools.
|
||||
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016, don’t include Microsoft Edge or many other Universal Windows Platform (UWP) apps. Systems running the LTSB operating systems do not support these apps because their services get frequently updated with new functionality. For customers who require the LTSB for specialized devices, we recommend using Internet Explorer 11.
|
||||
> [!IMPORTANT]
|
||||
> The Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016, don’t include Microsoft Edge or many other Universal Windows Platform (UWP) apps. Systems running the LTSB operating systems do not support these apps because their services get frequently updated with new functionality. For customers who require the LTSB for specialized devices, we recommend using Internet Explorer 11.
|
||||
|
||||
|
||||
## Minimum system requirements
|
||||
|
@ -23,8 +23,8 @@ ms.sitesec: library
|
||||
|
||||
You can customize the favorites bar, for example, you can turn off features such as Save a Favorite and Import settings, and hide or show the favorites bar on all pages. Another customization you can make is provisioning a standard list of favorites, including folders, to appear in addition to the user’s favorites. If it’s important to keep the favorites in both IE11 and Microsoft Edge synced, you can turn on syncing where changes to the list of favorites in one browser reflect in the other.
|
||||
|
||||
>[!TIP]
|
||||
>You can find the Favorites under C:\\Users\\<_username_>\\Favorites.
|
||||
> [!TIP]
|
||||
> You can find the Favorites under C:\\Users\\<_username_>\\Favorites.
|
||||
|
||||
You can find the Microsoft Edge Group Policy settings in the following location of the Group Policy Editor unless otherwise noted in the policy:
|
||||
|
||||
|
@ -21,12 +21,11 @@ ms.topic: reference
|
||||
|
||||
Microsoft Edge is the default browser experience for Windows 10 and Windows 10 Mobile. However, Microsoft Edge lets you continue to use IE11 for sites that are on your corporate intranet or included on your Enterprise Mode Site List. If you are running web apps that continue to use ActiveX controls, x-ua-compatible headers, or legacy document modes, you need to keep running them in IE11. IE11 offers additional security, manageability, performance, backward compatibility, and modern standards support.
|
||||
|
||||
>[!TIP]
|
||||
>If you are running an earlier version of Internet Explorer, we recommend upgrading to IE11, so that any legacy apps continue to work correctly.
|
||||
> [!TIP]
|
||||
> If you are running an earlier version of Internet Explorer, we recommend upgrading to IE11, so that any legacy apps continue to work correctly.
|
||||
|
||||
**Technology not supported by Microsoft Edge**
|
||||
|
||||
|
||||
- ActiveX controls
|
||||
|
||||
- Browser Helper Objects
|
||||
@ -45,14 +44,13 @@ Using Enterprise Mode means that you can continue to use Microsoft Edge as your
|
||||
|
||||
## Relevant group policies
|
||||
|
||||
1. [Configure the Enterprise Mode Site List](#configure-the-enterprise-mode-site-list)
|
||||
|
||||
1. [Configure the Enterprise Mode Site List](#configure-the-enterprise-mode-site-list)
|
||||
2. [Send all intranet sites to Internet Explorer 11](#send-all-intranet-sites-to-internet-explorer-11)
|
||||
|
||||
2. [Send all intranet sites to Internet Explorer 11](#send-all-intranet-sites-to-internet-explorer-11)
|
||||
3. [Show message when opening sites in Internet Explorer](#show-message-when-opening-sites-in-internet-explorer)
|
||||
|
||||
3. [Show message when opening sites in Internet Explorer](#show-message-when-opening-sites-in-internet-explorer)
|
||||
|
||||
4. [(IE11 policy) Send all sites not included in the Enterprise Mode Site List to Microsoft Edge](#ie11-policy-send-all-sites-not-included-in-the-enterprise-mode-site-list-to-microsoft-edge)
|
||||
4. [(IE11 policy) Send all sites not included in the Enterprise Mode Site List to Microsoft Edge](#ie11-policy-send-all-sites-not-included-in-the-enterprise-mode-site-list-to-microsoft-edge)
|
||||
|
||||
You can find the Microsoft Edge Group Policy settings in the following location of the Group Policy Editor unless otherwise noted in the policy:
|
||||
|
||||
|
@ -3,14 +3,15 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/28/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
<!-- ## Configure Home Button-->
|
||||
<!-- ## Configure Home Button-->
|
||||
>*Supported versions: Microsoft Edge on Windows 10, version 1809*<br>
|
||||
> *Supported versions: Microsoft Edge on Windows 10, version 1809*<br>
|
||||
> *Default setting: Disabled or not configured (Show home button and load the Start page)*
|
||||
|
||||
|
||||
[!INCLUDE [configure-home-button-shortdesc](../shortdesc/configure-home-button-shortdesc.md)]
|
||||
@ -28,9 +29,8 @@ ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>If you want to make changes to this policy:<ol><li>Enable the **Unlock Home Button** policy.</li><li>Make changes to the **Configure Home Button** policy or **Set Home Button URL** policy.</li><li>Disable the **Unlock Home Button** policy.</li></ol>
|
||||
> [!TIP]
|
||||
> If you want to make changes to this policy:<ol><li>Enable the **Unlock Home Button** policy.</li><li>Make changes to the **Configure Home Button** policy or **Set Home Button URL** policy.</li><li>Disable the **Unlock Home Button** policy.</li></ol>
|
||||
|
||||
### ADMX info and settings
|
||||
#### ADMX info
|
||||
@ -54,8 +54,6 @@ ms.topic: include
|
||||
### Related policies
|
||||
|
||||
- [Set Home Button URL](../available-policies.md#set-home-button-url): [!INCLUDE [set-home-button-url-shortdesc](../shortdesc/set-home-button-url-shortdesc.md)]
|
||||
- [Set Home Button URL](../available-policies.md#set-home-button-url): [!INCLUDE [set-home-button-url-shortdesc](../shortdesc/set-home-button-url-shortdesc.md)]
|
||||
- [Unlock Home Button](../available-policies.md#unlock-home-button): [!INCLUDE [unlock-home-button-shortdesc](../shortdesc/unlock-home-button-shortdesc.md)]
|
||||
|
||||
|
||||
<hr>
|
||||
|
@ -3,15 +3,16 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
<!-- Configure Open Microsoft Edge With-->
|
||||
|
||||
|
||||
>*Supported versions: Microsoft Edge on Windows 10, version 1809*<br>
|
||||
> *Supported versions: Microsoft Edge on Windows 10, version 1809*<br>
|
||||
> *Default setting: Enabled (A specific page or pages)*
|
||||
|
||||
[!INCLUDE [configure-open-microsoft-edge-with-shortdesc](../shortdesc/configure-open-microsoft-edge-with-shortdesc.md)]
|
||||
|
||||
@ -31,10 +32,8 @@ ms.topic: include
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>If you want to make changes to this policy:<ol><li>Set the **Disabled Lockdown of Start Pages** policy to not configured.</li><li>Make changes to the **Configure Open Microsoft With** policy.</li><li>Enable the **Disabled Lockdown of Start Pages** policy.</li></ol>
|
||||
> [!TIP]
|
||||
> If you want to make changes to this policy:<ol><li>Set the **Disabled Lockdown of Start Pages** policy to not configured.</li><li>Make changes to the **Configure Open Microsoft With** policy.</li><li>Enable the **Disabled Lockdown of Start Pages** policy.</li></ol>
|
||||
|
||||
|
||||
### ADMX info and settings
|
||||
@ -58,11 +57,7 @@ ms.topic: include
|
||||
### Related policies
|
||||
|
||||
- [Configure Start pages](../available-policies.md#configure-start-pages): [!INCLUDE [configure-start-pages-shortdesc](../shortdesc/configure-start-pages-shortdesc.md)]
|
||||
- [Configure Start pages](../available-policies.md#configure-start-pages): [!INCLUDE [configure-start-pages-shortdesc](../shortdesc/configure-start-pages-shortdesc.md)]
|
||||
- [Disable lockdown of Start pages](../available-policies.md#disable-lockdown-of-start-pages): [!INCLUDE [disable-lockdown-of-start-pages-shortdesc](../shortdesc/disable-lockdown-of-start-pages-shortdesc.md)]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
@ -3,20 +3,21 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
<!-- ## Provision Favorites -->
|
||||
<!-- ## Provision Favorites -->
|
||||
>*Supported versions: Microsoft Edge on Windows 10, version 1511 or later*<br>
|
||||
> *Supported versions: Microsoft Edge on Windows 10, version 1511 or later*<br>
|
||||
> *Default setting: Disabled or not configured (Customizable)*
|
||||
|
||||
[!INCLUDE [provision-favorites-shortdesc](../shortdesc/provision-favorites-shortdesc.md)]
|
||||
|
||||
|
||||
|
||||
>[!IMPORTANT]
|
||||
> [!IMPORTANT]
|
||||
> Enable only this policy or the Keep favorites in sync between Internet Explorer and Microsoft Edge policy. If you enable both, Microsoft Edge prevents users from syncing their favorites between the two browsers.
|
||||
|
||||
### Supported values
|
||||
|
||||
|
@ -3,19 +3,20 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
<!-- ## Send all intranet sites to Internet Explorer 11 -->
|
||||
<!-- ## Send all intranet sites to Internet Explorer 11 -->
|
||||
>*Supported versions: Microsoft Edge on Windows 10*<br>
|
||||
> *Supported versions: Microsoft Edge on Windows 10*<br>
|
||||
> *Default setting: Disabled or not configured*
|
||||
|
||||
[!INCLUDE [send-all-intranet-sites-to-ie-shortdesc](../shortdesc/send-all-intranet-sites-to-ie-shortdesc.md)]
|
||||
|
||||
|
||||
>[!TIP]
|
||||
> [!TIP]
|
||||
> Microsoft Edge does not support ActiveX controls, Browser Helper Objects, VBScript, or other legacy technology. If you have websites or web apps that still use this technology and needs IE11 to run, you can add them to the Enterprise Mode site list, using Enterprise Mode Site List Manager.
|
||||
|
||||
|
||||
### Supported values
|
||||
|
@ -16,8 +16,8 @@ ms.date: 01/17/2020
|
||||
|
||||
# Deploy Microsoft Edge Legacy kiosk mode
|
||||
|
||||
>Applies to: Microsoft Edge Legacy (version 45 and earlier) on Windows 10, version 1809 or later
|
||||
>Professional, Enterprise, and Education
|
||||
> Applies to: Microsoft Edge Legacy (version 45 and earlier) on Windows 10, version 1809 or later
|
||||
> Professional, Enterprise, and Education
|
||||
|
||||
> [!NOTE]
|
||||
> You've reached the documentation for Microsoft Edge Legacy (version 45 and earlier.) To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/). For information about kiosk mode in the new version of Microsoft Edge, see [Microsoft Edge kiosk mode](https://docs.microsoft.com/DeployEdge/microsoft-edge-kiosk-mode).
|
||||
@ -35,7 +35,7 @@ At the end of this topic, you can find a list of [supported policies](#supported
|
||||
|
||||
## Kiosk mode configuration types
|
||||
|
||||
>**Policy** = Configure kiosk mode (ConfigureKioskMode)
|
||||
> **Policy** = Configure kiosk mode (ConfigureKioskMode)
|
||||
|
||||
Microsoft Edge Legacy kiosk mode supports four configurations types that depend on how Microsoft Edge Legacy is set up with assigned access, either as a single-app or multi-app kiosk. These configuration types help you determine what is best suited for your kiosk device or scenario.
|
||||
|
||||
@ -151,8 +151,8 @@ Windows Settings is the simplest and the only way to set up one or a couple of s
|
||||
|
||||
With this method, you can use Microsoft Intune or other MDM services to configure Microsoft Edge Legacy kiosk mode in assigned access and how it behaves on a kiosk device. To learn about a few app fundamentals and requirements before adding them to Intune, see [Add apps to Microsoft Intune](https://docs.microsoft.com/intune/apps-add).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you are using a local account as a kiosk account in Microsoft Intune, make sure to sign into this account and then sign out before configuring the kiosk device.
|
||||
> [!IMPORTANT]
|
||||
> If you are using a local account as a kiosk account in Microsoft Intune, make sure to sign into this account and then sign out before configuring the kiosk device.
|
||||
|
||||
1. In Microsoft Intune or other MDM service, configure [AssignedAccess](https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp) to prevent users from accessing the file system, running executables, or other apps.
|
||||
|
||||
@ -258,11 +258,11 @@ Make sure to check with your provider for instructions.
|
||||
In the following table, we show you the features available in both Microsoft Edge Legacy kiosk mode and Kiosk Browser app available in Microsoft Store. Both kiosk mode and kiosk browser app work in assigned access.
|
||||
|
||||
|
||||
| **Feature** | **Microsoft Edge Legacy kiosk mode** | **Microsoft Kiosk browser app** |
|
||||
| **Feature** | **Microsoft Edge Legacy kiosk mode** | **Microsoft Kiosk browser app** |
|
||||
|-----------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------:|
|
||||
| Print support |  |  |
|
||||
| Multi-tab support |  |  |
|
||||
| Allow/Block URL support |   |
|
||||
| Allow/Block URL support |  |  |
|
||||
| Configure Home Button |  |  |
|
||||
| Set Start page(s) URL |  |  <p>*Same as Home button URL* |
|
||||
| Set New Tab page URL |  |  |
|
||||
|
@ -1,12 +1,13 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 04/23/2020
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
[Microsoft browser extension policy](https://docs.microsoft.com/legal/windows/agreements/microsoft-browser-extension-policy):
|
||||
[Microsoft browser extension policy](https://docs.microsoft.com/legal/microsoft-edge/microsoft-browser-extension-policy):
|
||||
This article describes the supported mechanisms for extending or modifying the behavior or user experience of Microsoft Edge and Internet Explorer, or the content these browsers display. Techniques that aren't explicitly listed in this article are considered to be **unsupported**.
|
||||
|
@ -14,7 +14,7 @@ ms.localizationpriority: high
|
||||
|
||||
# Web Application Compatibility lab kit
|
||||
|
||||
>Updated: October, 2017
|
||||
> Updated: October, 2017
|
||||
|
||||
Upgrading web applications to modern standards is the best long-term solution to ensure compatibility with today’s web browsers, but using backward compatibility can save time and money. Internet Explorer 11 has features that can ease your browser and operating system upgrades, reducing web application testing and remediation costs. On Windows 10, you can standardize on Microsoft Edge for faster, safer browsing and fall back to Internet Explorer 11 just for sites that need backward compatibility.
|
||||
|
||||
@ -54,5 +54,5 @@ The Web Application Compatibility Lab Kit is also available in the following lan
|
||||
|
||||
[DOWNLOAD THE LAB KIT](https://www.microsoft.com/evalcenter/evaluate-windows-10-web-application-compatibility-lab)
|
||||
|
||||
>[!TIP]
|
||||
>Please use a broad bandwidth to download this content to enhance your downloading experience. Lab environment requires 8 GB of available memory and 100 GB of free disk space.
|
||||
> [!TIP]
|
||||
> Please use a broad bandwidth to download this content to enhance your downloading experience. Lab environment requires 8 GB of available memory and 100 GB of free disk space.
|
||||
|
@ -17,16 +17,16 @@ ms.author: dansimp
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
Employees assigned to the Requester role can create a change request. A change request is used to tell the Approvers and the Administrator that a website needs to be added or removed from the Enterprise Mode Site List. The employee can navigate to each stage of the process by using the workflow links provided at the top of each page of the portal.
|
||||
|
||||
>[!Important]
|
||||
>Each Requester must have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
> [!Important]
|
||||
> Each Requester must have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
**To create a new change request**
|
||||
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks **Create new request**.
|
||||
@ -70,4 +70,4 @@ Employees assigned to the Requester role can create a change request. A change r
|
||||
- **If the change is incorrect.** The Requester can rollback the change in pre-production or ask for help from the Administrator.
|
||||
|
||||
## Next steps
|
||||
After the change request is created, the Requester must make sure the suggested changes work in the pre-production environment. For these steps, see the [Verify your changes using the Enterprise Mode Site List Portal](verify-changes-preprod-enterprise-mode-portal.md) topic.
|
||||
After the change request is created, the Requester must make sure the suggested changes work in the pre-production environment. For these steps, see [Verify your changes using the Enterprise Mode Site List Portal](verify-changes-preprod-enterprise-mode-portal.md).
|
||||
|
@ -1,4 +1,5 @@
|
||||
### Enterprise Mode features
|
||||
|
||||
Enterprise Mode includes the following features:
|
||||
|
||||
- **Improved web app and website compatibility.** Through improved emulation, Enterprise Mode lets many legacy web apps run unmodified on IE11, supporting several site patterns that aren’t currently supported by existing document modes.
|
||||
@ -8,8 +9,8 @@ Download the [Enterprise Mode Site List Manager (schema v.2)](https://go.microso
|
||||
|
||||
- **Centralized control.** You can specify the websites or web apps to interpret using Enterprise Mode, through an XML file on a website or stored locally. Domains and paths within those domains can be treated differently, allowing granular control. Use Group Policy to let users turn Enterprise Mode on or off from the Tools menu and to decide whether the Enterprise browser profile appears on the Emulation tab of the F12 developer tools.
|
||||
|
||||
>[!Important]
|
||||
>All centrally-made decisions override any locally-made choices.
|
||||
> [!Important]
|
||||
> All centrally-made decisions override any locally-made choices.
|
||||
|
||||
- **Integrated browsing.** When Enterprise Mode is set up, users can browse the web normally, letting the browser change modes automatically to accommodate Enterprise Mode sites.
|
||||
|
||||
|
@ -17,14 +17,14 @@ ms.author: dansimp
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
>[!Important]
|
||||
>This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
> [!Important]
|
||||
> This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
The Requester successfully submits a change request to the Enterprise Mode Site List Portal and then gets an email, including:
|
||||
|
||||
|
@ -3,15 +3,16 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
If you need to replace your entire site list because of errors, or simply because it’s out of date, you can import your exported Enterprise Mode site list using the Enterprise Mode Site List Manager.
|
||||
|
||||
|
||||
>[!IMPORTANT]
|
||||
> [!IMPORTANT]
|
||||
> Importing your file overwrites everything that’s currently in the tool, so make sure it’s what want to do.
|
||||
|
||||
1. In the Enterprise Mode Site List Manager, click **File \> Import**.
|
||||
|
||||
|
@ -26,8 +26,8 @@ You must continue using IE11 if web apps use any of the following:
|
||||
* legacy document modes
|
||||
|
||||
If you have uninstalled IE11, you can download it from the Microsoft Store or the [Internet Explorer 11 download page](https://go.microsoft.com/fwlink/p/?linkid=290956). Alternatively, you can use Enterprise Mode with Microsoft Edge to transition only the sites that need these technologies to load in IE11.
|
||||
|
||||
>[!TIP]
|
||||
|
||||
> [!TIP]
|
||||
> If you want to use Group Policy to set Internet Explorer as your default browser, you can find the info here, [Set the default browser using Group Policy](https://go.microsoft.com/fwlink/p/?LinkId=620714).
|
||||
|
||||
|
||||
@ -38,4 +38,3 @@ If you have uninstalled IE11, you can download it from the Microsoft Store or th
|
||||
|Document modes | Starting with IE8, Internet Explorer introduced a new “document mode” with every release. These document modes could be requested via the x-ua-compatible header to put the browser into a mode which emulates legacy versions. |Similar to other modern browsers, Microsoft Edge has a single “living” document mode. To minimize the compatibility burden, we test features behind switches in about:flags until stable and ready to be turned on by default. |
|
||||
|
||||
|
||||
---
|
||||
|
@ -18,16 +18,16 @@ ms.author: dansimp
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
Employees assigned to the Requester role can create a change request. A change request is used to tell the Approvers and the Administrator that a website needs to be added or removed from the Enterprise Mode Site List. The employee can navigate to each stage of the process by using the workflow links provided at the top of each page of the portal.
|
||||
|
||||
>[!Important]
|
||||
>Each Requester must have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
> [!Important]
|
||||
> Each Requester must have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
**To create a new change request**
|
||||
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks **Create new request**.
|
||||
@ -71,4 +71,5 @@ Employees assigned to the Requester role can create a change request. A change r
|
||||
- **If the change is incorrect.** The Requester can rollback the change in pre-production or ask for help from the Administrator.
|
||||
|
||||
## Next steps
|
||||
After the change request is created, the Requester must make sure the suggested changes work in the pre-production environment. For these steps, see the [Verify your changes using the Enterprise Mode Site List Portal](verify-changes-preprod-enterprise-mode-portal.md) topic.
|
||||
|
||||
After the change request is created, the Requester must make sure the suggested changes work in the pre-production environment. For these steps, see [Verify your changes using the Enterprise Mode Site List Portal](verify-changes-preprod-enterprise-mode-portal.md).
|
||||
|
Before Width: | Height: | Size: 63 KiB After Width: | Height: | Size: 258 KiB |
@ -18,14 +18,14 @@ ms.author: dansimp
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
>[!Important]
|
||||
>This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
> [!Important]
|
||||
> This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
The Requester successfully submits a change request to the Enterprise Mode Site List Portal and then gets an email, including:
|
||||
|
||||
|
@ -20,11 +20,11 @@ ms.date: 10/25/2018
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
Internet Explorer and Microsoft Edge can work together to support your legacy web apps, while still defaulting to the higher bar for security and modern experiences enabled by Microsoft Edge. Working with multiple browsers can be difficult, particularly if you have a substantial number of internal sites. To help manage this dual-browser experience, we are introducing a new web tool specifically targeted towards larger organizations: the [Enterprise Mode Site List Portal](https://github.com/MicrosoftEdge/enterprise-mode-site-list-portal).
|
||||
|
||||
@ -33,7 +33,7 @@ If you have specific websites and apps that you know have compatibility problems
|
||||
|
||||
Using Enterprise Mode means that you can continue to use Microsoft Edge as your default browser, while also ensuring that your apps continue working on IE11.
|
||||
|
||||
>[!TIP]
|
||||
> [!TIP]
|
||||
> If you are running an earlier version of Internet Explorer, we recommend upgrading to IE11, so that any legacy apps continue to work correctly.
|
||||
|
||||
For Windows 10 and Windows 10 Mobile, Microsoft Edge is the default browser experience. However, Microsoft Edge lets you continue to use IE11 for sites that are on your corporate intranet or included on your Enterprise Mode Site List.
|
||||
@ -54,8 +54,8 @@ Download the [Enterprise Mode Site List Manager (schema v.2)](https://go.microso
|
||||
|
||||
- **Centralized control.** You can specify the websites or web apps to interpret using Enterprise Mode, through an XML file on a website or stored locally. Domains and paths within those domains can be treated differently, allowing granular control. Use Group Policy to let users turn Enterprise Mode on or off from the Tools menu and to decide whether the Enterprise browser profile appears on the Emulation tab of the F12 developer tools.
|
||||
|
||||
>[!Important]
|
||||
>All centrally-made decisions override any locally-made choices.
|
||||
> [!Important]
|
||||
> All centrally-made decisions override any locally-made choices.
|
||||
|
||||
- **Integrated browsing.** When Enterprise Mode is set up, users can browse the web normally, letting the browser change modes automatically to accommodate Enterprise Mode sites.
|
||||
|
||||
@ -121,11 +121,11 @@ There are 2 versions of this tool, both supported on Windows 7, Windows 8.1, and
|
||||
|
||||
- [Enterprise Mode Site List Manager (schema v.1)](https://www.microsoft.com/download/details.aspx?id=42501). This is an older version of the schema that you must use if you want to create and update your Enterprise Mode Site List for devices running the v.1 version of the schema.
|
||||
|
||||
We strongly recommend moving to the new schema, v.2. For more info, see [Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md).
|
||||
We strongly recommend moving to the new schema, v.2. For more info, see [Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md).
|
||||
|
||||
- [Enterprise Mode Site List Manager (schema v.2)](https://www.microsoft.com/download/details.aspx?id=49974). The updated version of the schema, including new functionality. You can use this version of the schema to create and update your Enterprise Mode Site List for devices running the v.2 version of the schema.
|
||||
|
||||
If you open a v.1 version of your Enterprise Mode Site List using this version, it will update the schema to v.2, automatically. For more info, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
|
||||
If you open a v.1 version of your Enterprise Mode Site List using this version, it will update the schema to v.2, automatically. For more info, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
|
||||
|
||||
If your list is too large to add individual sites, or if you have more than one person managing the site list, we recommend using the Enterprise Site List Portal.
|
||||
|
||||
|
@ -18,14 +18,14 @@ ms.date: 05/10/2018
|
||||
|
||||
Get answers to commonly asked questions about the Internet Explorer 11 Blocker Toolkit.
|
||||
|
||||
>[!Important]
|
||||
>If you administer your company’s environment using an update management solution, such as Windows Server Update Services (WSUS) or System Center 2012 Configuration Manager, you don’t need to use the Internet Explorer 11 Blocker Toolkit. Update management solutions let you completely manage your Windows Updates and Microsoft Updates, including your Internet Explorer 11 deployment.
|
||||
> [!Important]
|
||||
> If you administer your company’s environment using an update management solution, such as Windows Server Update Services (WSUS) or System Center 2012 Configuration Manager, you don’t need to use the Internet Explorer 11 Blocker Toolkit. Update management solutions let you completely manage your Windows Updates and Microsoft Updates, including your Internet Explorer 11 deployment.
|
||||
|
||||
- [Automatic updates delivery process](#automatic-updates-delivery-process)
|
||||
- [Automatic updates delivery process](#automatic-updates-delivery-process)
|
||||
|
||||
- [How the Internet Explorer 11 Blocker Toolkit works](#how-the-internet-explorer-11-blocker-toolkit-works)
|
||||
- [How the Internet Explorer 11 Blocker Toolkit works](#how-the-internet-explorer-11-blocker-toolkit-works)
|
||||
|
||||
- [Internet Explorer 11 Blocker Toolkit and other update services](#internet-explorer-11-blocker-toolkit-and-other-update-services)
|
||||
- [Internet Explorer 11 Blocker Toolkit and other update services](#internet-explorer-11-blocker-toolkit-and-other-update-services)
|
||||
|
||||
## Automatic Updates delivery process
|
||||
|
||||
@ -112,10 +112,10 @@ If these scenarios apply to your company, see [Internet Explorer 11 delivery thr
|
||||
|
||||
## Additional resources
|
||||
|
||||
- [Internet Explorer 11 Blocker Toolkit download](https://www.microsoft.com/download/details.aspx?id=40722)
|
||||
- [Internet Explorer 11 Blocker Toolkit download](https://www.microsoft.com/download/details.aspx?id=40722)
|
||||
|
||||
- [Internet Explorer 11 FAQ for IT pros](https://docs.microsoft.com/internet-explorer/ie11-faq/faq-for-it-pros-ie11)
|
||||
- [Internet Explorer 11 FAQ for IT pros](https://docs.microsoft.com/internet-explorer/ie11-faq/faq-for-it-pros-ie11)
|
||||
|
||||
- [Internet Explorer 11 delivery through automatic updates](../ie11-deploy-guide/ie11-delivery-through-automatic-updates.md)
|
||||
- [Internet Explorer 11 delivery through automatic updates](../ie11-deploy-guide/ie11-delivery-through-automatic-updates.md)
|
||||
|
||||
- [Internet Explorer 11 deployment guide](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/index)
|
||||
- [Internet Explorer 11 deployment guide](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/index)
|
||||
|
@ -18,8 +18,8 @@ The Internet Explorer Administration Kit (IEAK) simplifies the creation, deploym
|
||||
|
||||
Use this guide to learn about the several options and processes you'll need to consider while you're using the Internet Explorer Administration Kit 11 (IEAK 11) to customize, deploy, and manage Internet Explorer 11 for your employee's devices.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Because this content isn't intended to be a step-by-step guide, not all of the steps are necessary.
|
||||
> [!IMPORTANT]
|
||||
> Because this content isn't intended to be a step-by-step guide, not all of the steps are necessary.
|
||||
|
||||
|
||||
## Included technology
|
||||
|
@ -21,8 +21,8 @@ In addition to the Software License Terms for the Internet Explorer Administrati
|
||||
During installation, you must pick a version of IEAK 11, either **External** or **Internal**, based on your license agreement. Your version selection decides the options you can chose, the steps you follow to deploy your Internet Explorer 11 package, and how you manage the browser after deployment.
|
||||
|
||||
- **External Distribution as an Internet Service Provider (ISP), Internet Content Provider (ICP), or Developer.** If you are an ISP or an ICP, your license agreement also states that you must show the Internet Explorer logo on your packaging and promotional goods, as well as on your website.
|
||||
>[!IMPORTANT]
|
||||
>Original Equipment Manufacturers (OEMs) that install IEAK 11 as part of a Windows product, under an OEM license agreement with Microsoft, must use their appropriate Windows OEM Preinstallation document (OPD) as the guide for allowable customizations.
|
||||
> [!IMPORTANT]
|
||||
> Original Equipment Manufacturers (OEMs) that install IEAK 11 as part of a Windows product, under an OEM license agreement with Microsoft, must use their appropriate Windows OEM Preinstallation document (OPD) as the guide for allowable customizations.
|
||||
|
||||
- **Internal Distribution via a Corporate Intranet.** This version is for network admins that plan to directly deploy IE11 into a corporate environment.
|
||||
|
||||
|
@ -9,7 +9,7 @@ ms.reviewer: ramakoni, DEV_Triage
|
||||
ms.prod: internet-explorer
|
||||
ms.technology:
|
||||
ms.topic: kb-support
|
||||
ms.custom: CI=111020
|
||||
ms.custom: CI=111026
|
||||
ms.localizationpriority: Normal
|
||||
# localization_priority: medium
|
||||
# ms.translationtype: MT
|
||||
@ -71,10 +71,18 @@ The batch file offers the following options:
|
||||
|
||||
**Contents of the batch file**
|
||||
|
||||
```console
|
||||
```dos
|
||||
@echo off
|
||||
:: AxelR Test Batch
|
||||
:: tested on Windows 8 + IE10, Windows7 + IE9
|
||||
# This sample script is not supported under any Microsoft standard support program or service.
|
||||
# The sample script is provided AS IS without warranty of any kind. Microsoft further disclaims
|
||||
# all implied warranties including, without limitation, any implied warranties of merchantability
|
||||
# or of fitness for a particular purpose. The entire risk arising out of the use or performance of
|
||||
# the sample scripts and documentation remains with you. In no event shall Microsoft, its authors,
|
||||
# or anyone else involved in the creation, production, or delivery of the scripts be liable for any
|
||||
# damages whatsoever (including, without limitation, damages for loss of business profits, business
|
||||
# interruption, loss of business information, or other pecuniary loss) arising out of the use of or
|
||||
# inability to use the sample scripts or documentation, even if Microsoft has been advised of the
|
||||
# possibility of such damages
|
||||
|
||||
:home
|
||||
cls
|
||||
@ -83,55 +91,33 @@ echo Delete IE History
|
||||
echo Please select the task you wish to run.
|
||||
echo Pick one:
|
||||
echo.
|
||||
echo 1. Delete Non-trusted web History(low level hidden clean up)
|
||||
echo 2. Delete History
|
||||
echo 3. Delete Cookies
|
||||
echo 4. Delete Temporary Internet Files
|
||||
echo 5. Delete Form Data
|
||||
echo 6. Delete Stored Passwords
|
||||
echo 7. Delete All
|
||||
echo 8. Delete All "Also delete files and settings stored by add-ons"
|
||||
echo 9. Delete IE10 and 9 Temporary Internet Files
|
||||
echo 10. Reset IE Settings
|
||||
echo 77. EXIT
|
||||
echo 1. Delete History
|
||||
echo 2. Delete Cookies
|
||||
echo 3. Delete Temporary Internet Files
|
||||
echo 4. Delete Form Data
|
||||
echo 5. Delete Stored Passwords
|
||||
echo 6. Delete All
|
||||
echo 7. Delete All "Also delete files and settings stored by add-ons"
|
||||
echo 8. Delete IE10 and 9 Temporary Internet Files
|
||||
echo 9. Reset IE Settings
|
||||
echo 00. EXIT
|
||||
:choice
|
||||
Echo Hit a number [1-10] and press enter.
|
||||
set /P CH=[1-10]
|
||||
|
||||
if "%CH%"=="1" set x=del /s /q C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah
|
||||
if "%CH%"=="2" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1
|
||||
if "%CH%"=="3" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2
|
||||
if "%CH%"=="4" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
|
||||
if "%CH%"=="5" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16
|
||||
if "%CH%"=="6" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32
|
||||
if "%CH%"=="7" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255
|
||||
if "%CH%"=="8" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351
|
||||
if "%CH%"=="9" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9
|
||||
if "%CH%"=="10" set x=rundll32.exe inetcpl.cpl ResetIEtoDefaults
|
||||
if "%CH%"=="77" goto quit
|
||||
if "%CH%"=="1" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1
|
||||
if "%CH%"=="2" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2
|
||||
if "%CH%"=="3" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
|
||||
if "%CH%"=="4" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16
|
||||
if "%CH%"=="5" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32
|
||||
if "%CH%"=="6" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255
|
||||
if "%CH%"=="7" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351
|
||||
if "%CH%"=="8" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9
|
||||
if "%CH%"=="9" set x=rundll32.exe inetcpl.cpl ResetIEtoDefaults
|
||||
if "%CH%"=="00" goto quit
|
||||
|
||||
%x%
|
||||
|
||||
goto Home
|
||||
|
||||
::Temporary Internet Files > Delete files - To delete copies of web pages, images, and media
|
||||
::that are saved for faster viewing.
|
||||
::Cookies > Delete cookies - To delete cookies, which are files that are stored on your computer by
|
||||
::websites to save preferences such as login information.
|
||||
::History > Delete history - To delete the history of the websites you have visited.
|
||||
::Form data > Delete forms - To delete all the saved information that you have typed into
|
||||
::forms.
|
||||
::Passwords > Delete passwords - To delete all the passwords that are automatically filled in
|
||||
::when you log on to a website that you've previously visited.
|
||||
::Delete all - To delete all of these listed items in one operation.
|
||||
|
||||
::enter below in search/run to see Low history dir if exists
|
||||
::C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low
|
||||
|
||||
::Delete all low (untrusted history) very hidden
|
||||
::this will clean any unlocked files under the dir and not delete the dir structure
|
||||
::del /s /q low\* /ah ::del /s /q C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah
|
||||
|
||||
goto Home
|
||||
:quit
|
||||
```
|
||||
|
@ -65,7 +65,9 @@
|
||||
## [Frequently asked security questions](hololens-faq-security.md)
|
||||
## [Status of the HoloLens services](hololens-status.md)
|
||||
## [Get support](https://support.microsoft.com/supportforbusiness/productselection?sapid=3ec35c62-022f-466b-3a1e-dbbb7b9a55fb)
|
||||
## [SCEP whitepaper](scep-whitepaper.md)
|
||||
|
||||
# Resources
|
||||
## [Windows Autopilot for HoloLens 2 evaluation guide](hololens2-autopilot.md)
|
||||
|
||||
# [HoloLens release notes](hololens-release-notes.md)
|
||||
# [Give us feedback](hololens-feedback.md)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Change history for Microsoft HoloLens documentation
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
description: This topic lists new and updated topics for HoloLens.
|
||||
keywords: change history
|
||||
ms.prod: hololens
|
||||
|
@ -30,7 +30,7 @@ This article teaches you how to control HoloLens and your holographic world with
|
||||
|
||||
## Built-in voice commands
|
||||
|
||||
Get around HoloLens faster with these basic commands. In order to use these you need to enable Speech during first run of the device or in **Settings** > **Privacy** > **Speech**. You can always check whether speech is enabled by looking at the status at the top of Start menu.
|
||||
Get around HoloLens faster with these basic commands. In order to use these, you need to enable Speech during the first run of the device or in **Settings** > **Privacy** > **Speech**. You can always check whether speech is enabled by looking at the status at the top of the Start menu. For the best speech recognition results, HoloLens 2 uses the Microsoft cloud-based services. However, you can use Settings to disable this feature. To do this, in Settings, turn off **Online speech recognition**. After you change this setting, HoloLens 2 will only process voice data locally to recognize commands and dictation, and Cortana will not be available.
|
||||
|
||||
### General speech commands
|
||||
|
||||
|
@ -10,7 +10,7 @@ ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 01/26/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
---
|
||||
|
@ -10,7 +10,7 @@ ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/15/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
@ -29,7 +29,7 @@ You can manage multiple Microsoft HoloLens devices simultaneously using solution
|
||||
|
||||
## Auto-enrollment in MDM
|
||||
|
||||
If your organization uses Azure Active Directory (Azure AD) and an MDM solution that accepts an AAD token for authentication (currently, only supported in Microsoft Intune and AirWatch), your IT admin can configure Azure AD to automatically allow MDM enrollment after the user signs in with their Azure AD account. [Learn how to configure Azure AD enrollment.](https://docs.microsoft.com/intune/deploy-use/set-up-windows-device-management-with-microsoft-intune#azure-active-directory-enrollment)
|
||||
If your organization uses Azure Active Directory (Azure AD) and an MDM solution that accepts an AAD token for authentication (currently, only supported in Microsoft Intune and AirWatch), your IT admin can configure Azure AD to automatically allow MDM enrollment after the user signs in with their Azure AD account. [Learn how to configure Azure AD enrollment.](https://docs.microsoft.com/mem/intune/enrollment/windows-enroll#enable-windows-10-automatic-enrollment)
|
||||
|
||||
When auto-enrollment is enabled, no additional manual enrollment is needed. When the user signs in with an Azure AD account, the device is enrolled in MDM after completing the first-run experience.
|
||||
|
||||
|
@ -73,8 +73,6 @@ appliesto:
|
||||
1. **When a PKI cert is being generated for trusted communication, we want the cert to be generated on the device so that we know it's only on that device, unique to that device, and can't be exported or used to impersonate the device. Is this true on HoloLens? If not is there a potential mitigation?**
|
||||
1. CSR for SCEP is generated on the device itself. Intune and the on premise SCEP connector help secure the requests themselves by adding and verifying a challenge string that's sent to the client.
|
||||
1. Since HoloLens (1st Gen and 2nd Gen) have a TPM module, these certs would be stored in the TPM module, and are unable to be extracted. Additionally, even if it could be extracted, the challenge strings couldn't be verified on a different device, rendering the certs/key unusable on different devices.
|
||||
1. **SCEP is vulnerable. How does Microsoft mitigate the known vulnerabilities of SCEP?**
|
||||
1. This [SCEP Whitepaper](scep-whitepaper.md) addresses how Microsoft mitigates SCEP vulnerabilities.
|
||||
|
||||
## HoloLens 2nd Gen Security Questions
|
||||
|
||||
@ -125,5 +123,3 @@ appliesto:
|
||||
1. **When a PKI cert is being generated for trusted communication, we want the cert to be generated on the device so that we know it's only on that device, unique to that device, and can't be exported or used to impersonate the device. Is this true on HoloLens? If not is there a potential mitigation?**
|
||||
1. CSR for SCEP is generated on the device itself. Intune and the on premise SCEP connector help secure the requests themselves by adding and verifying a challenge string that's sent to the client.
|
||||
1. Since HoloLens (1st Gen and 2nd Gen) have a TPM module, these certs would be stored in the TPM module, and are unable to be extracted. Additionally, even if it could be extracted, the challenge strings couldn't be verified on a different device, rendering the certs/key unusable on different devices.
|
||||
1. **SCEP is vulnerable. How does Microsoft mitigate the known vulnerabilities of SCEP?**
|
||||
1. This [SCEP Whitepaper](scep-whitepaper.md) addresses how Microsoft mitigates SCEP vulnerabilities.
|
||||
|
@ -11,9 +11,9 @@ ms.custom:
|
||||
- CSSTroubleshooting
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
ms.date: 1/6/2020
|
||||
ms.date: 4/14/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
@ -64,7 +64,7 @@ Here's a quick summary of what's new:
|
||||
- Support for FIDO2 Security Keys to enable secure and easy authentication for shared devices
|
||||
- Seamlessly apply a provisioning package from a USB drive to your HoloLens
|
||||
- Use a provisioning packages to enroll your HoloLens to your Mobile Device Management system
|
||||
- Use Windows AutoPilot to set up and pre-configure new devices, quickly getting them ready for productive use. Send a note to hlappreview@microsoft.com to join the preview.
|
||||
- Use Windows Autopilot to set up and pre-configure new devices, quickly getting them ready for productive use. To participate in the program you'll need to meet a few requirements. While the program is in preview mode you'll need to be using Microsoft Intune. You'll need to use a tenant that is flighted for HoloLens. Lastly you'll need to have installed an insider preview buildon your HoloLens 2. To praticipate in the preview of this new program send a note to hlappreview@microsoft.com to join the preview.
|
||||
- Dark Mode - HoloLens customers can now choose the default mode for apps that support both color schemes! Based on customer feedback, with this update we are setting the default app mode to "dark," but you can easily change this setting at any time.
|
||||
- Support for additional system voice commands
|
||||
- An updated Cortana app with a focus on productivity
|
||||
@ -88,7 +88,7 @@ Provisioning packages let you set HoloLens configuration through a config file r
|
||||
1. Plug it into any freshly flashed HoloLens and press **Volume down + Power** to apply your provisioning package.
|
||||
|
||||
### System voice commands
|
||||
You can now can access these commands with your voice:
|
||||
You can now access these commands with your voice:
|
||||
- "Restart device"
|
||||
- "Shutdown device"
|
||||
- "Brightness up"
|
||||
@ -120,6 +120,19 @@ Here are some of the in-box apps that support Dark mode!
|
||||
- 3D Viewer
|
||||
- Movies & TV
|
||||
|
||||
### Windows Autopilot for HoloLens 2
|
||||
|
||||
This Autopilot program supports Autopilot self-deploying mode to provision HoloLens 2 devices as shared devices under your tenant. Self-deploying mode leverages the device's preinstalled OEM image and drivers during the provisioning process. A user can provision the device without putting the device on and going through the Out-of-the-box Experience (OOBE).
|
||||
|
||||
When a user starts the Autopilot self-deploying process, the process completes the following steps:
|
||||
1. Join the device to Azure Active Directory (Azure AD).
|
||||
2. Use Azure AD to enroll the device in Microsoft Intune (or another MDM service).
|
||||
3. Download the device-targeted policies, certificates, and networking profiles.
|
||||
4. Provision the device.
|
||||
5. Present the sign-in screen to the user.
|
||||
|
||||
For full information about Autopilot, see [Windows Autopilot for HoloLens 2 evaluation guide](hololens2-autopilot.md).
|
||||
|
||||
### FFU download and flash directions
|
||||
To test with a flight signed ffu, you first have to flight unlock your device prior to flashing the flight signed ffu.
|
||||
1. On PC
|
||||
|
@ -12,7 +12,7 @@ ms.custom:
|
||||
- CI 111456
|
||||
- CSSTroubleshooting
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
|
@ -4,7 +4,7 @@ description: This is the list of known issues that may affect HoloLens developer
|
||||
keywords: troubleshoot, known issue, help
|
||||
author: mattzmsft
|
||||
ms.author: mazeller
|
||||
ms.date: 8/30/2019
|
||||
ms.date: 4/20/2020
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- CI 111456
|
||||
@ -13,14 +13,60 @@ HoloLens and holograms: Frequently asked questions
|
||||
manager: jarrettr
|
||||
ms.prod: hololens
|
||||
appliesto:
|
||||
- HoloLens 1
|
||||
- HoloLens (1st Gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Known issues for HoloLens
|
||||
|
||||
This is the current list of known issues for HoloLens that affect developers. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future HoloLens software updates.
|
||||
This is the current list of known issues for HoloLens devices. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future HoloLens software updates.
|
||||
|
||||
## Unable to connect and deploy to HoloLens through Visual Studio
|
||||
>[!NOTE]
|
||||
> - If you discover an issue that is not blocking you please report it on your HoloLens device via [Feedback Hub](hololens-feedback.md).
|
||||
> - If the issue you are facing is blocking you, in addtion to filing feedback, please [file a support request](https://aka.ms/hlsupport).
|
||||
|
||||
- [Known issues for all HoloLens generations](#known-issues-for-all-hololens-generations)
|
||||
- [Known issues for HoloLens 2 devices](#known-issues-for-hololens-2-devices)
|
||||
- [Known issues for HoloLens (1st Gen)](#known-issues-for-hololens-1st-gen)
|
||||
- [Known issues for HoloLens emulator](#known-issues-for-hololens-emulator)
|
||||
|
||||
## Known issues for all HoloLens generations
|
||||
|
||||
### Unity
|
||||
|
||||
- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Unity recommended for HoloLens development.
|
||||
- Known issues with the Unity HoloLens Technical Preview are documented in the [HoloLens Unity forums](https://forum.unity3d.com/threads/known-issues.394627/).
|
||||
|
||||
### Windows Device Portal
|
||||
|
||||
- The Live Preview feature in Mixed Reality capture may exhibit several seconds of latency.
|
||||
- On the Virtual Input page, the Gesture and Scroll controls under the Virtual Gestures section are not functional. Using them will have no effect. The virtual keyboard on the same page works correctly.
|
||||
- After enabling Developer Mode in Settings, it may take a few seconds before the switch to turn on the Device Portal is enabled.
|
||||
|
||||
## Known issues for HoloLens 2 devices
|
||||
|
||||
### Blue screen is shown after unenrolling from Insider preview builds on a device reflashed with a Insider build
|
||||
|
||||
This is an issue affecting that affects users who are were on an Insider preview build, reflashed their HoloLens 2 with a new insider preview build, and then unenrolled from the Insider program.
|
||||
|
||||
This does not affect:
|
||||
- Users who are not enrolled in Windows Insider
|
||||
- Insiders:
|
||||
- If a device has been enrolled since Insider builds were version 18362.x
|
||||
- If they flashed a Insider signed 19041.x build AND stay enrolled in the Insider program
|
||||
|
||||
Work-around:
|
||||
- Avoid the issue
|
||||
- Flash a non-insider build. One of the regular monthly updates.
|
||||
- Stay on Insider Preview
|
||||
- Reflash the device
|
||||
1. Put the [HoloLens 2 into flashing mode](https://review.docs.microsoft.com/hololens/hololens-recovery?branch=master#hololens-2) manually by fully powering down while not connect. Then while holding Volume up, tap the Power button.
|
||||
1. Connect to the PC and open Advanced Recovery Companion.
|
||||
1. Flash the HoloLens 2 to the default build.
|
||||
|
||||
## Known issues for HoloLens (1st Gen)
|
||||
|
||||
### Unable to connect and deploy to HoloLens through Visual Studio
|
||||
|
||||
> [!NOTE]
|
||||
> Last Update: 8/8 @ 5:11PM - Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
|
||||
@ -29,7 +75,7 @@ Visual Studio has released VS 2019 Version 16.2 which includes a fix to this iss
|
||||
|
||||
Issue root-cause: Users who used Visual Studio 2015 or early releases of Visual Studio 2017 to deploy and debug applications on their HoloLens and then subsequently used the latest versions of Visual Studio 2017 or Visual Studio 2019 with the same HoloLens will be affected. The newer releases of Visual Studio deploy a new version of a component, but files from the older version are left over on the device, causing the newer version to fail. This causes the following error message: DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on \<ip\> due to error 80004005.
|
||||
|
||||
### Workaround
|
||||
#### Workaround
|
||||
|
||||
Our team is currently working on a fix. In the meantime, you can use the following steps to work around the issue and help unblock deployment and debugging:
|
||||
|
||||
@ -79,7 +125,7 @@ Our team is currently working on a fix. In the meantime, you can use the followi
|
||||
|
||||
We will provide further updates as they become available.
|
||||
|
||||
## Issues launching the Microsoft Store and apps on HoloLens
|
||||
### Issues launching the Microsoft Store and apps on HoloLens
|
||||
|
||||
> [!NOTE]
|
||||
> Last Update: 4/2 @ 10 AM - Issue resolved.
|
||||
@ -126,38 +172,27 @@ If your device is still unable to load apps, you can sideload a version of the .
|
||||
|
||||
We appreciate your patience as we have gone through the process to get this issue resolved, and we look forward to continued working with our community to create successful Mixed Reality experiences.
|
||||
|
||||
## Device Update
|
||||
### Device Update
|
||||
|
||||
- 30 seconds after a new update, the shell may disappear one time. Please perform the **bloom** gesture to resume your session.
|
||||
|
||||
## Visual Studio
|
||||
### Visual Studio
|
||||
|
||||
- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Visual Studio that is recommended for HoloLens development.
|
||||
- When deploying an app from Visual Studio to your HoloLens, you may see the error: **The requested operation cannot be performed on a file with a user-mapped section open. (Exception from HRESULT: 0x800704C8)**. If this happens, try again and your deployment will generally succeed.
|
||||
|
||||
## Emulator
|
||||
|
||||
- Not all apps in the Microsoft Store are compatible with the emulator. For example, Young Conker and Fragments are not playable on the emulator.
|
||||
- You cannot use the PC webcam in the Emulator.
|
||||
- The Live Preview feature of the Windows Device Portal does not work with the emulator. You can still capture Mixed Reality videos and images.
|
||||
|
||||
## Unity
|
||||
|
||||
- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Unity recommended for HoloLens development.
|
||||
- Known issues with the Unity HoloLens Technical Preview are documented in the [HoloLens Unity forums](https://forum.unity3d.com/threads/known-issues.394627/).
|
||||
|
||||
## Windows Device Portal
|
||||
|
||||
- The Live Preview feature in Mixed Reality capture may exhibit several seconds of latency.
|
||||
- On the Virtual Input page, the Gesture and Scroll controls under the Virtual Gestures section are not functional. Using them will have no effect. The virtual keyboard on the same page works correctly.
|
||||
- After enabling Developer Mode in Settings, it may take a few seconds before the switch to turn on the Device Portal is enabled.
|
||||
|
||||
## API
|
||||
### API
|
||||
|
||||
- If the application sets the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) behind the user or the normal to camera.forward, holograms will not appear in Mixed Reality Capture photos or videos. Until this bug is fixed in Windows, if applications actively set the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) they should ensure the plane normal is set opposite camera-forward (for example, normal = -camera.forward).
|
||||
|
||||
## Xbox Wireless Controller
|
||||
### Xbox Wireless Controller
|
||||
|
||||
- Xbox Wireless Controller S must be updated before it can be used with HoloLens. Ensure you are [up to date](https://support.xbox.com/xbox-one/accessories/update-controller-for-stereo-headset-adapter) before attempting to pair your controller with a HoloLens.
|
||||
- If you reboot your HoloLens while the Xbox Wireless Controller is connected, the controller will not automatically reconnect to HoloLens. The Guide button light will flash slowly until the controller powers off after 3 minutes. To reconnect your controller immediately, power off the controller by holding the Guide button until the light turns off. When you power your controller on again, it will reconnect to HoloLens.
|
||||
- If your HoloLens enters standby while the Xbox Wireless Controller is connected, any input on the controller will wake the HoloLens. You can prevent this by powering off your controller when you are done using it.
|
||||
|
||||
## Known issues for HoloLens emulator
|
||||
|
||||
- Not all apps in the Microsoft Store are compatible with the emulator. For example, Young Conker and Fragments are not playable on the emulator.
|
||||
- You cannot use the PC webcam in the Emulator.
|
||||
- The Live Preview feature of the Windows Device Portal does not work with the emulator. You can still capture Mixed Reality videos and images.
|
||||
|
@ -9,7 +9,7 @@ ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/16/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
|
@ -16,7 +16,7 @@ ms.custom:
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/10/2020
|
||||
ms.reviewer: Teresa-Motiv
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
|
@ -3,7 +3,7 @@ title: HoloLens release notes
|
||||
description: Learn about updates in each new HoloLens release.
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.topic: article
|
||||
@ -26,7 +26,7 @@ appliesto:
|
||||
> [!Note]
|
||||
> HoloLens Emulator Release Notes can be found [here](https://docs.microsoft.com/windows/mixed-reality/hololens-emulator-archive).
|
||||
|
||||
### Coming Soon
|
||||
### April Update - build 18362.1059
|
||||
|
||||
**Dark mode for supported apps**
|
||||
|
||||
|
248
devices/hololens/hololens2-autopilot.md
Normal file
@ -0,0 +1,248 @@
|
||||
---
|
||||
title: Windows Autopilot for HoloLens 2 evaluation guide
|
||||
description:
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.date: 4/10/2020
|
||||
ms.prod: hololens
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- CI 116283
|
||||
- CSSTroubleshooting
|
||||
audience: ITPro
|
||||
ms.localizationpriority: high
|
||||
keywords: autopilot
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Windows Autopilot for HoloLens 2 evaluation guide
|
||||
|
||||
When you set up HoloLens 2 devices for the Windows Autopilot program, your users can follow a simple process to provision the devices from the cloud.
|
||||
|
||||
This Autopilot program supports Autopilot self-deploying mode to provision HoloLens 2 devices as shared devices under your tenant. Self-deploying mode leverages the device's preinstalled OEM image and drivers during the provisioning process. A user can provision the device without putting the device on and going through the Out-of-the-box Experience (OOBE).
|
||||
|
||||

|
||||
|
||||
When a user starts the Autopilot self-deploying process, the process completes the following steps:
|
||||
|
||||
1. Join the device to Azure Active Directory (Azure AD).
|
||||
> [!NOTE]
|
||||
> Autopilot for HoloLens does not support Active Directory join or Hybrid Azure AD join.
|
||||
1. Use Azure AD to enroll the device in Microsoft Intune (or another MDM service).
|
||||
1. Download the device-targeted policies, user-targeted apps, certificates, and networking profiles.
|
||||
1. Provision the device.
|
||||
1. Present the sign-in screen to the user.
|
||||
|
||||
## Windows Autopilot for HoloLens 2: Get started
|
||||
|
||||
The following steps summarize the process of setting up your environment for the Windows Autopilot for HoloLens 2. The rest of this section provides the details of these steps.
|
||||
|
||||
1. Make sure that you meet the requirements for Windows Autopilot for HoloLens.
|
||||
1. Enroll in the Windows Autopilot for HoloLens 2 program.
|
||||
1. Verify that your tenant is flighted (enrolled to participate in the program).
|
||||
1. Register devices in Windows Autopilot.
|
||||
1. Create a device group.
|
||||
1. Create a deployment profile.
|
||||
1. Verify the ESP configuration.
|
||||
1. Configure a custom configuration profile for HoloLens devices (known issue).
|
||||
1. Verify the profile status of the HoloLens devices.
|
||||
|
||||
### 1. Make sure that you meet the requirements for Windows Autopilot for HoloLens
|
||||
For the latest information about how to participate in the program, review [Windows Insider Release Notes](hololens-insider.md#windows-insider-release-notes).
|
||||
|
||||
Review the following sections of the Windows Autopilot requirements article:
|
||||
|
||||
- [Network requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#networking-requirements)
|
||||
- [Licensing requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#licensing-requirements)
|
||||
- [Configuration requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#configuration-requirements)
|
||||
> [!IMPORTANT]
|
||||
> Unlike other Windows Autopilot programs, Windows Autopilot for HoloLens 2 has specific operating system requirements.
|
||||
|
||||
Review the "[Requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/self-deploying#requirements)" section of the Windows Autopilot Self-Deploying mode article. Your environment has to meet these requirements as well as the standard Windows Autopilot requirements.
|
||||
|
||||
> [!NOTE]
|
||||
> You do not have to review the "Step by step" and "Validation" sections of the article. The procedures later in this article provide corresponding steps that are specific to HoloLens.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> For information about how to register devices and configure profiles, see [4. Register devices in Windows Autopilot](#4-register-devices-in-windows-autopilot) and [6. Create a deployment profile](#6-create-a-deployment-profile) in this article. These sections provide steps that are specific to HoloLens.
|
||||
|
||||
Before you start the OOBE and provisioning process, make sure that the HoloLens devices meet the following requirements:
|
||||
|
||||
- The devices are not already members of Azure AD, and are not enrolled in Intune (or another MDM system). The Autopilot self-deploying process completes these steps. To make sure that all the device-related information is cleaned up, check the **Devices** pages in both Azure AD and Intune.
|
||||
- Every device can connect to the internet. You can use a wired or wireless connection.
|
||||
- Every device can connect to a computer by using a USB-C cable, and that computer has the following available:
|
||||
- Advanced Recovery Companion (ARC)
|
||||
- The latest Windows update: Windows 10, version 19041.1002.200107-0909 or a later version)
|
||||
|
||||
To configure and manage the Autopilot self-deploying mode profiles, make sure that you have access to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
|
||||
|
||||
### 2. Enroll in the Windows Autopilot for HoloLens 2 program
|
||||
|
||||
To participate in the program, you have to use a tenant that is flighted for HoloLens. To do this, go to [Windows Autopilot for HoloLens Private Preview request](https://aka.ms/APHoloLensTAP) or use the following QR code to submit a request.
|
||||
|
||||

|
||||
|
||||
In this request, provide the following information:
|
||||
|
||||
- Tenant domain
|
||||
- Tenant ID
|
||||
- Number of HoloLens 2 devices that are participating in this evaluation
|
||||
- Number of HoloLens 2 devices that you plan to deploy by using Autopilot self-deploying mode
|
||||
|
||||
### 3. Verify that your tenant is flighted
|
||||
|
||||
To verify that your tenant is flighted for the Autopilot program after you submit your request, follow these steps:
|
||||
|
||||
1. Sign in to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
|
||||
1. Select **Devices** > **Windows** > **Windows enrollment** > **Windows Autopilot deployment profiles** > **Create profile**.
|
||||
|
||||

|
||||
You should see a list that includes **HoloLens**. If this option is not present, use one of the [Feedback](#feedback) options to contact us.
|
||||
|
||||
### 4. Register devices in Windows Autopilot
|
||||
|
||||
To register a HoloLens device in the Windows Autopilot program, you have to obtain the hardware hash of the device (also known as the hardware ID). The device can record its hardware hash in a CSV file during the OOBE process, or later when a device owner starts the diagnostic log collection process (described in the following procedure). Typically, the device owner is the first user to sign in to the device.
|
||||
|
||||
**Retrieve a device hardware hash**
|
||||
|
||||
1. Start the HoloLens 2 device.
|
||||
1. On the device, press the Power and Volume Down buttons at the same time and then release them. The device collects diagnostic logs and the hardware hash, and stores them in a set of .zip files.
|
||||
1. Use a USB-C cable to connect the device to a computer.
|
||||
1. On the computer, open File Explorer. Open **This PC\\\<*HoloLens device name*>\\Internal Storage\\Documents**, and locate the AutopilotDiagnostics.zip file.
|
||||
|
||||
> [!NOTE]
|
||||
> The .zip file may not immediately be available. If the file is not ready yet you may see a HoloLensDiagnostics.temp file in the Documents folder. To update the list of files, refresh the window.
|
||||
|
||||
1. Extract the contents of the AutopilotDiagnostics.zip file.
|
||||
1. In the extracted files, locate the CSV file that has a file name prefix of "DeviceHash." Copy that file to a drive on the computer where you can access it later.
|
||||
> [!IMPORTANT]
|
||||
> The data in the CSV file should use the following header and line format:
|
||||
> ```
|
||||
> Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User <serialNumber>,<ProductID>,<hardwareHash>,<optionalGroupTag>,<optionalAssignedUser>
|
||||
>```
|
||||
|
||||
**Register the device in Windows Autopilot**
|
||||
|
||||
1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment**, and then select **Devices** > **Import** under **Windows Autopilot Deployment Program**.
|
||||
|
||||
1. Under **Add Windows Autopilot devices**, select the DeviceHash CSV file, select **Open**, and then select **Import**.
|
||||
|
||||

|
||||
1. After the import finishes, select **Devices** > **Windows** > **Windows enrollment** > **Devices** > **Sync**. The process might take a few minutes to complete, depending on how many devices are being synchronized. To see the registered device, select **Refresh**.
|
||||
|
||||

|
||||
|
||||
### 5. Create a device group
|
||||
|
||||
1. In Microsoft Endpoint Manager admin center, select **Groups** > **New group**.
|
||||
1. For **Group type**, select **Security**, and then enter a group name and description.
|
||||
1. For **Membership type**, select either **Assigned** or **Dynamic Device**.
|
||||
1. Do one of the following:
|
||||
|
||||
- If you selected **Assigned** for **Membership type** in the previous step, select **Members**, and then add Autopilot devices to the group. Autopilot devices that aren't yet enrolled are listed by using the device serial number as the device name.
|
||||
- If you selected **Dynamic Devices** for **Membership type** in the previous step, select **Dynamic device members**, and then enter code in **Advanced rule** that resembles the following:
|
||||
- If you want to create a group that includes all of your Autopilot devices, type: `(device.devicePhysicalIDs -any _ -contains "[ZTDId]")`
|
||||
- Intune's group tag field maps to the **OrderID** attribute on Azure AD devices. If you want to create a group that includes all of your Autopilot devices that have a specific group tag (the Azure AD device OrderID), you must type: `(device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881")`
|
||||
- If you want to create a group that includes all your Autopilot devices that have a specific Purchase Order ID, type: `(device.devicePhysicalIds -any _ -eq "[PurchaseOrderId]:76222342342")`
|
||||
|
||||
> [!NOTE]
|
||||
> These rules target attributes that are unique to Autopilot devices.
|
||||
1. Select **Save**, and then select **Create**.
|
||||
|
||||
### 6. Create a deployment profile
|
||||
|
||||
1. In Microsoft Endpoint Manager admin center, select **Devices** > **Windows** > **Windows enrollment** > **Windows Autopilot deployment profiles** > **Create profile** > **HoloLens**.
|
||||
1. Enter a profile name and description, and then select **Next**.
|
||||
|
||||

|
||||
1. On the **Out-of-box experience (OOBE)** page, most of the settings are pre-configured to streamline OOBE for this evaluation. Optionally, you can configure the following settings:
|
||||
|
||||
- **Language (Region)**: Select the language for OOBE. We recommend that you select a language from the list of [supported languages for HoloLens 2](hololens2-language-support.md).
|
||||
- **Automatically configure keyboard**: To make sure that the keyboard matches the selected language, select **Yes**.
|
||||
- **Apply device name template**: To automatically set the device name during OOBE, select **Yes** and then enter the template phrase and placeholders in **Enter a name** For example, enter a prefix and `%RAND:4%`—a placeholder for a four-digit random number.
|
||||
> [!NOTE]
|
||||
> If you use a device name template, the OOBE process restarts the device one additional time after it applies the device name and before it joins the device to Azure AD. This restart enables the new name to take effect.
|
||||
|
||||

|
||||
1. After you configure the settings, select **Next**.
|
||||
1. On the **Scope tags** page, optionally add the scope tags that you want to apply to this profile. For more information about scope tags, see [Use role-based access control and scope tags for distributed IT](https://docs.microsoft.com/mem/intune/fundamentals/scope-tags.md). When finished, select **Next**.
|
||||
1. On the **Assignments** page, select **Selected groups** for **Assign to**.
|
||||
1. Under **SELECTED GROUPS**, select **+ Select groups to include**.
|
||||
1. In the **Select groups to include** list, select the device group that you created for the Autopilot HoloLens devices, and then select **Next**.
|
||||
|
||||
If you want to exclude any groups, select **Select groups to exclude**, and select the groups that you want to exclude.
|
||||
|
||||

|
||||
1. On the **Review + Create** page, review the settings and then select **Create** to create the profile.
|
||||
|
||||

|
||||
|
||||
### 7. Verify the ESP configuration
|
||||
|
||||
The Enrollment Status Page (ESP) displays the status of the complete device configuration process that runs when an MDM managed user signs into a device for the first time. Make sure that your ESP configuration resembles the following, and verify that the assignments are correct.
|
||||
|
||||

|
||||
|
||||
### 8. Configure a custom configuration profile for HoloLens devices (known issue)
|
||||
|
||||
1. In [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com), select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
1. For **Platform**, specify **Windows 10 and later**, and for **Profile**, select **Custom**.
|
||||
1. Select **Create**.
|
||||
1. Enter a name for the profile, and then select **Settings** > **Configure**.
|
||||
|
||||

|
||||
1. Select **Add**, and then specify the following information:
|
||||
|
||||
- **Name**: SidecarPath
|
||||
- **OMA-URI**: ./images/Device/Vendor/MSFT/EnrollmentStatusTracking/DevicePreparation/PolicyProviders/Sidecar/InstallationState
|
||||
- **Data type**: Integer
|
||||
- **Value**: 2
|
||||
1. Select **OK** two times, and then select **Create** to create the profile.
|
||||
1. After Intune creates the configuration profile, assign the configuration profile to the device group for the HoloLens devices.
|
||||
|
||||
### 9. Verify the profile status of the HoloLens devices
|
||||
|
||||
1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment** > **Devices**.
|
||||
1. Verify that the HoloLens devices are listed, and that their profile status is **Assigned**.
|
||||
> [!NOTE]
|
||||
> It may take a few minutes for the profile to be assigned to the device.
|
||||
|
||||

|
||||
|
||||
## Windows Autopilot for HoloLens 2 User Experience
|
||||
|
||||
Your HoloLens users can follow these steps to provision HoloLens devices.
|
||||
|
||||
1. Use the USB-C cable to connect the HoloLens device to a computer that has Advanced Recovery Companion (ARC) installed and has the appropriate Windows update downloaded.
|
||||
1. Use ARC to flash the appropriate version of Windows on to the device.
|
||||
1. Connect the device to the network, and then restart the device.
|
||||
> [!IMPORTANT]
|
||||
> You must connect the device to the network before the Out-of-the-Box-Experience (OOBE) starts. The device determines whether it is provisioning as an Autopilot device while on the first OOBE screen. If the device cannot connect to the network, or if you choose not to provision the device as an Autopilot device, you cannot change to Autopilot provisioning at a later time. Instead, you would have to start this procedure over in order to provision the device as an Autopilot device.
|
||||
|
||||
The device should automatically start OOBE. Do not interact with OOBE. Instead sit, back and relax! Let HoloLens 2 detect network connectivity and allow it complete OOBE automatically. The device may restart during OOBE. The OOBE screens should resemble the following.
|
||||
|
||||

|
||||

|
||||

|
||||

|
||||
|
||||
At the end of OOBE, you can sign in to the device by using your user name and password.
|
||||
|
||||

|
||||
|
||||
## Known Issues
|
||||
|
||||
- The list of supported languages for Autopilot deployment profiles includes languages that HoloLens does not support. Select a language that [HoloLens supports](hololens2-language-support.md).
|
||||
|
||||
## Feedback
|
||||
|
||||
To provide feedback or report issues, use one of the following methods:
|
||||
|
||||
- Use the Feedback Hub app. You can find this app on a HoloLens-connected computer. In Feedback Hub, select the **Enterprise Management** > **Device** category.
|
||||
|
||||
When you provide feedback or report an issue, provide a detailed description. If applicable, include screenshots and logs.
|
||||
- Send an email message to [hlappreview@microsoft.com](mailto:hlappreview@microsoft.com). For the email subject, enter **\<*Tenant*> Autopilot for HoloLens 2 evaluation feedback** (where \<*Tenant*> is the name of your Intune tenant).
|
||||
|
||||
Provide a detailed description in your message. However, unless Support personnel specifically request it, do not include data such as screenshots or logs. Such data might include private or personally identifiable information (PII).
|
@ -3,7 +3,7 @@ title: HoloLens 2 device care and cleaning FAQ
|
||||
description:
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.date: 3/26/2020
|
||||
ms.date: 4/14/2020
|
||||
ms.prod: hololens
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
@ -69,10 +69,10 @@ To clean the brow pad, wipe it by using a cloth that's moistened by using water
|
||||
|
||||
## Can I use ultraviolet (UV) light to sanitize the device?
|
||||
|
||||
UV germicidal irradiation has not been tested on HoloLens 2.
|
||||
UV-C germicidal irradiation has not been tested on HoloLens 2.
|
||||
|
||||
> [!CAUTION]
|
||||
> High levels of UV exposure can degrade the display quality of the device and damage the visor coating. Over-exposure to UV radiation has the following effects, in order of the duration and intensity of exposure:
|
||||
> High levels of UV-A and UV-B exposure can degrade the display quality of the device and damage the visor coating. Over-exposure to UV-A and UV-B radiation has the following effects, in order of the duration and intensity of exposure:
|
||||
>
|
||||
> 1. The brow pad and device closures become discolored.
|
||||
> 1. Defects appear in the anti-reflective (AR) coating on the visor and on the sensor windows.
|
||||
|
BIN
devices/hololens/images/hololens-ap-devices-assignments.png
Normal file
After Width: | Height: | Size: 56 KiB |
BIN
devices/hololens/images/hololens-ap-devices-sync.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
devices/hololens/images/hololens-ap-enrollment-profiles.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
devices/hololens/images/hololens-ap-hash-import.png
Normal file
After Width: | Height: | Size: 115 KiB |
BIN
devices/hololens/images/hololens-ap-intro.png
Normal file
After Width: | Height: | Size: 90 KiB |
After Width: | Height: | Size: 92 KiB |
BIN
devices/hololens/images/hololens-ap-profile-name.png
Normal file
After Width: | Height: | Size: 136 KiB |
BIN
devices/hololens/images/hololens-ap-profile-oobe.png
Normal file
After Width: | Height: | Size: 78 KiB |
BIN
devices/hololens/images/hololens-ap-profile-settings-oma.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
devices/hololens/images/hololens-ap-profile-settings.png
Normal file
After Width: | Height: | Size: 86 KiB |
BIN
devices/hololens/images/hololens-ap-profile-summ.png
Normal file
After Width: | Height: | Size: 64 KiB |
BIN
devices/hololens/images/hololens-ap-qrcode.png
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
devices/hololens/images/hololens-ap-uex-1.png
Normal file
After Width: | Height: | Size: 136 KiB |
BIN
devices/hololens/images/hololens-ap-uex-2.png
Normal file
After Width: | Height: | Size: 196 KiB |
BIN
devices/hololens/images/hololens-ap-uex-3.png
Normal file
After Width: | Height: | Size: 294 KiB |
BIN
devices/hololens/images/hololens-ap-uex-4.png
Normal file
After Width: | Height: | Size: 235 KiB |
BIN
devices/hololens/images/hololens-ap-uex-5.png
Normal file
After Width: | Height: | Size: 45 KiB |
@ -1,80 +0,0 @@
|
||||
---
|
||||
title: SCEP Whitepaper
|
||||
description: A whitepaper that describes how Microsoft mitigates the vulnerabilities of SCEP.
|
||||
ms.assetid: bd55ecd1-697a-4b09-8274-48d1499fcb0b
|
||||
author: pawinfie
|
||||
ms.author: pawinfie
|
||||
ms.date: 02/12/2020
|
||||
keywords: hololens, Windows Mixed Reality, security
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.localizationpriority: high
|
||||
ms.custom:
|
||||
- CI 111456
|
||||
- CSSTroubleshooting
|
||||
appliesto:
|
||||
- HoloLens 1 (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# SCEP whitepaper
|
||||
|
||||
## High Level
|
||||
|
||||
### How the SCEP Challenge PW is secured
|
||||
|
||||
We work around the weakness of the SCEP protocol by generating custom challenges in Intune itself. The challenge string we create is signed/encrypted, and contains the information we've configured in Intune for certificate issuance into the challenge blob. This means the blob used as the challenge string contains the expected CSR information like the Subject Name, Subject Alternative Name, and other attributes.
|
||||
|
||||
We then pass that to the device and then the device generates it's CSR and passes it, and the blob to the SCEP URL it received in the MDM profile. On NDES servers running the Intune SCEP module we perform a custom challenge validation that validates the signature on the blob, decrypts the challenge blob itself, compare it to the CSR received, and then determine if we should issue the cert. If any portion of this check fails then the certificate request is rejected.
|
||||
|
||||
## Behind the scenes
|
||||
|
||||
### Intune Connector has a number of responsibilities
|
||||
|
||||
1. The connector is SCEP policy module which contains a "Certification Registration Point" component which interacts with the Intune service, and is responsible for validating, and securing the SCEP request coming into the NDES server.
|
||||
|
||||
1. The connector will install an App Pool on the NDES IIS server > Microsoft Intune CRP service Pool, and a CertificateRegistrationSvc under the "Default Web Site" on IIS.
|
||||
|
||||
1. **When the Intune NDES connector is first configured/setup on the NDES server, a certificate is issued from the Intune cloud service to the NDES server. This cert is used to securely communicate with the Intune cloud service - customer tenant. The cert is unique to the customers NDES server. Can be viewed in Certlm.msc issued by SC_Online_Issuing. This certs Public key is used by Intune in the cloud to encrypt the challenge blob. In addition, when the connector is configured, Intune's public key is sent to the NDES server.**
|
||||
>[!NOTE]
|
||||
>The connector communication with Intune is strictly outbound traffic.
|
||||
|
||||
1. The Intune cloud service combined with the Intune connector/policy module addresses the SCEP protocol challenge password weakness (in the SCEP protocol) by generating a custom challenge. The challenge is generated in Intune itself.
|
||||
|
||||
1. In the challenge blob, Intune puts information that we expect in the cert request (CSR - Certificate Signing Request) coming from a mobile device like the following: what we expect the Subject and SAN (validated against AAD attributes/properties of the user/device) to be, and specifics contained in the Intune SCEP profile that is created by an Intune admin, i.e., Request Handling, EKU, Renewal, validity period, key size, renewal period.
|
||||
>[!NOTE]
|
||||
>The Challenge blob is Encrypted with the Connectors Public Key, and Signed with Intune's (cloud service) Private Key. The device cannot decrypt the challenge
|
||||
|
||||
1. When an Intune admin creates a SCEP profile in their tenant, Intune will send the SCEP profile payload along with the Encrypted and Signed Challenge to the targeted device. The device generates a CSR, and reaches out to NDES URL (contained in the SCEP profile). The device cert request payload contains the CSR, and the encrypted, signed challenge blob.
|
||||
|
||||
1. When the device reaches out to the NDES server (via the NDES/SCEP URL provided in the SCEP Profile payload), the SCEP cert request validation is performed by the policy module running on the NDES server. The challenge signature is verified using Intune's public key (which is on the NDES server, when the connector was installed and configured) and decrypted using the connectors private key. The policy module compares the CSR details against the decrypted challenge and determines if a cert should be issued. If the CSR passes validation, the NDES server requests a certificate from the CA on behalf of the user/device.
|
||||
>[!NOTE]
|
||||
>The above process takes place on the NDES server running the Policy Module. No interaction with the Intune cloud service takes place.
|
||||
|
||||
1. The NDES connector notification/reporting of cert delivery takes place after NDES sends the issued cert to the device. This is performed as a separate operation outside the cert request flow. Meaning that once NDES sends the cert to the device via the AAD app proxy (or other publishing firewall/proxy, a log is written with the cert delivery details on the NDES server by the connector (file location \Program Files\Microsoft Intune\CertificateRequestStatus\Succeed\ folder. The connector will look here, and send updates to Intune.
|
||||
|
||||
1. The mobile device must be enrolled in Intune. If not, we reject the request as well
|
||||
|
||||
1. The Intune connector disables the standard NDES challenge password request URL on the NDES server.
|
||||
|
||||
1. The NDES server SCEP URI in most customer deployments is made available to the internet via Azure App Proxy, or an on-prem reverse proxy, i.e. F5.
|
||||
>[!NOTE]
|
||||
>The Azure App Proxy is an outbound-only connection over Port 443, from the customers onprem network where the App Proxy connector is running on a server. The AAD app proxy can also be hosted on the NDES server. No inbound ports required when using Azure App Proxy.
|
||||
|
||||
1. The mobile device talks only to the NDES URI
|
||||
|
||||
1. Side note: AAD app proxy's role is to make onprem resources (like NDES and other customer onprem web services) securely available to the internet.
|
||||
|
||||
1. The Intune connector must communicate with the Intune cloud service. The connector communication will not go through the Azure App Proxy. The connector will talk with the Intune cloud service via whatever mechanism a customer has onprem to allow outbound traffic to the internet, i.e. Internal proxy service.
|
||||
>[!NOTE]
|
||||
> if a proxy is used by the customer, no SSL packet inspection can take place for the NDES/Connector server going out.
|
||||
|
||||
1. Connector traffic with Intune cloud service consists of the following operations:
|
||||
|
||||
1. 1st time configuration of the connector: Authentication to AAD during the initial connector setup.
|
||||
|
||||
1. Connector checks in with Intune, and will process and any cert revocation transactions (i.e, if the Intune tenant admin issues a remote wipe – full or partial, also If a user unenrolls their device from Intune), reporting on issued certs, renewing the connectors' SC_Online_Issuing certificate from Intune. Also note: the NDES Intune connector has shared PKCS cert functionality (if you decide to issue PKCS/PFX based certs) so the connector checks to Intune for PKCS cert requests even though there won't be any requests to process. We are splitting that functionality out, so this connector just handles SCEP, but no ETA yet.
|
||||
|
||||
1. [Here](https://docs.microsoft.com/intune/intune-endpoints#microsoft-intune-certificate-connector) is a reference for Intune NDES connector network communications.
|
@ -3,7 +3,7 @@ title: Accessibility (Surface Hub)
|
||||
description: Accessibility settings for the Microsoft Surface Hub can be changed by using the Settings app. You'll find them under Ease of Access. Your Surface Hub has the same accessibility options as Windows 10.
|
||||
ms.assetid: 1D44723B-1162-4DF6-99A2-8A3F24443442
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Accessibility settings, Settings app, Ease of Access
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Admin group management (Surface Hub)
|
||||
description: Every Microsoft Surface Hub can be configured individually by opening the Settings app on the device.
|
||||
ms.assetid: FA67209E-B355-4333-B903-482C4A3BDCCE
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: admin group management, Settings app, configure Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: PowerShell for Surface Hub (Surface Hub)
|
||||
description: PowerShell scripts to help set up and manage your Microsoft Surface Hub.
|
||||
ms.assetid: 3EF48F63-8E4C-4D74-ACD5-461F1C653784
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: PowerShell, set up Surface Hub, manage Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Applying ActiveSync policies to device accounts (Surface Hub)
|
||||
description: The Microsoft Surface Hub's device account uses ActiveSync to sync mail and calendar. This allows people to join and start scheduled meetings from the Surface Hub, and allows them to email any whiteboards they have made during their meeting.
|
||||
ms.assetid: FAABBA74-3088-4275-B58E-EC1070F4D110
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Surface Hub, ActiveSync policies
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Change history for Surface Hub
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
description: This topic lists new and updated topics for Surface Hub.
|
||||
keywords: change history
|
||||
ms.prod: surface-hub
|
||||
|
@ -3,7 +3,7 @@ title: Change the Microsoft Surface Hub device account
|
||||
description: You can change the device account in Settings to either add an account if one was not already provisioned, or to change any properties of an account that was already provisioned.
|
||||
ms.assetid: AFC43043-3319-44BC-9310-29B1F375E672
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: change device account, change properties, Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Connect other devices and display with Surface Hub
|
||||
description: You can connect other device to your Surface Hub to display content.
|
||||
ms.assetid: 8BB80FA3-D364-4A90-B72B-65F0F0FC1F0D
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
|
@ -3,7 +3,7 @@ title: Create a device account using UI (Surface Hub)
|
||||
description: If you prefer to use a graphical user interface, you can create a device account for your Microsoft Surface Hub with either the Office 365 UI or the Exchange Admin Center.
|
||||
ms.assetid: D11BCDC4-DABA-4B9A-9ECB-58E02CC8218C
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: create device account, Office 365 UI, Exchange Admin center, Microsoft 365 admin center, Skype for Business, mobile device mailbox policy
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Create and test a device account (Surface Hub)
|
||||
description: This topic introduces how to create and test the device account that Microsoft Surface Hub uses to communicate with Microsoft Exchange and Skype.
|
||||
ms.assetid: C8605B5F-2178-4C3A-B4E0-CE32C70ECF67
|
||||
ms.reviewer: rikot
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: create and test device account, device account, Surface Hub and Microsoft Exchange, Surface Hub and Skype
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Reset or recover a Surface Hub
|
||||
description: Describes the reset and recovery processes for the Surface Hub, and provides instructions.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: reset Surface Hub, recover
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Microsoft Exchange properties (Surface Hub)
|
||||
description: Some Microsoft Exchange properties of the device account must be set to particular values to have the best meeting experience on Microsoft Surface Hub.
|
||||
ms.assetid: 3E84393B-C425-45BF-95A6-D6502BA1BF29
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Microsoft Exchange properties, device account, Surface Hub, Windows PowerShell cmdlet
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: First-run program (Surface Hub)
|
||||
description: The term \ 0034;first run \ 0034; refers to the series of steps you'll go through the first time you power up your Microsoft Surface Hub, and means the same thing as \ 0034;out-of-box experience \ 0034; (OOBE). This section will walk you through the process.
|
||||
ms.assetid: 07C9E84C-1245-4511-B3B3-75939AD57C49
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: first run, Surface Hub, out-of-box experience, OOBE
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Hybrid deployment (Surface Hub)
|
||||
description: A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub.
|
||||
ms.assetid: 7BFBB7BE-F587-422E-9CE4-C9DDF829E4F1
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: hybrid deployment, device account for Surface Hub, Exchange hosted on-prem, Exchange hosted online
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
@ -144,7 +144,7 @@ Next, you enable the device account with [Skype for Business Online](#skype-for-
|
||||
|
||||
To enable Skype for Business online, your tenant users must have Exchange mailboxes (at least one Exchange mailbox in the tenant is required). The following table explains which plans or additional services you need.
|
||||
|
||||
| Skype room system scenario | If you have Office 365 Premium, Office 365 ProPlus, or Skype for Business Standalone Plan 2, you need: | If you have an Enterprise-based plan, you need: | If you have Skype for Business Server 2015 (on-premises or hybrid), you need: |
|
||||
| Skype room system scenario | If you have Office 365 Premium, Microsoft 365 Apps for enterprise, or Skype for Business Standalone Plan 2, you need: | If you have an Enterprise-based plan, you need: | If you have Skype for Business Server 2015 (on-premises or hybrid), you need: |
|
||||
| --- | --- | --- | --- |
|
||||
| Join a scheduled meeting | Skype for Business Standalone Plan 1 | E1, 3, 4, or 5 | Skype for Business Server Standard CAL |
|
||||
| Initiate an ad-hoc meeting | Skype for Business Standalone Plan 2 | E 1, 3, 4, or 5 | Skype for Business Server Standard CAL or Enterprise CAL |
|
||||
|
@ -3,7 +3,7 @@ title: Install apps on your Microsoft Surface Hub
|
||||
description: Admins can install apps can from either the Microsoft Store or the Microsoft Store for Business.
|
||||
ms.assetid: 3885CB45-D496-4424-8533-C9E3D0EDFD94
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: install apps, Microsoft Store, Microsoft Store for Business
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/08/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Manage settings with an MDM provider (Surface Hub)
|
||||
description: Microsoft Surface Hub provides an enterprise management solution to help IT administrators manage policies and business applications on these devices using a mobile device management (MDM) solution.
|
||||
ms.assetid: 18EB8464-6E22-479D-B0C3-21C4ADD168FE
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: mobile device management, MDM, manage policies
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Manage Microsoft Surface Hub
|
||||
description: How to manage your Surface Hub after finishing the first-run program.
|
||||
ms.assetid: FDB6182C-1211-4A92-A930-6C106BCD5DC1
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: manage Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Manage Windows updates on Surface Hub
|
||||
description: You can manage Windows updates on your Microsoft Surface Hub or Surface Hub 2S by setting the maintenance window, deferring updates, or using Windows Server Update Services (WSUS).
|
||||
ms.assetid: A737BD50-2D36-4DE5-A604-55053D549045
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: manage Windows updates, Surface Hub, Windows Server Update Services, WSUS
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -6,13 +6,13 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.date: 04/24/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Miracast on existing wireless network or LAN
|
||||
# Miracast over infrastructure
|
||||
|
||||
In the Windows 10, version 1703, Microsoft has extended the ability to send a Miracast stream over a local network rather than over a direct wireless link. This functionality is based on the [Miracast over Infrastructure Connection Establishment Protocol (MS-MICE)](https://msdn.microsoft.com/library/mt796768.aspx).
|
||||
|
||||
@ -28,7 +28,12 @@ Miracast over Infrastructure offers a number of benefits:
|
||||
|
||||
## How it works
|
||||
|
||||
Users attempt to connect to a Miracast receiver as they did previously. When the list of Miracast receivers is populated, Windows 10 will identify that the receiver is capable of supporting a connection over the infrastructure. When the user selects a Miracast receiver, Windows 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). If the name is not resolvable via either DNS method, Windows 10 will fall back to establishing the Miracast session using the standard Wi-Fi direct connection.
|
||||
Users attempt to connect to a Miracast receiver through their Wi-Fi adapter as they did previously. When the list of Miracast receivers is populated, Windows 10 will identify that the receiver is capable of supporting a connection over the infrastructure. When the user selects a Miracast receiver, Windows 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). If the name is not resolvable via either DNS method, Windows 10 will fall back to establishing the Miracast session using the standard Wi-Fi direct connection.
|
||||
|
||||
> [!NOTE]
|
||||
> For more information on the connection negotiation sequence, see [Miracast over Infrastructure Connection Establishment Protocol (MS-MICE)](https://msdn.microsoft.com/library/mt796768.aspx)
|
||||
|
||||
|
||||
|
||||
|
||||
## Enabling Miracast over Infrastructure
|
||||
@ -36,14 +41,19 @@ Users attempt to connect to a Miracast receiver as they did previously. When the
|
||||
If you have a Surface Hub or other Windows 10 device that has been updated to Windows 10, version 1703, then you automatically have this new feature. To take advantage of it in your environment, you need to ensure the following is true within your deployment:
|
||||
|
||||
- The Surface Hub or device (Windows PC or phone) needs to be running Windows 10, version 1703.
|
||||
- Open TCP port: **7250**.
|
||||
- A Surface Hub or Windows PC can act as a Miracast over Infrastructure *receiver*. A Windows PC or phone can act as a Miracast over Infrastructure *source*.
|
||||
- As a Miracast receiver, the Surface Hub or device must be connected to your enterprise network via either Ethernet or a secure Wi-Fi connection (e.g. using either WPA2-PSK or WPA2-Enterprise security). If the Surface Hub or device is connected to an open Wi-Fi connection, Miracast over Infrastructure will disable itself.
|
||||
- As a Miracast source, the Windows PC or phone must be connected to the same enterprise network via Ethernet or a secure Wi-Fi connection.
|
||||
- The DNS Hostname (device name) of the Surface Hub or device needs to be resolvable via your DNS servers. You can achieve this by either allowing your Surface Hub to register automatically via Dynamic DNS, or by manually creating an A or AAAA record for the Surface Hub's hostname.
|
||||
- Windows 10 PCs must be connected to the same enterprise network via Ethernet or a secure Wi-Fi connection.
|
||||
- On Windows 10 PCs, the **Projecting to this PC** feature must be enabled within System Settings, and the device must have a Wi-Fi interface enabled in order to respond to discovery requests.
|
||||
- On Windows 10 PCs, the **Projecting to this PC** feature must be enabled in System Settings, and the device must have a Wi-Fi interface enabled in order to respond to discovery requests that only occur through the Wi-Fi adapter.
|
||||
|
||||
|
||||
It is important to note that Miracast over Infrastructure is not a replacement for standard Miracast. Instead, the functionality is complementary, and provides an advantage to users who are part of the enterprise network. Users who are guests to a particular location and don’t have access to the enterprise network will continue to connect using the Wi-Fi Direct connection method.
|
||||
|
||||
The **InBoxApps/WirelessProjection/PinRequired** setting in the [SurfaceHub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) is not required for Miracast over Infrastructure. This is because Miracast over Infrastructure only works when both devices are connected to the same enterprise network. This removes the security restriction that was previously missing from Miracast. We recommend that you continue using this setting (if you used it previously) as Miracast will fall back to regular Miracast if the infrastructure connection does not work.
|
||||
|
||||
## FAQ
|
||||
**Why do I still need Wi-Fi to use Miracast over infrastructure?**<br>
|
||||
Discovery requests to identify Miracast receivers can only occur through the Wi-Fi adapter. Once the receivers have been identified, Windows 10 can then attempt the connection to the network.
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Monitor your Microsoft Surface Hub
|
||||
description: Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS).
|
||||
ms.assetid: 1D2ED317-DFD9-423D-B525-B16C2B9D6942
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: monitor Surface Hub, Microsoft Operations Management Suite, OMS
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: On-premises deployment single forest (Surface Hub)
|
||||
description: This topic explains how you add a device account for your Microsoft Surface Hub when you have a single-forest, on-premises deployment.
|
||||
ms.assetid: 80E12195-A65B-42D1-8B84-ECC3FCBAAFC6
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: single forest deployment, on prem deployment, device account, Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -8,7 +8,7 @@ author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 08/28/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Online deployment with Office 365 (Surface Hub)
|
||||
description: This topic has instructions for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment.
|
||||
ms.assetid: D325CA68-A03F-43DF-8520-EACF7C3EDEC1
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: device account for Surface Hub, online deployment
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Password management (Surface Hub)
|
||||
description: Every Microsoft Surface Hub device account requires a password to authenticate and enable features on the device.
|
||||
ms.assetid: 0FBFB546-05F0-430E-905E-87111046E4B8
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: password, password management, password rotation, device account
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Physically install Microsoft Surface Hub
|
||||
description: The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation.
|
||||
ms.assetid: C764DBFB-429B-4B29-B4E8-D7F0073BC554
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Surface Hub, readiness guide, installation location, mounting options
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Prepare your environment for Microsoft Surface Hub
|
||||
description: This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Microsoft Surface Hub.
|
||||
ms.assetid: 336A206C-5893-413E-A270-61BFF3DF7DA9
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: prepare environment, features of Surface Hub, create and test device account, check network availability
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Create provisioning packages (Surface Hub)
|
||||
description: For Windows 10, settings that use the registry or a configuration service provider (CSP) can be configured using provisioning packages.
|
||||
ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: add certificate, provisioning package
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Save your BitLocker key (Surface Hub)
|
||||
description: Every Microsoft Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.
|
||||
ms.assetid: E11E4AB6-B13E-4ACA-BCE1-4EDC9987E4F2
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Surface Hub, BitLocker, Bitlocker recovery keys
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Set up Microsoft Surface Hub
|
||||
description: Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program.
|
||||
ms.assetid: 4D1722BC-704D-4471-BBBE-D0500B006221
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: set up instructions, Surface Hub, setup worksheet, first-run program
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Setup worksheet (Surface Hub)
|
||||
description: When you've finished pre-setup and are ready to start first-time setup for your Microsoft Surface Hub, make sure you have all the information listed in this section.
|
||||
ms.assetid: AC6F925B-BADE-48F5-8D53-8B6FFF6EE3EB
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Setup worksheet, pre-setup, first-time setup
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Top support solutions for Microsoft Surface Hub
|
||||
description: Find top solutions for common issues using Surface Hub.
|
||||
ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: Troubleshoot common problems, setup issues
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 08/28/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 08/22/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Implement Quality of Service on Surface Hub
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
description: Learn how to configure QoS on Surface Hub.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -3,7 +3,7 @@ title: Using the Surface Hub Recovery Tool
|
||||
description: How to use the Surface Hub Recovery Tool to re-image the SSD.
|
||||
ms.assetid: FDB6182C-1211-4A92-A930-6C106BCD5DC1
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
keywords: manage Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Surface Hub SSD replacement
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
description: Learn how to replace the solid state drive in a Surface Hub.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Technical information for 55" Surface Hub
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
manager: laurawi
|
||||
description: Specifications for the 55" Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
|