From 80fbd7e2d25af8f0882f5377d4ba9bc1a7a5283d Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2019 11:57:56 -0800 Subject: [PATCH 1/2] updates - dfci - firmware --- devices/surface/surface-dock-firmware-update.md | 2 +- devices/surface/surface-manage-dfci-guide.md | 7 +++---- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/devices/surface/surface-dock-firmware-update.md b/devices/surface/surface-dock-firmware-update.md index 5a35ad30b4..8f334bb260 100644 --- a/devices/surface/surface-dock-firmware-update.md +++ b/devices/surface/surface-dock-firmware-update.md @@ -94,7 +94,7 @@ 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-). | -**Table 2. Event log IDs for Surface Dock Firmware Update** +**Table 2. Event log IDs for Surface Dock Firmware Update**
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. | Event ID | Event type | diff --git a/devices/surface/surface-manage-dfci-guide.md b/devices/surface/surface-manage-dfci-guide.md index b8d7cfccff..ce65883155 100644 --- a/devices/surface/surface-manage-dfci-guide.md +++ b/devices/surface/surface-manage-dfci-guide.md @@ -8,7 +8,7 @@ ms.sitesec: library author: dansimp ms.author: dansimp ms.topic: article -ms.date: 10/20/2019 +ms.date: 11/13/2019 ms.reviewer: jesko manager: dansimp 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) -5. On the Scope tags page, select **Next**. -6. On the Assignments page, choose **Select groups to include** and click your Azure AD security group. Select **Next**. -7. Accept the summary and then select **Create**. The Autopilot profile is now created and assigned to the group. +5. 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. ## Configure Enrollment Status Page From 27717ab693da33340cf4fa7f3d24254ef2c007a8 Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2019 12:12:15 -0800 Subject: [PATCH 2/2] Update surface-hub-2s-connect.md --- devices/surface-hub/surface-hub-2s-connect.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devices/surface-hub/surface-hub-2s-connect.md b/devices/surface-hub/surface-hub-2s-connect.md index 7a08a67098..a32df68734 100644 --- a/devices/surface-hub/surface-hub-2s-connect.md +++ b/devices/surface-hub/surface-hub-2s-connect.md @@ -9,7 +9,7 @@ ms.author: greglin manager: laurawi audience: Admin ms.topic: article -ms.date: 06/20/2019 +ms.date: 11/13/2019 ms.localizationpriority: Medium --- @@ -28,7 +28,7 @@ In general, it’s recommended to use native cable connections whenever possible | **Connection** | **Functionality** | **Description**| | --- | --- | ---| | HDMI + USB-C | HDMI-in for audio and video

USB-C for TouchBack and InkBack | USB-C supports TouchBack and InkBack with the HDMI A/V connection.

Use USB-C to USB-A to connect to legacy computers.

**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
(via compute module) | Video-in
Audio-in | Single cable needed for A/V

TouchBack and InkBack not supported

HDCP enabled | +| USB-C
(via compute module) | Video-in
Audio-in | Single cable needed for A/V

TouchBack and InkBack is supported

HDCP enabled | | HDMI (in port) | Video, Audio into Surface Hub 2S | Single cable needed for A/V

TouchBack and InkBack not supported

HDCP enabled | | MiniDP 1.2 output | Video-out such as mirroring to a larger projector. | Single cable needed for A/V |