From 33d3507e45bdc4ae95e99a577ae7bb0851b0c1ad Mon Sep 17 00:00:00 2001 From: magdavuko <50476079+magdavuko@users.noreply.github.com> Date: Thu, 12 Mar 2020 18:09:46 -0700 Subject: [PATCH 1/8] Update hololens-calibration.md - Corrections to the calibration description: not acceptable to close eyes (for longer period) during calibration - Adding instructions to disable calibration prompt if calibration is failing. - Added info on how many calibrations can be stored locally. --- devices/hololens/hololens-calibration.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/devices/hololens/hololens-calibration.md b/devices/hololens/hololens-calibration.md index cfc55d1070..13f5f81e72 100644 --- a/devices/hololens/hololens-calibration.md +++ b/devices/hololens/hololens-calibration.md @@ -37,7 +37,7 @@ HoloLens 2 prompts a user to calibrate the device under the following circumstan ![Calibration prompt](./images/07-et-adjust-for-your-eyes.png) -During this process, you'll look at a set of targets (gems). It's fine if you blink or close your eyes during calibration but try not to stare at other objects in the room. This allows HoloLens to learn about your eye position to render your holographic world. +During this process, you'll look at a set of targets (gems). It's fine if you blink during calibration, but try to stay focused on the gems instead of other objects in the room. This allows HoloLens to learn about your eye position to render your holographic world. ![Calibration prompt](./images/07-et-hold-head-still.png) @@ -51,7 +51,7 @@ If calibration was successful, you'll see a success screen. If not, read more a ### Calibration when sharing a device or session -Multiple users can share a HoloLens 2 device, without a need for each person to go through device setup. When a new user puts the device on their head for th first time, HoloLens 2 automatically prompts the user to calibrate visuals. When a user that has previously calibrated visuals puts the device on their head, the display seamlessly adjusts for quality and a comfortable viewing experience. +Multiple users can share a HoloLens 2 device, without a need for each person to go through device setup. When a new user puts the device on their head for the first time, HoloLens 2 automatically prompts the user to calibrate visuals. When a user that has previously calibrated visuals puts the device on their head, the display seamlessly adjusts for quality and a comfortable viewing experience. ### Manually starting the calibration process @@ -83,11 +83,12 @@ If calibration is unsuccessful try: - Moving objects in your visor out of the way (such as hair) - Turning on a light in your room or moving out of direct sunlight -If you followed all guidelines and calibration is still failing, please let us know by filing feedback in [Feedback Hub](hololens-feedback.md). +If you followed all guidelines and calibration is still failing, you can disable the calibration prompt in Settings. Please also let us know by filing feedback in [Feedback Hub](hololens-feedback.md). ### Calibration data and security Calibration information is stored locally on the device and is not associated with any account information. There is no record of who has used the device without calibration. This mean new users will get prompted to calibrate visuals when they use the device for the first time, as well as users who opted out of calibration previously or if calibration was unsuccessful. +The device can store up to 50 calibration profiles locally. After this number has been reached, the oldest unused profile will be automatically deleted. Calibration information can always be deleted from the device in **Settings** > **Privacy** > **Eye tracker**. From 35281879d345ced6a8a97728b131aec8d3d8d2a6 Mon Sep 17 00:00:00 2001 From: Mizanur Rahman <41208456+Mizanurra@users.noreply.github.com> Date: Mon, 11 May 2020 16:03:19 -0700 Subject: [PATCH 2/8] Updated licensing requirements Updated Microsoft 365 Business subscriptions to the new name Microsoft 365 Business Premium subscriptions. --- .../windows-autopilot/windows-autopilot-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-requirements.md b/windows/deployment/windows-autopilot/windows-autopilot-requirements.md index b129a7a7fb..7da78c244e 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-requirements.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-requirements.md @@ -94,7 +94,7 @@ If the Microsoft Store is not accessible, the AutoPilot process will still conti Windows Autopilot depends on specific capabilities available in Windows 10 and Azure Active Directory. It also requires an MDM service such as Microsoft Intune. These capabilities can be obtained through various editions and subscription programs: To provide needed Azure Active Directory (automatic MDM enrollment and company branding features) and MDM functionality, one of the following is required: -- [Microsoft 365 Business subscriptions](https://www.microsoft.com/microsoft-365/business) +- [Microsoft 365 Business Premium subscriptions](https://www.microsoft.com/microsoft-365/business) - [Microsoft 365 F1 subscriptions](https://www.microsoft.com/microsoft-365/enterprise/firstline) - [Microsoft 365 Academic A1, A3, or A5 subscriptions](https://www.microsoft.com/education/buy-license/microsoft365/default.aspx) - [Microsoft 365 Enterprise E3 or E5 subscriptions](https://www.microsoft.com/microsoft-365/enterprise), which include all Windows 10, Office 365, and EM+S features (Azure AD and Intune). From f5a02ab961d34139933d4a1985fe3c2c6c6e42d1 Mon Sep 17 00:00:00 2001 From: magdavuko <50476079+magdavuko@users.noreply.github.com> Date: Tue, 12 May 2020 21:57:48 -0700 Subject: [PATCH 3/8] Update devices/hololens/hololens-calibration.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- devices/hololens/hololens-calibration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-calibration.md b/devices/hololens/hololens-calibration.md index 13f5f81e72..22afb8eb13 100644 --- a/devices/hololens/hololens-calibration.md +++ b/devices/hololens/hololens-calibration.md @@ -88,7 +88,7 @@ If you followed all guidelines and calibration is still failing, you can disable ### Calibration data and security Calibration information is stored locally on the device and is not associated with any account information. There is no record of who has used the device without calibration. This mean new users will get prompted to calibrate visuals when they use the device for the first time, as well as users who opted out of calibration previously or if calibration was unsuccessful. -The device can store up to 50 calibration profiles locally. After this number has been reached, the oldest unused profile will be automatically deleted. +The device can store up to 50 calibration profiles locally. After this number has been reached, the oldest unused profile will be deleted automatically. Calibration information can always be deleted from the device in **Settings** > **Privacy** > **Eye tracker**. From 6b02e76dba358ea2b39bcafec7bd9ea487545491 Mon Sep 17 00:00:00 2001 From: Nagappan Veerappan Date: Fri, 15 May 2020 13:21:19 -0700 Subject: [PATCH 4/8] LAB repro for Multiple domains with WHFB HKT sync LAB repro for Multiple domains with WHFB HKT sync account --- .../hello-hybrid-cert-whfb-settings-dir-sync.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md index 16c17aa3f9..b9c99d4bae 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md @@ -21,7 +21,7 @@ ms.reviewer: **Applies to** - Windows 10, version 1703 or later - Hybrid deployment -- Certificate trust +- Key trust ## Directory Synchronization @@ -61,6 +61,8 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva 5. In the **Enter the object names to select** text box, type the name of the Azure AD Connect service account. Click **OK**. 6. Click **OK** to return to **Active Directory Users and Computers**. +Note: if your AD forest has multiple domains. Please make sure you add the ADConnect sync service account (ie. MSOL_12121212) into "Enterprise Key Admins" group to gain permission across the domains in the forest. + ### Section Review > [!div class="checklist"] From c6c879fd0fcd7db76c87a4bac4a99c151565b34d Mon Sep 17 00:00:00 2001 From: DanPandre <54847950+DanPandre@users.noreply.github.com> Date: Tue, 19 May 2020 08:45:41 -0400 Subject: [PATCH 5/8] 2S firmware version update SMC firmware was re-released --- devices/surface-hub/surface-hub-update-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface-hub/surface-hub-update-history.md b/devices/surface-hub/surface-hub-update-history.md index f4616cd18b..673c77e71c 100644 --- a/devices/surface-hub/surface-hub-update-history.md +++ b/devices/surface-hub/surface-hub-update-history.md @@ -37,7 +37,7 @@ This update is specific to the Surface Hub 2S and provides the driver and firmwa * Improves system stability. * Surface System driver - 1.7.139.0 * Improves system stability. -* Surface SMC Firmware update - 1.173.139.0 +* Surface SMC Firmware update - 1.176.139.0 * Improves system stability. From 3cd790f41552b3c215ea08d2bf07813d915425cd Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Tue, 19 May 2020 14:09:54 -0700 Subject: [PATCH 6/8] Update devices/hololens/hololens-calibration.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- devices/hololens/hololens-calibration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/devices/hololens/hololens-calibration.md b/devices/hololens/hololens-calibration.md index 22afb8eb13..29021789a2 100644 --- a/devices/hololens/hololens-calibration.md +++ b/devices/hololens/hololens-calibration.md @@ -88,7 +88,8 @@ If you followed all guidelines and calibration is still failing, you can disable ### Calibration data and security Calibration information is stored locally on the device and is not associated with any account information. There is no record of who has used the device without calibration. This mean new users will get prompted to calibrate visuals when they use the device for the first time, as well as users who opted out of calibration previously or if calibration was unsuccessful. -The device can store up to 50 calibration profiles locally. After this number has been reached, the oldest unused profile will be deleted automatically. + +The device can locally store up to 50 calibration profiles. After this number is reached, the device automatically deletes the oldest unused profile. Calibration information can always be deleted from the device in **Settings** > **Privacy** > **Eye tracker**. From 083e35c01c2020403ec97aa952b0880ac32fb2c1 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 19 May 2020 16:31:49 -0700 Subject: [PATCH 7/8] Fixes for grammar and note style --- .../hello-hybrid-cert-whfb-settings-dir-sync.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md index b9c99d4bae..828a386e51 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md @@ -61,7 +61,8 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva 5. In the **Enter the object names to select** text box, type the name of the Azure AD Connect service account. Click **OK**. 6. Click **OK** to return to **Active Directory Users and Computers**. -Note: if your AD forest has multiple domains. Please make sure you add the ADConnect sync service account (ie. MSOL_12121212) into "Enterprise Key Admins" group to gain permission across the domains in the forest. +> [!NOTE] +> If your AD forest has multiple domains. Please make sure you add the ADConnect sync service account (that is, MSOL_12121212) into "Enterprise Key Admins" group to gain permission across the domains in the forest. ### Section Review From 686137bce175afb740d05ffeef1dd200083831cf Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 19 May 2020 16:32:47 -0700 Subject: [PATCH 8/8] Another grammar fix --- .../hello-hybrid-cert-whfb-settings-dir-sync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md index 828a386e51..0aa43d1982 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-dir-sync.md @@ -28,7 +28,7 @@ ms.reviewer: In hybrid deployments, users register the public portion of their Windows Hello for Business credential with Azure. Azure AD Connect synchronizes the Windows Hello for Business public key to Active Directory. -The key-trust model needs Windows Server 2016 domain controllers, which configures the key registration permissions automatically; however, the certificate-trust model does not and requires you to add the permissions manually. +The key-trust model needs Windows Server 2016 domain controllers, which configure the key registration permissions automatically; however, the certificate-trust model does not and requires you to add the permissions manually. > [!IMPORTANT] > If you already have a Windows Server 2016 domain controller in your domain, you can skip **Configure Permissions for Key Synchronization**. In this case, you should use the pre-created group KeyAdmins in step 3 of the "Group Memberships for the Azure AD Connect Service Account" section of this article.