From dec74b2b51794370de92d843dceb2f51cf48d0fd Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Tue, 25 Aug 2020 15:16:24 -0700 Subject: [PATCH] resolving some build warnings --- .../bitlocker/bitlocker-frequently-asked-questions.md | 2 +- .../bitlocker/bitlocker-how-to-enable-network-unlock.md | 3 ++- .../bitlocker/ts-bitlocker-intune-issues.md | 2 +- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md b/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md index 1f6db4c45f..3679c9fde7 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md +++ b/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions.md @@ -18,7 +18,7 @@ ms.date: 02/28/2019 ms.custom: bitlocker --- -# BitLocker frequently asked questions (FAQ) +# BitLocker frequently asked questions (FAQ) resources **Applies to** - Windows 10 diff --git a/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md b/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md index be66dcfa75..612474e464 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md +++ b/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md @@ -368,7 +368,7 @@ The following steps can be used to configure Network Unlock on these older syste 6. Configure registry settings for Network Unlock: Apply the registry settings by running the following certutil script (assuming your network unlock certificate file is called **BitLocker-NetworkUnlock.cer**) on each computer running any of the client operating systems designated in the **Applies To** list at the beginning of this topic. - +```dos certutil -f -grouppolicy -addstore FVE_NKP BitLocker-NetworkUnlock.cer reg add "HKLM\SOFTWARE\Policies\Microsoft\FVE" /v OSManageNKP /t REG_DWORD /d 1 /f reg add "HKLM\SOFTWARE\Policies\Microsoft\FVE" /v UseAdvancedStartup /t REG_DWORD /d 1 /f @@ -377,6 +377,7 @@ The following steps can be used to configure Network Unlock on these older syste reg add "HKLM\SOFTWARE\Policies\Microsoft\FVE" /v UseTPM /t REG_DWORD /d 2 /f reg add "HKLM\SOFTWARE\Policies\Microsoft\FVE" /v UseTPMKey /t REG_DWORD /d 2 /f reg add "HKLM\SOFTWARE\Policies\Microsoft\FVE" /v UseTPMKeyPIN /t REG_DWORD /d 2 /f +``` 7. Set up a TPM protector on the clients 8. Reboot the clients to add the Network (Certificate Based) protector 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 fdf85626d1..895c4eec13 100644 --- a/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md +++ b/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues.md @@ -206,7 +206,7 @@ To verify the Secure Boot state, use the System Information app. To do this, fol 1. Verify that the **Secure Boot State** setting is **On**, as follows: ![System Information app, showing a supported Secure Boot State](./images/4509201-en-1.png) 1. If the **Secure Boot State** setting is **Unsupported**, you cannot use Silent BitLocker Encryption on this device. - ![System Information app, showing a supported Secure Boot State](./images/4509202-en-1.png) + ![System Information app, showing a unsupported Secure Boot State](./images/4509202-en-1.png) > [!NOTE] > You can also use the [Confirm-SecureBootUEFI](https://docs.microsoft.com/powershell/module/secureboot/confirm-securebootuefi?view=win10-ps) cmdlet to verify the Secure Boot state. To do this, open an elevated PowerShell window and run the following command: