| Posted by: drdread - 03 September 2020 14:06:38 |
|---|
|
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:
|
| Posted by: sirclesadmin - 18 November 2020 18:09:16 |
|---|
| 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 [url=https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-manage-in-organization]here.[/url] |