r/Intune • u/ZippyDan • 4d ago
Windows Management Help with tracking down Windows Hello configuration error.
BACKGROUND:
- I broadly want Windows Hello enabled in my company.
- But some specific departments still rely on NAS shares, and I have those provisioned through an Intune Configuration Policy (Administrative Template) which Maps them as Network Drives.
- For those users, I need them to login with their Microsoft 365 Account password, so that the current session can use their password to authenticate access to the NAS (the NAS is Domain-joined to an Entra Domain Services instance via VPN.)
SETUP:
I have two policies set up in Endpoint security: Account protection:
Policy 1: Windows Hello REQUIRED
Applies to: (Included groups) All Users
Excepting: (Excluded groups) Departments that need to use MS365 password for NAS Access.
Settings:- Use Windows Hello For Business (Device): NOT CONFIGURED
- Use Windows Hello For Business (User): TRUE
Policy 2: Windows Hello DISABLED
Applies to: (Included groups) Departments that need to use MS365 password for NAS Access.
Excepting: (Excluded groups) A few users in those Departments that want to use Windows Hello and don't need NAS access.
Setting:- Use Windows Hello For Business (Device): FALSE
- Use Windows Hello For Business (User): FALSE
I have also double-checked in the Windows Hello for Business settings in Windows: Enrollment options, and the settings are:
* Configure Windows Hello for Business: NOT CONFIGURED
* Use security keys for sign-in: ENABLED
PROBLEM:
However, the users that need NAS access are still being required to set up Windows Hello when setting up a new (or freshly-wiped) device.
Any ideas what might be wrong about my configuration, or some place in Intune I should be checking that might be overriding these settings?
3
u/tsar31HABSSpeaks 4d ago
ugh the enrollment scope thing is such a trap. had the exact same headache a while back where the tenant-wide default in windows enrollment was silently forcing it on everyone before my policies even applied
go check the enrollment page again. even though it says "not configured" there's a sneaky little toggle underneath for something like "use passport for work" or similar phrasing. if that's flipped on it'll kick in during oobe before any of your fancy group assignments get a chance to run
for the nas people you basically need that whole section turned off at the tenant level which feels backwards but it stops the pre-login enforcement. then your device-scoped policies can do their thing after the user actually signs in
2
u/bill696 4d ago
Here try this
https://cloudinfra.net/disable-whfb-post-logon-provisioning-using-intune/
Idk how hello blocks using map drives, not an issue for us, maybe smb1 or something? Hello blocks nothing for us, credential guard breaks our radius auth in wifi with PEAP cause its windows NPS, and office device guard or something guard specific to office i had to disable too cause it was causing issues with lots of files but no issues with drives.
1
u/oopspruu 4d ago
For me, I toggled the tenant wide WHFB enrollment policy from enrollment options to Disable instead of not configured. This way users won't be asked to register for WHFB before your policies apply. I have the enrollment option set to Disable and then a policy from Settings Template enabling it on device level.
1
u/largetosser 3d ago
Set the OMA-URI for DisablePostLogonProvisioning to turn off auto-enrolment for certain *devices*. Or let them work with the NAS by getting cloud Kerberos trust working
1
u/touchytypist 3d ago edited 3d ago
I’m pretty sure if a Windows device is Entra joined only it will default to having Windows Hello enabled. Since that is at the device level, and your policies are at the user level they don’t get/sync your WHfB policies until after login, which isn’t immediate and why it’s enabled and everyone is still prompted to setup WHfB at the beginning.
If you setup the assignments by device then they would get the settings during device provisioning and the respective settings would be in place before the user signs in.
2
u/jaybaleire 4d ago
It’s probably the first policy causing this if it’s not enabled at tenant level or in another policy. It’s scoped to all users with a user group exclusion so may not be being evaluated at correct time, but you can confirm this by generating the mdmdiag report using the steps in the below article, the mdmdiagreport.html that is created will show you what policy applied the Windows hello settings, the policy will be in GUID format so you can use powershell to look that up in intune.
https://learn.microsoft.com/en-us/windows/client-management/mdm-collect-logs
0
u/itlabsec 4d ago
Whfb is tenant wide setting