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

Screenshots for UEFI and changes in checklist

devices/surface-hub/TOC.md

@@ -33,7 +33,7 @@
 ### [Managing Surface Hub 2S with Microsoft Intune](surface-hub-2s-manage-intune.md)
 ### [Local management for Surface Hub 2S settings](local-management-surface-hub-settings.md)
 ### [Manage device account password rotation](surface-hub-2s-manage-passwords.md)
-### [Servicing and updating for Surface Hub 2S](surface-hub-2s-service-update.md)
+### [Manage Windows updates](manage-windows-updates-for-surface-hub.md)
 ### [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
 ### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
 ### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)

devices/surface-hub/surface-hub-2s-deploy-checklist.md

@@ -15,49 +15,49 @@ ms.localizationpriority: Normal
 
 ## Surface Hub 2S pre-deployment checklist
 
-|**Check**|**Item**|**Response**|**Learn more**|
-|:------ |:------ |:----- |:------ |
-| ☐ |**Device account name**| | |
-| ☐ |**Device account UPN**| | |
-| ☐ |**ActiveSync Policy**| | |
-| ☐ |**Calendar processing configuration completed**| - Yes <br> - No | |
-| ☐ |**Device-friendly name**| | |
-| ☐ |**Device host name**| | |
-| ☐ |**Affiliation**| - None <br> - Active Directory affiliation <br> - Azure Active Directory | |
-| ☐ |**Microsoft Teams Mode**| - Mode 0 <br> - Mode 1 <br> - Mode 2 | |
-| ☐ |**Device Management**| - Yes, Microsoft Intune <br> - Yes, other mobile device manager [MDM] <br> - None |  |
-| ☐ |**Proxy**| - Automatic configuration <br> - Proxy server <br> - Proxy auto-config (PAC) file | |
-| ☐ |**Proxy authentication**| - Device account credentials <br> - Prompt for credentials | |
-| ☐ |**Password rotation**| - On <br> - Off | |
-| ☐ |**Skype for Business additional domain names (on-premises only)**| | |
-| ☐ |**Session timeout time**| | |
-| ☐ |**Session timeout action**| - End session <br> - Allow resume | |
-| ☐ |**My meetings and files**| - Enabled <br> - Disabled | |
-| ☐ |**Lock screen timeout**| | |
-| ☐ |**Sleep idle timeout**| | |
-| ☐ |**Bluetooth**| - On <br> - Off | |
-| ☐ |**Use only BitLocker USB drives**| - On <br> - Off | |
-| ☐ |**Install additional certificates (on-premises only)**| | [Using certificates for AADJ on-premises single-sign on](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-cert) |
-|☐ |**Windows update**| - Windows Update for Business <br> - Windows Server Update Services [WSUS] | [Deploy updates using Windows Update for Business](https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb) <br> [Get Started with Windows Server Update Services (WSUS)](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) |
-|☐ |**Surface app speaker setting**| - Rolling stand <br> - Wall-mounted | |
-|☐ |**IP Address**| - Wired — DHCP <br> - Wired — DHCP reservation <br> - Wireless — DHCP <br> - Wireless — DHCP reservation | |
+|**Item**|**Response**|**Learn more**|
+|:------ |:------ |:----- |
+|**Device account name**| | |
+|**Device account UPN**| | |
+|**ActiveSync Policy**| | |
+|**Calendar processing configuration completed**| ☐ Yes <br>  ☐ No | |
+|**Device-friendly name**| | |
+|**Device host name**| | |
+|**Affiliation**| ☐ None <br> ☐ Active Directory affiliation <br> ☐ Azure Active Directory | |
+|**Microsoft Teams Mode**| ☐ Mode 0 <br> ☐ Mode 1 <br> ☐ Mode 2 | |
+|**Device Management**| ☐ Yes, Microsoft Intune <br> ☐ Yes, other mobile device manager [MDM] <br> ☐ None |  |
+|**Proxy**| ☐ Automatic configuration <br> ☐ Proxy server <br> ☐ Proxy auto-config (PAC) file | |
+|**Proxy authentication**| ☐ Device account credentials <br> ☐ Prompt for credentials | |
+|**Password rotation**| ☐ On <br> ☐ Off | |
+|**Skype for Business additional domain names (on-premises only)**| | |
+|**Session timeout time**| | |
+|**Session timeout action**| ☐ End session <br> ☐ Allow resume | |
+|**My meetings and files**| ☐ Enabled <br> ☐ Disabled | |
+|**Lock screen timeout**| | |
+|**Sleep idle timeout**| | |
+|**Bluetooth**| ☐ On <br> ☐ Off | |
+|**Use only BitLocker USB drives**| ☐ On <br> ☐ Off | |
+|**Install additional certificates (on-premises only)**| | [Using certificates for AADJ on-premises single-sign on](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-cert) |
+|**Windows update**| ☐ Windows Update for Business <br> ☐ Windows Server Update Services [WSUS] | [Deploy updates using Windows Update for Business](https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb) <br> [Get Started with Windows Server Update Services (WSUS)](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) |
+|**Surface app speaker setting**| ☐ Rolling stand <br> ☐ Wall-mounted | |
+|**IP Address**| ☐ Wired — DHCP <br> ☐ Wired — DHCP reservation <br> ☐ Wireless — DHCP <br> ☐ Wireless — DHCP reservation | |
 
 ## Surface Hub 2S post-deployment checklist
 
 |**Check**|**Item**|**Response**|**Learn more**|
 |:------|:-------|:---------|:----------|
