From 7bd2173e3c6593c1682e8d7a0e6a610566493e80 Mon Sep 17 00:00:00 2001 From: Teresa-Motiv Date: Thu, 7 Nov 2019 14:52:05 -0800 Subject: [PATCH] edits --- .../bitlocker/troubleshoot-bitlocker.md | 2 +- .../bitlocker/ts-bitlocker-config-issues.md | 6 +++--- .../bitlocker/ts-bitlocker-intune-issues.md | 2 +- .../bitlocker/ts-bitlocker-recovery-issues.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/security/information-protection/bitlocker/troubleshoot-bitlocker.md b/windows/security/information-protection/bitlocker/troubleshoot-bitlocker.md index 7b9c03a149..e741ed572f 100644 --- a/windows/security/information-protection/bitlocker/troubleshoot-bitlocker.md +++ b/windows/security/information-protection/bitlocker/troubleshoot-bitlocker.md @@ -88,7 +88,7 @@ Open an elevated Windows PowerShell window, and run each of the following comman |[**get-tpm \> C:\\TPM.txt**](https://docs.microsoft.com/powershell/module/trustedplatformmodule/get-tpm?view=win10-ps) |Exports information about the local computer's Trusted Platform Module (TPM). This cmdlet shows different values depending on whether the TPM chip is version 1.2 or 2.0. This cmdlet is not supported in Windows 7. | |[**manage-bde –status \> C:\\BDEStatus.txt**](https://docs.microsoft.com/windows-server/administration/windows-commands/manage-bde-status) |Exports information about the general encryption status of all drives on the computer. | |[**manage-bde c:
-protectors -get \> C:\\Protectors**](https://docs.microsoft.com/windows-server/administration/windows-commands/manage-bde-protectors) |Exports information about the protection methods that are used for the BitLocker encryption key. | -|[**reagentc /info \> C:\\reagent.txt**](https://docs.microsoft.com/windows-hardware/manufacture/desktop/reagentc-command-line-options) |Exports information oin an online or offline image about the current status of the Windows Recovery Environment (WindowsRE) and any available recovery image. | +|[**reagentc /info \> C:\\reagent.txt**](https://docs.microsoft.com/windows-hardware/manufacture/desktop/reagentc-command-line-options) |Exports information about an online or offline image about the current status of the Windows Recovery Environment (WindowsRE) and any available recovery image. | |[**get-BitLockerVolume \| fl**](https://docs.microsoft.com/powershell/module/bitlocker/get-bitlockervolume?view=win10-ps) |Gets information about volumes that BitLocker Drive Encryption can protect. | ## Review the configuration information diff --git a/windows/security/information-protection/bitlocker/ts-bitlocker-config-issues.md b/windows/security/information-protection/bitlocker/ts-bitlocker-config-issues.md index 00ffa6f2a6..8d2fed5bd4 100644 --- a/windows/security/information-protection/bitlocker/ts-bitlocker-config-issues.md +++ b/windows/security/information-protection/bitlocker/ts-bitlocker-config-issues.md @@ -45,13 +45,13 @@ After Windows 7 was released, several other areas of BitLocker were improved: - BitLocker Wizard - manage-bde - Group Policy Objects (GPOs) - - Mobile Device Managment (MDM) policy + - Mobile Device Management (MDM) policy - Windows PowerShell - Windows Management Interface (WMI) - **Integration with Azure Active Directory** (Azure AD). BitLocker can store recovery information in Azure AD to make it easier to recover. -- **[Direct memory access (DMA) port protection](https://docs.microsoft.com/windows/security/information-protection/kernel-dma-protection-for-thunderbolt)**. By using MDM policies to manage BitLocker, you can block a device's DMA ports and secure the device during its startup. +- **[Direct memory access (DMA) Port Protection](https://docs.microsoft.com/windows/security/information-protection/kernel-dma-protection-for-thunderbolt)**. By using MDM policies to manage BitLocker, you can block a device's DMA ports and secure the device during its startup. - **[BitLocker Network Unlock](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock)**. If your BitLocker-enabled desktop or server computer is connected to a wired corporate network in a domain environment, you can automatically unlock its operating system volume during a system restart. @@ -162,7 +162,7 @@ When the VSS NTDS writer requests access to the encrypted drive, the Local Secur ‎ \# This volume is locked by BitLocker Drive Encryption. ``` -The operation produces the following callstack: +The operation produces the following call stack: ``` \# Child-SP RetAddr Call Site diff --git a/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md b/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md index c9f0c5512f..c5a60928ad 100644 --- a/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md +++ b/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md @@ -131,7 +131,7 @@ reagentc /enable #### Step 3: Verify the Windows Boot Loader configuration -If the partition status is heathy, but the **reagentc /enable** command results in an error, verify that Windows Boot Loader contains the recovery sequence GUID. To do this, run the following command in an elevated Command Prompt window: +If the partition status is healthy, but the **reagentc /enable** command results in an error, verify that Windows Boot Loader contains the recovery sequence GUID. To do this, run the following command in an elevated Command Prompt window: ```cmd bcdedit /enum all diff --git a/windows/security/information-protection/bitlocker/ts-bitlocker-recovery-issues.md b/windows/security/information-protection/bitlocker/ts-bitlocker-recovery-issues.md index 45607c0564..012f5a20ec 100644 --- a/windows/security/information-protection/bitlocker/ts-bitlocker-recovery-issues.md +++ b/windows/security/information-protection/bitlocker/ts-bitlocker-recovery-issues.md @@ -209,7 +209,7 @@ To suspend BitLocker while you install TPM or UEFI firmware updates: ```ps Suspend-BitLocker -MountPoint ":" -RebootCount 0 ``` - In this cmdlet <*DriveLetter*> is the letter htat is assigned to your drive. + In this cmdlet <*DriveLetter*> is the letter that is assigned to your drive. 1. Install the Surface device driver and firmware updates. 1. After you install the firmware updates, restart the computer, open an elevated PowerShell window, and then run the following cmdlet: ```ps