deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 11:53:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #1545 from CoveMiner/surface-2s-update-vjokai

Browse Source 
Surface 2s update vjokai
This commit is contained in:
Gary Moore
2019-11-13 14:59:56 -08:00
committed by GitHub
parent ad9a8b3eae 27717ab693
commit 757a6f5347
3 changed files with 7 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
devices/surface-hub/surface-hub-2s-connect.md
View File

@ -9,7 +9,7 @@ ms.author: greglin
manager: laurawi manager: laurawi
audience: Admin audience: Admin
ms.topic: article ms.topic: article
ms.date: 06/20/2019 ms.date: 11/13/2019
ms.localizationpriority: Medium ms.localizationpriority: Medium
--- ---
@ -28,7 +28,7 @@ In general, it’s recommended to use native cable connections whenever possible
| **Connection** | **Functionality** | **Description**| | **Connection** | **Functionality** | **Description**|
| --- | --- | ---| | --- | --- | ---|
| HDMI + USB-C | HDMI-in for audio and video<br><br>USB-C for TouchBack and InkBack | USB-C supports TouchBack and InkBack with the HDMI A/V connection.<br><br>Use USB-C to USB-A to connect to legacy computers.<br><br>**NOTE:** For best results, connect HDMI before connecting a USB-C cable. If the computer you're using for HDMI is not compatible with TouchBack and InkBack, you won't need a USB-C cable. | | HDMI + USB-C | HDMI-in for audio and video<br><br>USB-C for TouchBack and InkBack | USB-C supports TouchBack and InkBack with the HDMI A/V connection.<br><br>Use USB-C to USB-A to connect to legacy computers.<br><br>**NOTE:** For best results, connect HDMI before connecting a USB-C cable. If the computer you're using for HDMI is not compatible with TouchBack and InkBack, you won't need a USB-C cable. |
| USB-C <br> (via compute module) | Video-in <br>Audio-in | Single cable needed for A/V<br><br>TouchBack and InkBack not supported<br><br>HDCP enabled | | USB-C <br> (via compute module) | Video-in <br>Audio-in | Single cable needed for A/V<br><br>TouchBack and InkBack is supported<br><br>HDCP enabled |
| HDMI (in port) | Video, Audio into Surface Hub 2S | Single cable needed for A/V<br><br>TouchBack and InkBack not supported<br><br>HDCP enabled | | HDMI (in port) | Video, Audio into Surface Hub 2S | Single cable needed for A/V<br><br>TouchBack and InkBack not supported<br><br>HDCP enabled |
| MiniDP 1.2 output | Video-out such as mirroring to a larger projector. | Single cable needed for A/V | | MiniDP 1.2 output | Video-out such as mirroring to a larger projector. | Single cable needed for A/V |

6
devices/surface/surface-dock-firmware-update.md
View File

@ -94,10 +94,8 @@ Successful completion of Surface Dock Firmware Update results in new registry ke
| Windows Device Install log | %windir%\inf\setupapi.dev.log | For more information about using Device Install Log, refer to [SetupAPI Logging](https://docs.microsoft.com/windows-hardware/drivers/install/setupapi-logging--windows-vista-and-later-). | | Windows Device Install log | %windir%\inf\setupapi.dev.log | For more information about using Device Install Log, refer to [SetupAPI Logging](https://docs.microsoft.com/windows-hardware/drivers/install/setupapi-logging--windows-vista-and-later-). |
**Table 2. Event log IDs for Surface Dock Firmware Update** **Table 2. Event log IDs for Surface Dock Firmware Update**<br>
Events are logged in the Application Event Log. Events are logged in the Application Event Log. Note: Earlier versions of this tool wrote events to Applications and Services Logs\Microsoft Surface Dock Updater.
> [!NOTE]
> Earlier versions of this tool wrote events to Applications and Services Logs\Microsoft Surface Dock Updater.
| Event ID | Event type | | Event ID | Event type |
| -------- | -------------------------------------------------------------------- | | -------- | -------------------------------------------------------------------- |

7
devices/surface/surface-manage-dfci-guide.md
View File

@ -8,7 +8,7 @@ ms.sitesec: library
author: dansimp author: dansimp
ms.author: dansimp ms.author: dansimp
ms.topic: article ms.topic: article
ms.date: 10/20/2019 ms.date: 11/13/2019
ms.reviewer: jesko ms.reviewer: jesko
manager: dansimp manager: dansimp
ms.audience: itpro ms.audience: itpro
@ -89,9 +89,8 @@ Before configuring DFCI policy settings, first create a DFCI profile and assign
![Create Autopilot profile](images/df3b.png) ![Create Autopilot profile](images/df3b.png)
5. On the Scope tags page, select **Next**. 5. On the Assignments page, choose **Select groups to include** and click your Azure AD security group. Select **Next**.
6. On the Assignments page, choose **Select groups to include** and click your Azure AD security group. Select **Next**. 6. Accept the summary and then select **Create**. The Autopilot profile is now created and assigned to the group.
7. Accept the summary and then select **Create**. The Autopilot profile is now created and assigned to the group.
## Configure Enrollment Status Page ## Configure Enrollment Status Page