From cdc8e7fc6e8be797dba2e9cf853f9fdb594a0d66 Mon Sep 17 00:00:00 2001 From: Raphael Schweizer Date: Tue, 10 Dec 2019 13:58:35 +0100 Subject: [PATCH] `copy-paste`ability MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit update to remove – (en-dash) in code --- .../bitlocker/bitlocker-how-to-enable-network-unlock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 e91f6d7db8..7cdd7f45b1 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 @@ -314,7 +314,7 @@ Troubleshooting Network Unlock issues begins by verifying the environment. Many - Verify the **Network (Certificate Based)** protector is listed on the client. This can be done using either manage-bde or Windows PowerShell cmdlets. For example the following command will list the key protectors currently configured on the C: drive of the lcoal computer: ```powershell - manage-bde –protectors –get C: + manage-bde -protectors -get C: ``` >**Note:** Use the output of manage-bde along with the WDS debug log to determine if the proper certificate thumbprint is being used for Network Unlock