mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 22:07:22 +00:00
Alt text & descriptions
This commit is contained in:
Teresa-Motiv
parent
7bd4f76afd
commit
a1fe3f16ca
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: BitLocker cannot encrypt a drive known issues
|
||||
description:
|
||||
description: Provides guidance for troubleshooting known issues that may prevent BitLocker Drive Encryption from encrypting a drive
|
||||
ms.reviewer: kaushika
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
@ -79,11 +79,11 @@ To verify that this issue has occurred, follow these steps:
|
||||
|
||||
1. Copy this output, and then use it as part of the [**ConvertFrom-SddlString**](https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/convertfrom-sddlstring?view=powershell-6) command in the PowerShell window, as follows:
|
||||
|
||||
|
||||
|
||||
|
||||
If you see NT AUTHORITY\INTERACTIVE (as highlighted), in the output of this command, this is the cause of the problem. Under typical conditions, the output should resemble the following:
|
||||
|
||||
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> GPOs that change the security descriptors of services have been known to cause this issue.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: BitLocker cannot encrypt a drive known TPM issues
|
||||
description:
|
||||
description: Provides guidance for troubleshooting known issues that may prevent BitLocker Drive Encryption from encrypting a drive, and that you can attribute to the TPM
|
||||
ms.reviewer: kaushika
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: BitLocker configuration known issues
|
||||
description:
|
||||
description: Describes common issues that involve your BitLocker configuration and BitLocker's general functionality, and provides guidance for addressing those issues.
|
||||
ms.reviewer: kaushika
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
@ -11,7 +11,7 @@ manager: kaushika
|
||||
audience: ITPro
|
||||
ms.collection: Windows Security Technologies\BitLocker
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 9/27/2019
|
||||
ms.date: 10/7/2019
|
||||
---
|
||||
|
||||
# BitLocker configuration: known issues
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Decode Measured Boot logs to track PCR changes
|
||||
description:
|
||||
description: Provides instructions for installing and using a tool for analyzing log information to identify changes to PCRs
|
||||
ms.reviewer: kaushika
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
@ -11,7 +11,7 @@ manager: kaushika
|
||||
audience: ITPro
|
||||
ms.collection: Windows Security Technologies\BitLocker
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 10/4/2019
|
||||
ms.date: 10/7/2019
|
||||
---
|
||||
|
||||
# Decode Measured Boot logs to track PCR changes
|
||||
@ -39,11 +39,11 @@ To install the tool, follow these steps:
|
||||
|
||||
1. Accept the default installation path.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under **Select the features you want to install**, select **Windows Hardware Lab Kit—Controller + Studio**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Finish the installation.
|
||||
|
||||
@ -54,7 +54,7 @@ To install the tool, follow these steps:
|
||||
|
||||
The TBSLogGenerator.exe file resides in this folder.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Run the following command:
|
||||
```cmd
|
||||
@ -67,16 +67,16 @@ To install the tool, follow these steps:
|
||||
TBSLogGenerator.exe -LF C:\MeasuredBoot\0000000005-0000000000.log > C:\MeasuredBoot\0000000005-0000000000.txt
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
The command produces a text file that uses the specified name. In the case of the example, the file is **0000000005-0000000000.txt**. The file resides in the same folder as the original .log file.
|
||||
|
||||
|
||||
|
||||
|
||||
The content of this text file resembles the following:
|
||||
|
||||
|
||||
|
||||
|
||||
To find the PCR information, go to the end of the file.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enforcing BitLocker policies by using Intune known issues
|
||||
description:
|
||||
description: provides assistance for issues that you may see if you use Microsoft Intune policy to manage silent BitLocker encryption on devices.
|
||||
ms.reviewer: kaushika
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
@ -11,12 +11,12 @@ manager: kaushika
|
||||
audience: ITPro
|
||||
ms.collection: Windows Security Technologies\BitLocker
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 10/2/2019
|
||||
ms.date: 10/7/2019
|
||||
---
|
||||
|
||||
# Enforcing BitLocker policies by using Intune: known issues
|
||||
|
||||
This article provides assistance for issues you may see if you use Microsoft Intune policy to manage silent BitLocker encryption on devices. The Intune portal indicates if BitLocker has failed to encrypt on or more managed devices.
|
||||
This article provides assistance for issues that you may see if you use Microsoft Intune policy to manage silent BitLocker encryption on devices. The Intune portal indicates whether BitLocker has failed to encrypt on or more managed devices.
|
||||
|
||||
|
||||
|
||||
@ -314,13 +314,13 @@ The OMA-URI references for these settings are the following:
|
||||
|
||||
During regular operations, BitLocker Drive Encryption generates events such as event ID 796 and event ID 845.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can also verify if the BitLocker Recovery Key has been uploaded to Azure by checking the device details in the Azure AD Devices section.
|
||||
|
||||
|
||||
|
||||
|
||||
On the device, check the Registry Editor to verify the policy settings on the device. Verify the entries under the following subkeys:
|
||||
|
||||
|
||||
@ -279,4 +279,4 @@ To resolve this issue, do one of the following:
|
||||
- Remove any device that uses TPM 1.2 from any group that is subject to Group Policy Objects (GPOs) that enforce Secure Launch.
|
||||
- Modify the **Turn On Virtualization Based Security** GPO to set **Secure Launch Configuration** to **Disabled**.
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user