diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index 2038eeeae2..1385906e3f 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -15,7 +15,7 @@ metadata: author: aczechowski ms.author: aaroncz manager: aaroncz - ms.date: 08/27/2024 + ms.date: 11/05/2024 ms.localizationpriority: medium # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new @@ -34,6 +34,8 @@ landingContent: url: volume-activation/plan-for-volume-activation-client.md - text: Windows compatibility cookbook url: /windows/compatibility/ + - text: Cloud-native Windows + url: /mem/solutions/cloud-native-endpoints/cloud-native-endpoints-overview - title: Prepare linkLists: diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-end-user-exp.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-end-user-exp.md index 44b73e931e..90528e17a2 100644 --- a/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-end-user-exp.md +++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-end-user-exp.md @@ -72,4 +72,6 @@ In the following example: ## Minimize user disruption due to updates -Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. By default, [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart) are configured dynamically based on device usage patterns. Device restarts occur outside of active hours until the deadline is reached. +Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. By default, [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart) are configured dynamically based on device usage patterns. Device restarts occur outside of active hours until the deadline is reached. + +Windows Autopatch doesn't modify the existing Windows Update notifications. If you wish to modify the end-user update notification experience, see [Use CSPs and MDMs to configure Windows Update for Business](/windows/deployment/update/waas-wufb-csp-mdm). diff --git a/windows/security/identity-protection/hello-for-business/configure.md b/windows/security/identity-protection/hello-for-business/configure.md index 901fa618d2..29cb37b8e0 100644 --- a/windows/security/identity-protection/hello-for-business/configure.md +++ b/windows/security/identity-protection/hello-for-business/configure.md @@ -2,7 +2,7 @@ title: Configure Windows Hello for Business description: Learn about the configuration options for Windows Hello for Business and how to implement them in your organization. ms.topic: how-to -ms.date: 04/23/2024 +ms.date: 11/05/2024 --- # Configure Windows Hello for Business @@ -83,7 +83,7 @@ To check the Windows Hello for Business policy settings applied at enrollment ti 1. Select **Windows Hello for Business** 1. Verify the status of **Configure Windows Hello for Business** and any settings that might be configured -:::image type="content" source="deploy/images/whfb-intune-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="deploy/images/whfb-intune-disable.png"::: + :::image type="content" source="deploy/images/whfb-intune-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="deploy/images/whfb-intune-disable.png"::: ## Policy conflicts from multiple policy sources @@ -109,7 +109,7 @@ Configuration type| Details | | CSP (user)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\\UserSid\Policies`
**Key name**: `UsePassportForWork`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | | CSP (device)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\\Device\Policies`
**Key name**: `UsePassportForWork`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | | GPO (user)|**Key path**: `HKEY_USERS\\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | -| GPO (user)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | +| GPO (device)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | > [!NOTE] > If there's a conflicting device policy and user policy, the user policy takes precedence. It's not recommended to create Local GPO or registry settings that could conflict with an MDM policy. This conflict could lead to unexpected results.