mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Update Windows Hello for Business configuration
This commit is contained in:
parent
e3b922aa8d
commit
b355b5ccae
@ -32,12 +32,53 @@ When you Microsoft Entra join a device, the system attempts to automatically enr
|
|||||||
|
|
||||||
Cloud-only deployments use Microsoft Entra multifactor authentication (MFA) during Windows Hello for Business enrollment, and there's no additional MFA configuration needed. If you aren't already registered in MFA, you'll be guided through the MFA registration as part of the Windows Hello for Business enrollment process.
|
Cloud-only deployments use Microsoft Entra multifactor authentication (MFA) during Windows Hello for Business enrollment, and there's no additional MFA configuration needed. If you aren't already registered in MFA, you'll be guided through the MFA registration as part of the Windows Hello for Business enrollment process.
|
||||||
|
|
||||||
Policy settings can be configured to control the behavior of Windows Hello for Business, via configuration service provider (CSP) or group policy (GPO). In cloud-only deployments, devices are typically configured via an MDM solution like Microsoft Intune, using the [PassportForWork CSP][WIN-1].
|
Policy settings can be configured to control the behavior of Windows Hello for Business, via configuration service provider (CSP) or group policy (GPO). In cloud-only deployments, devices are
|
||||||
|
typically configured via an MDM solution like Microsoft Intune, using the [PassportForWork CSP][WIN-1].
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Review the article [Configure Windows Hello for Business using Microsoft Intune](../configure.md#configure-windows-hello-for-business-using-microsoft-intune) to learn about the different options offered by Microsoft Intune to configure Windows Hello for Business.
|
||||||
|
|
||||||
|
If the Intune tenant-wide policy is configured to disable Windows Hello for Business, or if devices are deployed with Windows Hello disabled, tThere's one policy setting required to enable Windows Hello for Business in a cloud-only trust model:
|
||||||
|
|
||||||
|
- [Use Windows Hello for Business](../policy-settings.md#use-windows-hello-for-business)
|
||||||
|
|
||||||
|
Follow the instructions below to configure your devices using either Microsoft Intune or group policy (GPO).
|
||||||
|
|
||||||
|
# [:::image type="icon" source="images/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||||
|
|
||||||
|
[!INCLUDE [intune-settings-catalog-1](../../../../../includes/configure/intune-settings-catalog-1.md)]
|
||||||
|
|
||||||
|
| Category | Setting name | Value |
|
||||||
|
|--|--|--|
|
||||||
|
| **Windows Hello for Business** | Use Passport For Work | true |
|
||||||
|
|
||||||
|
[!INCLUDE [intune-settings-catalog-2](../../../../../includes/configure/intune-settings-catalog-2.md)]
|
||||||
|
|
||||||
|
Alternatively, you can configure devices using a [custom policy][MEM-1] with the [PassportForWork CSP][CSP-1].
|
||||||
|
|
||||||
|
| Setting |
|
||||||
|
|--------|
|
||||||
|
| - **OMA-URI:** `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UsePassportForWork`<br>- **Data type:** `bool`<br>- **Value:** `True`|
|
||||||
|
|
||||||
|
# [:::image type="icon" source="images/group-policy.svg"::: **GPO**](#tab/gpo)
|
||||||
|
|
||||||
|
To configure a device with group policy, use the [Local Group Policy Editor](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc731745(v=ws.10)).
|
||||||
|
|
||||||
|
| Group policy path | Group policy setting | Value |
|
||||||
|
| - | - | - |
|
||||||
|
| **Computer Configuration\Administrative Templates\Windows Components\Windows Hello for Business**<br>or<br> **User Configuration\Administrative Templates\Windows Components\Windows Hello for Business**|Use Windows Hello for Business| **Enabled**|
|
||||||
|
| **Computer Configuration\Administrative Templates\Windows Components\Windows Hello for Business** |Use a hardware security device| **Enabled**|
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> The enablement of the *Use a hardware security device* policy setting is optional, but recommended.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
> [!TIP]
|
> [!TIP]
|
||||||
> If you're using Microsoft Intune, and you're not using the [tenant-wide policy](../configure.md#verify-the-tenant-wide-policy), enable the Enrollment Status Page (ESP) to ensure that the devices receive the Windows Hello for Business policy settings before users can access their desktop. For more information about ESP, see [Set up the Enrollment Status Page][MEM-1].
|
> If you're using Microsoft Intune, and you're not using the [tenant-wide policy](../configure.md#verify-the-tenant-wide-policy), enable the Enrollment Status Page (ESP) to ensure that the devices receive the Windows Hello for Business policy settings before users can access their desktop. For more information about ESP, see [Set up the Enrollment Status Page][MEM-1].
|
||||||
|
|
||||||
For a list of settings to configure Windows Hello for Business, see [Windows Hello for Business policy settings](../policy-settings.md).
|
Additional policy settings can be configured to control the behavior of Windows Hello for Business. For more information, see [Windows Hello for Business policy settings](../policy-settings.md).
|
||||||
|
|
||||||
## Enroll in Windows Hello for Business
|
## Enroll in Windows Hello for Business
|
||||||
|
|
||||||
|
@ -58,7 +58,15 @@ For more information about how Microsoft Entra Kerberos works with Windows Hello
|
|||||||
|
|
||||||
## Configure Windows Hello for Business policy settings
|
## Configure Windows Hello for Business policy settings
|
||||||
|
|
||||||
After setting up the Microsoft Entra Kerberos object, Windows Hello for business must be enabled and configured to use the cloud Kerberos trust. Follow the instructions below to configure your devices using either Microsoft Intune or group policy (GPO).
|
After setting up the Microsoft Entra Kerberos object, Windows Hello for business must be enabled and configured to use cloud Kerberos trust. There are 2 policy settings required to configure Windows Hello for Business in a cloud Kerberos trust model:
|
||||||
|
|
||||||
|
- [Use Windows Hello for Business](../policy-settings.md#use-windows-hello-for-business)
|
||||||
|
- [use-cloud-trust-for-on-premises-authentication](../policy-settings.md#use-cloud-trust-for-on-premises-authentication)
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> If the **Use certificate for on-premises authentication** policy is enabled, certificate trust takes precedence over cloud Kerberos trust. Ensure that the machines that you want to enable cloud Kerberos trust have this policy **not configured**.
|
||||||
|
|
||||||
|
Follow the instructions below to configure your devices using either Microsoft Intune or group policy (GPO).
|
||||||
|
|
||||||
# [:::image type="icon" source="images/intune.svg"::: **Intune/CSP**](#tab/intune)
|
# [:::image type="icon" source="images/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||||
|
|
||||||
@ -83,8 +91,6 @@ Alternatively, you can configure devices using a [custom policy][MEM-1] with the
|
|||||||
| - **OMA-URI:** `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UsePassportForWork`<br>- **Data type:** `bool`<br>- **Value:** `True`|
|
| - **OMA-URI:** `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UsePassportForWork`<br>- **Data type:** `bool`<br>- **Value:** `True`|
|
||||||
| - **OMA-URI:** `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UseCloudTrustForOnPremAuth`<br>- **Data type:** `bool`<br>- **Value:** `True`|
|
| - **OMA-URI:** `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UseCloudTrustForOnPremAuth`<br>- **Data type:** `bool`<br>- **Value:** `True`|
|
||||||
|
|
||||||
For more information about the cloud Kerberos trust policy, see [Windows Hello for Business policy settings](../policy-settings.md#use-cloud-trust-for-on-premises-authentication).
|
|
||||||
|
|
||||||
# [:::image type="icon" source="images/group-policy.svg"::: **GPO**](#tab/gpo)
|
# [:::image type="icon" source="images/group-policy.svg"::: **GPO**](#tab/gpo)
|
||||||
|
|
||||||
[!INCLUDE [gpo-enable-whfb](includes/gpo-enable-whfb.md)]
|
[!INCLUDE [gpo-enable-whfb](includes/gpo-enable-whfb.md)]
|
||||||
@ -118,9 +124,6 @@ If you deploy Windows Hello for Business configuration using both Group Policy a
|
|||||||
|
|
||||||
Additional policy settings can be configured to control the behavior of Windows Hello for Business. For more information, see [Windows Hello for Business policy settings](../policy-settings.md).
|
Additional policy settings can be configured to control the behavior of Windows Hello for Business. For more information, see [Windows Hello for Business policy settings](../policy-settings.md).
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If the **Use certificate for on-premises authentication** policy is enabled, certificate trust takes precedence over cloud Kerberos trust. Ensure that the machines that you want to enable cloud Kerberos trust have this policy **not configured**.
|
|
||||||
|
|
||||||
## Enroll in Windows Hello for Business
|
## Enroll in Windows Hello for Business
|
||||||
|
|
||||||
The Windows Hello for Business provisioning process begins immediately after a user has signed in if certain prerequisite checks are passed. Windows Hello for Business *cloud Kerberos trust* adds a prerequisite check for Microsoft Entra hybrid joined devices when cloud Kerberos trust is enabled by policy.
|
The Windows Hello for Business provisioning process begins immediately after a user has signed in if certain prerequisite checks are passed. Windows Hello for Business *cloud Kerberos trust* adds a prerequisite check for Microsoft Entra hybrid joined devices when cloud Kerberos trust is enabled by policy.
|
||||||
@ -188,4 +191,3 @@ The following scenarios aren't supported using Windows Hello for Business cloud
|
|||||||
[MEM-1]: /mem/intune/configuration/custom-settings-configure
|
[MEM-1]: /mem/intune/configuration/custom-settings-configure
|
||||||
[SERV-1]: /windows-server/administration/performance-tuning/role/active-directory-server/capacity-planning-for-active-directory-domain-services
|
[SERV-1]: /windows-server/administration/performance-tuning/role/active-directory-server/capacity-planning-for-active-directory-domain-services
|
||||||
[TS-1]: /troubleshoot/windows-client/group-policy/create-and-manage-central-store
|
[TS-1]: /troubleshoot/windows-client/group-policy/create-and-manage-central-store
|
||||||
|
|
||||||
|
@ -3,8 +3,6 @@ ms.date: 01/03/2024
|
|||||||
ms.topic: include
|
ms.topic: include
|
||||||
---
|
---
|
||||||
|
|
||||||
For Microsoft Entra hybrid joined devices, you can use group policies to configure Windows Hello for Business.
|
|
||||||
|
|
||||||
The *Enable Windows Hello for Business* policy setting is the configuration needed for Windows to determine if a user should attempt to enroll for Windows Hello for Business. A user will only attempt enrollment if this policy setting is **enabled**.\
|
The *Enable Windows Hello for Business* policy setting is the configuration needed for Windows to determine if a user should attempt to enroll for Windows Hello for Business. A user will only attempt enrollment if this policy setting is **enabled**.\
|
||||||
You can configure the *Enable Windows Hello for Business* setting for computer or users:
|
You can configure the *Enable Windows Hello for Business* setting for computer or users:
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user