drdread
  • drdread
  • 100% (Exalted)
  • Advanced Member Topic Starter
4 years ago
Can anyone shed any light on this?

It is something to do with GPO obviously, but we have nothing in place that I can see would generate this:

Log Name: Microsoft-Windows-User Device Registration/Admin
Source: Microsoft-Windows-User Device Registration
Date: 03/09/2020 13:04:00
Event ID: 360
Task Category: None
Level: Warning
Keywords:
User: domain.suffix\user
Computer: PC.domain.suffix
Description:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.

Event Xml:



360
0
3
0
0
0x8000000000000000

240


Microsoft-Windows-User Device Registration/Admin
PC.domain.suffix



Windows Hello for Business provisioning will not be launched.
Not Tested
No
Not Tested
Not Tested
Not Tested
Yes
Not Tested
none

Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


sirclesadmin
3 years ago
The domain to which the machine has been joined is not rigged up for Windows Hello login and so the Windows Hello service will not be provisioning login. You should be able to change this in your Azure environment and you can see how it is managed here.