Dear Mr. Chandrawanshi,
Thank you for reaching out regarding your deployment of Windows Hello for Business (WHfB) using Group Policy. We appreciate your initiative and are happy to provide guidance to support your implementation.
Windows Hello for Business can be deployed in two primary models:
- Key Trust (recommended for most on-premises environments)
Certificate Trust (requires a Public Key Infrastructure)
Since your Group Policy server is running on Windows Server 2022, you’re well-positioned to use the Key Trust model, which simplifies deployment and does not require issuing certificates to users.
To enable WHfB via Group Policy, please follow these steps:
- Enable Windows Hello for Business Path:
Computer Configuration > Administrative Templates > Windows Components > Windows Hello for BusinessSet Use Windows Hello for Business to Enabled - Configure PIN Complexity (Optional) Define PIN length, expiration, and history based on your security requirements.
- Enable Credential Provider Ensure that the Windows Hello for Business credential provider is not disabled.
- Allow Domain Users to Sign In Using WHfB Confirm that domain users are permitted to enroll and use WHfB.
Certificate Requirements
- Key Trust Model: No user certificates are required. Requires domain controllers running Windows Server 2016 or later with Kerberos support for WHfB.
- Certificate Trust Model: Requires a functioning Enterprise PKI (e.g., AD CS). User certificates must be issued and mapped to AD accounts.
For most organizations using Windows Server 2022, Key Trust is the preferred and simpler approach.
Let me know how it goes, and if this answer helps, feel free to hit “Accept Answer” so others can benefit too 😊
T&B, Domic Vo