mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-17 15:57:23 +00:00
updates
This commit is contained in:
parent
16172e584b
commit
327117414a
@ -20304,6 +20304,11 @@
|
||||
"source_path": "windows/security/identity-protection/hello-for-business/hello-feature-conditional-access.md",
|
||||
"redirect_url": "/windows/security/identity-protection/hello-for-business/hello-faq",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/identity-protection/hello-for-business/hello-event-300.md",
|
||||
"redirect_url": "/windows/security/identity-protection/hello-for-business/hello-faq",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
@ -1,37 +0,0 @@
|
||||
---
|
||||
title: Event ID 300 - Windows Hello successfully created (Windows)
|
||||
description: This event is created when a Windows Hello for Business is successfully created and registered with Azure Active Directory (Azure AD).
|
||||
ms.date: 07/27/2017
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10 and later</a>
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Event ID 300 - Windows Hello successfully created
|
||||
|
||||
This event is created when Windows Hello for Business is successfully created and registered with Azure Active Directory (Azure AD). Applications or services can trigger actions on this event. For example, a certificate provisioning service can listen to this event and trigger a certificate request.
|
||||
|
||||
## Event details
|
||||
|
||||
| **Product:** | Windows 10 or Windows 11 operating system |
|
||||
|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| **Log:** | Event Viewer > Applications and Service Logs\Microsoft\Windows\User Device Registration\Admin |
|
||||
| **ID:** | 300 |
|
||||
| **Source:** | Microsoft Azure Device Registration Service |
|
||||
| **Version:** | 10 or 11 |
|
||||
| **Message:** | The NGC key was successfully registered. Key ID: {4476694e-8e3b-4ef8-8487-be21f95e6f07}. UPN:test@contoso.com. Attestation: ATT\_SOFT. Client request ID: . Server request ID: db2da6bd-3d70-4b9b-b26b-444f669902da.</br>Server response: {"kid":"4476694e-8e3b-4ef8-8487-be21f95e6f07","upn":"test@contoso.com"} |
|
||||
|
||||
## Resolve
|
||||
|
||||
This is a normal condition. No further action is required.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Windows Hello for Business](hello-identity-verification.md)
|
||||
- [How Windows Hello for Business works](hello-how-it-works.md)
|
||||
- [Manage Windows Hello for Business in your organization](hello-manage-in-organization.md)
|
||||
- [Why a PIN is better than a password](hello-why-pin-is-better-than-password.md)
|
||||
- [Prepare people to use Windows Hello](hello-prepare-people-to-use.md)
|
||||
- [Windows Hello and password changes](hello-and-password-changes.md)
|
||||
- [Windows Hello errors during PIN creation](/troubleshoot/windows-client/user-profiles-and-logon/windows-hello-errors-during-pin-creation-in-windows-10)
|
||||
- [Windows Hello biometrics in the enterprise](hello-biometrics-in-enterprise.md)
|
@ -120,6 +120,9 @@ sections:
|
||||
- question: Can I disable the PIN while using Windows Hello for Business?
|
||||
answer: |
|
||||
No. The movement away from passwords is accomplished by gradually reducing the use of the password. In situations where you can't authenticate by using biometrics, you need a fallback mechanism that isn't a password. The PIN is the fallback mechanism. Disabling or hiding the PIN credential provider will disable the use of biometrics.
|
||||
- question: What is Event ID 300?
|
||||
answer: |
|
||||
This event is created when Windows Hello for Business is successfully created and registered with Azure Active Directory (Azure AD). Applications or services can trigger actions on this event. For example, a certificate provisioning service can listen to this event and trigger a certificate request. This is a normal condition and no further action is required.
|
||||
|
||||
- name: Design and planning
|
||||
questions:
|
||||
|
@ -131,6 +131,8 @@
|
||||
href: hello-prepare-people-to-use.md
|
||||
- name: Manage Windows Hello for Business in your organization
|
||||
href: hello-manage-in-organization.md
|
||||
- name: Windows Hello and password changes
|
||||
href: hello-and-password-changes.md
|
||||
- name: Windows Hello for Business features
|
||||
items:
|
||||
- name: PIN Reset
|
||||
@ -149,10 +151,6 @@
|
||||
href: hello-deployment-issues.md
|
||||
- name: Errors during PIN creation
|
||||
href: hello-errors-during-pin-creation.md
|
||||
- name: Event ID 300 - Windows Hello successfully created
|
||||
href: hello-event-300.md
|
||||
- name: Windows Hello and password changes
|
||||
href: hello-and-password-changes.md
|
||||
- name: Reference
|
||||
items:
|
||||
- name: How Windows Hello for Business provisioning works
|
||||
|
Loading…
x
Reference in New Issue
Block a user