mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-24 23:03:42 +00:00
Merge branch 'master' into v-smandalika-vl-rlb-4457208
This commit is contained in:
@ -312,6 +312,9 @@ To turn off the unlock server, the PXE provider can be unregistered from the WDS
|
||||
|
||||
To update the certificates used by Network Unlock, administrators need to import or generate the new certificate for the server and then update the Network Unlock certificate Group Policy setting on the domain controller.
|
||||
|
||||
> [!NOTE]
|
||||
> Servers that do not receive the Group Policy Object (GPO) will require a PIN when booting. In such cases, the reason why the server did not receive the GPO to update the certificate needs to be investigated.
|
||||
|
||||
## <a href="" id="bkmk-troubleshoot"></a>Troubleshoot Network Unlock
|
||||
|
||||
Troubleshooting Network Unlock issues begins by verifying the environment. Many times, a small configuration issue will be the root cause of the failure. Items to verify include:
|
||||
|
@ -25,8 +25,8 @@ This article addresses common issues in BitLocker and provides guidelines to tro
|
||||
Open Event Viewer and review the following logs under Applications and Services logs\\Microsoft\\Windows:
|
||||
|
||||
- **BitLocker-API**. Review the Management log, the Operational log, and any other logs that are generated in this folder. The default logs have the following unique names:
|
||||
- Microsoft-Windows-BitLocker/BitLocker Operational
|
||||
- Microsoft-Windows-BitLocker/BitLocker Management
|
||||
- Microsoft-Windows-BitLocker-API/BitLocker Operational
|
||||
- Microsoft-Windows-BitLocker-API/BitLocker Management
|
||||
|
||||
- **BitLocker-DrivePreparationTool**. Review the Admin log, the Operational log, and any other logs that are generated in this folder. The default logs have the following unique names:
|
||||
- Microsoft-Windows-BitLocker-DrivePreparationTool/Operational
|
||||
|
Reference in New Issue
Block a user