-| ☐ |**Device account syncing**| - Yes <br> - No | |
-| ☐ |**Bitlocker key**| - Saved to file (no affiliation) <br> - Saved in Active Directory (AD affiliation) <br>- Saved in Azure AD (Azure AD affiliation) | |
-| ☐ |**Device OS updates**| - Completed | |
-| ☐ |**Windows Store updates**| - Automatic <br> - Manual | |
-| ☐ |**Microsoft Teams scheduled meeting**| - Confirmation email received <br> - Meeting appears on start screen <br> - One-touch join functions <br> - Able to join audio <br> - Able to join video <br> - Able to share screen ||
-| ☐ |**Skype for Business scheduled meeting**| - Confirmation email received <br> - Meeting appears on start screen <br> - One-touch join functions correctly <br> - Able to join audio <br> - Able to join video <br> - Able to share screen <br> - Able to send/receive IM | |
-| ☐ |**Scheduled meeting when already invited**| - Meeting declined | |
-| ☐ |**Microsoft Teams ad-hoc meeting**| - Invite other users work <br> - Able to join audio <br> - Able to join video <br> - Able to share screen | |
-| ☐ |**Skype for Business scheduled meeting**| - Invite other users work <br> - Able to join audio <br> - Able to join video <br> - Able to share screen <br> - Able to send/receive IM | |
-| ☐ |**Microsoft Whiteboard**| - Launch from Welcome / Start screen <br> - Launch from Microsoft Teams | [Microsoft Whiteboard](https://whiteboard.microsoft.com/) |
-| ☐ |**Incoming Skype/Teams call**| - Able to join audio<br>- Able to join video <br> - Able to share screen <br> - Able to send/receive IM (Skype for Business only) | |
-| ☐ |**Incoming live video streams**| - Maximum 2 (Skype for Business) <br> - Maximum 4 (Microsoft Teams) | |
-| ☐ |**Microsoft Teams Mode 0 behavior**| - Skype for Business tile on Welcome/Start screen <br> - Can join scheduled Skype for Business meetings (Skype UI) <br> - Can join scheduled Teams meetings (Teams UI) | |
-| ☐ |**Microsoft Teams Mode 1 behavior**| - Teams tile on Welcome/Start screen <br> - Can join scheduled Skype for Business meetings (Skype UI) <br> - Can join scheduled Teams meetings (Teams UI) | |
-| ☐ |**Microsoft Teams Mode 2 behavior**| - Teams tile on Welcome / Start screen <br> - Can join scheduled Teams meetings <br> - Fail to join Skype for Business meetings | |
+|**Device account syncing**| ☐ Yes <br> ☐ No | |
+|**Bitlocker key**| ☐ Saved to file (no affiliation) <br> ☐ Saved in Active Directory (AD affiliation) <br>☐ Saved in Azure AD (Azure AD affiliation) | |
+|**Device OS updates**| ☐ Completed | |
+|**Windows Store updates**| ☐ Automatic <br> ☐ Manual | |
+|**Microsoft Teams scheduled meeting**| ☐ Confirmation email received <br> ☐ Meeting appears on start screen <br>  ☐ One-touch join functions <br> ☐ Able to join audio <br> ☐ Able to join video <br> ☐ Able to share screen ||
+|**Skype for Business scheduled meeting**| ☐ Confirmation email received <br> ☐ Meeting appears on start screen <br> ☐ One-touch join functions correctly <br> ☐ Able to join audio <br> ☐ Able to join video <br> ☐ Able to share screen <br> ☐ Able to send/receive IM | |
+|**Scheduled meeting when already invited**| ☐ Meeting declined | |
+|**Microsoft Teams ad-hoc meeting**| ☐ Invite other users work <br> ☐ Able to join audio <br> ☐ Able to join video <br> ☐ Able to share screen | |
+|**Skype for Business scheduled meeting**| ☐ Invite other users work <br> ☐ Able to join audio <br> ☐ Able to join video <br> ☐ Able to share screen <br> ☐ Able to send/receive IM | |
+|**Microsoft Whiteboard**| ☐ Launch from Welcome / Start screen <br> ☐ Launch from Microsoft Teams | [Microsoft Whiteboard](https://whiteboard.microsoft.com/) |
+|**Incoming Skype/Teams call**| ☐ Able to join audio<br>☐ Able to join video <br> ☐ Able to share screen <br> ☐ Able to send/receive IM (Skype for Business only) | |
+|**Incoming live video streams**| ☐ Maximum 2 (Skype for Business) <br> ☐ Maximum 4 (Microsoft Teams) | |
+|**Microsoft Teams Mode 0 behavior**| ☐ Skype for Business tile on Welcome/Start screen <br> ☐ Can join scheduled Skype for Business meetings (Skype UI) <br> ☐ Can join scheduled Teams meetings (Teams UI) | |
+|**Microsoft Teams Mode 1 behavior**| ☐ Teams tile on Welcome/Start screen <br> ☐ Can join scheduled Skype for Business meetings (Skype UI) <br> ☐ Can join scheduled Teams meetings (Teams UI) | |
+|**Microsoft Teams Mode 2 behavior**| ☐ Teams tile on Welcome / Start screen <br> ☐ Can join scheduled Teams meetings <br> ☐ Fail to join Skype for Business meetings | |

devices/surface-hub/surface-hub-2s-phone-authenticate.md

@@ -1,6 +1,6 @@
 ---
-title: "Configure phone authentication for Surface Hub 2S"
-description: "Learn how to simplify signing in to Surface Hub 2S using phone authentication."
+title: "Configure Easy Authentication for Surface Hub 2S"
+description: "Learn how to simplify signing in to Surface Hub 2S using Easy Authentication on your mobile device."
 keywords: separate values with commas
 ms.prod: surface-hub
 ms.sitesec: library

devices/surface-hub/surface-hub-2s-secure-with-uefi-semm.md

@@ -42,16 +42,24 @@ Unlike other Surface devices, you cannot use an MSI file or a Win PE image to ap
 
 ## To configure UEFI on Surface Hub 2S
 
-1. Start the UEFI Configurator and on the first screen, choose **Configuration Package**.
-2. To add the certificate to your package, you must have a valid certificate with the private key in a .pfx file format to sign and protect the package. Select **+ Certificate Protection.**
-3. Enter the certificate’s private key’s password.
-4. After importing the private key, continue creating the package.
-5. Choose **Hub** and **Surface Hub 2S** as the target for the UEFI configuration package.
-6. Choose the components and settings you want to activate or deactivate on Surface Hub 2S.
-7. Use the USB option to export the file.
-8. Insert and choose the USB drive you’d like to use for this package. The USB drive will be formatted and you lose any information you have on it.
-
-Upon successful creation of the package, the Configurator will display the last two characters of your certificate’s thumbprint. You need these characters when you import to the configuration to Surface Hub 2S.
+1. Start the UEFI Configurator and on the first screen, choose **Configuration Package**.<br><br>
+![* Start the UEFI Configurator and choose Configuration Package*](images/sh2-uefi1.png) <br> <br>
+2. To add the certificate to your package, you must have a valid certificate with the private key in a .pfx file format to sign and protect the package. Select **+ Certificate Protection.** <br>
+![* Select + Certificate Protection *](images/sh2-uefi2.png) <br><br>
+3. Enter the certificate’s private key’s password.<br>
+![* Enter the certificate’s private key’s password *](images/sh2-uefi3.png) <br><br>
+4. After importing the private key, continue creating the package.<br>
+![* Continue creating the package *](images/sh2-uefi4.png) <br><br>
+5. Choose **Hub** and **Surface Hub 2S** as the target for the UEFI configuration package.<br>
+![* Choose Hub and Surface Hub 2S as the target for the UEFI configuration package *](images/sh2-uefi5.png) <br><br>
+6. Choose the components and settings you want to activate or deactivate on Surface Hub 2S.<br>
+![* Choose the components and settings you want to activate or deactivate *](images/sh2-uefi6.png) <br><br>
+7. Use the USB option to export the file.<br>
+![* Use the USB option to export the file *](images/sh2-uefi8.png) <br><br>
+8. Insert and choose the USB drive you’d like to use for this package. The USB drive will be formatted and you lose any information you have on it.<br>
+![* Insert and choose the USB drive for your package  *](images/sh2-uefi9.png) <br><br>
+9. Upon successful creation of the package, the Configurator will display the last two characters of your certificate’s thumbprint. You need these characters when you import to the configuration to Surface Hub 2S.<br>
+![* Successful configuration of package *](images/sh2-uefi10.png) <br>
 
 ## To boot into UEFI
 

devices/surface/maintain-optimal-power-settings-on-Surface-devices.md

@@ -1,5 +1,5 @@
 ---
-title: Maintain optimal power settings 
+title: Best practice power settings for Surface devices
 description: This topic provides best practice recommendations for maintaining optimal power settings and explains how Surface streamlines the power management experience. 
 ms.prod: w10
 ms.mktglfcycl: manage
@@ -12,7 +12,7 @@ ms.reviewer:
 manager: dansimp
 ---
 
-# Maintain optimal power settings on Surface devices
+# Best practice power settings for Surface devices
 
 Surface devices are designed to take advantage of the latest advances in
 mobile device energy consumption to deliver a streamlined experience
@@ -22,9 +22,20 @@ components, momentarily waking up system components to handle background
 tasks -- such as an incoming email or network traffic -- before returning to a
 low power idle state (S0ix).
 
+## Summary of recommendations for IT administrators
+
+To ensure Surface devices across your organization fully benefit from Surface power optimization features:
+
+- Exclude Surface devices from any existing power management policy settings and let the Surface default policy control the power policy and behavior of the device.
+- If you must manage the power profile of devices across your network (such as in highly managed organizations), use the powercfg command tool to export the power profile from the factory image of the Surface device and then import it into the provisioning package for your Surface devices. For more information, refer to [Configure power settings](https://docs.microsoft.com/windows-hardware/customize/power-settings/configure-power-settings).
+- Always use the newest available version of the drivers and firmware for your devices and for the version of Windows 10 they're running. For more information, refer to [Deploying the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
+- Avoid creating custom power profiles or adjusting advanced power settings not visible in the default UI  (**System** > **Power & sleep**). For more information, refer to User best practices for extended battery life in this document.
+
+## Background
+
 The way Surface implements power management differs significantly from
 the earlier OS standard that gradually reduces and turns off power via a
-series of sleep states (S1, S2, S3).
+series of sleep states; for example, cycling through S1, S2, S3, and so on.
 
 Instead, Surface is imaged with a custom power profile that replaces
 legacy sleep and energy consumption functionality with modern standby
@@ -36,6 +47,11 @@ works in conjunction with Windows power manager to allocate or throttle
 only the exact amount of power required for hardware components to
 function.
 
+## Utilizing the custom power profile in Surface
+
+If you go into the power options on a  surface device, you'll see that there's a single power plan available. This is the custom power profile. And if you go to the advanced power settings, you’ll see a much smaller subset of power options compared to a generic PC running Windows 10. Unlike generic devices, Surface has firmware and custom components to manage these power options.
+
+
 ## Modern Standby
 
 The algorithmically embedded custom power profile enables modern standby
@@ -78,6 +94,7 @@ experience by delivering a single power plan (balanced) that replaces
 the multiple power plans from standard Windows builds.
 
 ### Simplified power settings user interface
+
 Surface provides a simplified UI in accord with best practice power
 setting recommendations. In general, it's recommended to only adjust settings visible in the default user interface and avoid configuring advanced power settings or Group Policy settings. Using the default screen and sleep timeouts while avoiding maximum
 brightness levels are the most effective ways for users to maintain
@@ -145,13 +162,14 @@ To learn more, see:
 
 # Learn more 
 
--   [Modern
+- [Modern
     standby](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby-wake-sources)
 
 <!-- -->
 
--   [Customize the Windows performance power
+- [Customize the Windows performance power
     slider](https://docs.microsoft.com/windows-hardware/customize/desktop/customize-power-slider)
 
--   [Battery
+- [Battery
     saver](https://docs.microsoft.com/windows-hardware/design/component-guidelines/battery-saver)
+- [Deploying the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)