mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 04:13:41 +00:00
Metadata/style update BitLocker 7
This commit is contained in:
Frank Rojas
@ -24,45 +24,57 @@ ms.technology: itpro-security
|
||||
|
||||
This article explains how to deploy BitLocker on Windows Server 2012 and later versions. For all Windows Server editions, BitLocker can be installed using Server Manager or Windows PowerShell cmdlets. BitLocker requires administrator privileges on the server on which it's to be installed.
|
||||
|
||||
## <a href="" id="installing-bitlocker-"></a>Installing BitLocker
|
||||
## Installing BitLocker
|
||||
|
||||
### <a href="" id="bkmk-blinstallsrvmgr"></a>To install BitLocker using server manager
|
||||
### To install BitLocker using server manager
|
||||
|
||||
1. Open server manager by selecting the server manager icon or running servermanager.exe.
|
||||
|
||||
2. Select **Manage** from the **Server Manager Navigation** bar and select **Add Roles and Features** to start the **Add Roles and Features Wizard.**
|
||||
|
||||
3. With the **Add Roles and Features** wizard open, select **Next** at the **Before you begin** pane (if shown).
|
||||
|
||||
4. Select **Role-based or feature-based installation** on the **Installation type** pane of the **Add Roles and Features** wizard and select **Next** to continue.
|
||||
|
||||
5. Select the **Select a server from the server pool** option in the **Server Selection** pane and confirm the server on which the BitLocker feature is to be installed.
|
||||
|
||||
6. Select **Next** on the **Server Roles** pane of the **Add Roles and Features** wizard to proceed to the **Features** pane.
|
||||
**Note**: Server roles and features are installed by using the same wizard in Server Manager.
|
||||
|
||||
> [!NOTE]
|
||||
> Server roles and features are installed by using the same wizard in Server Manager.
|
||||
|
||||
7. Select the check box next to **BitLocker Drive Encryption** within the **Features** pane of the **Add Roles and Features** wizard. The wizard shows the extra management features available for BitLocker. If you don't want to install these features, deselect the **Include management tools
|
||||
** and select **Add Features**. Once optional features selection is complete, select **Next** to proceed in the wizard.
|
||||
|
||||
> **Note:** The **Enhanced Storage** feature is a required feature for enabling BitLocker. This feature enables support for encrypted hard drives on capable systems.
|
||||
> [!NOTE]
|
||||
> The **Enhanced Storage** feature is a required feature for enabling BitLocker. This feature enables support for encrypted hard drives on capable systems.
|
||||
|
||||
8. Select **Install** on the **Confirmation** pane of the **Add Roles and Features** wizard to begin BitLocker feature installation. The BitLocker feature requires a restart for its installation to be complete. Selecting the **Restart the destination server automatically if required** option in the **Confirmation** pane forces a restart of the computer after installation is complete.
|
||||
|
||||
9. If the **Restart the destination server automatically if required** check box isn't selected, the **Results** pane of the **Add Roles and Features** wizard displays the success or failure of the BitLocker feature installation. If necessary, a notification of other action necessary to complete the feature installation, such as the restart of the computer, will be displayed in the results text.
|
||||
|
||||
### <a href="" id="bkmk-blinstallwps"></a>To install BitLocker using Windows PowerShell
|
||||
### To install BitLocker using Windows PowerShell
|
||||
|
||||
Windows PowerShell offers administrators another option for BitLocker feature installation. Windows PowerShell installs features using the `servermanager` or `dism` module; however, the `servermanager` and `dism` modules don't always share feature name parity. Because of this, it's advisable to confirm the feature or role name prior to installation.
|
||||
Windows PowerShell offers administrators another option for BitLocker feature installation. Windows PowerShell installs features using the `servermanager` or `dism` module. However, the `servermanager` and `dism` modules don't always share feature name parity. Because of this mismatch of feature name parity, it's advisable to confirm the feature or role name prior to installation.
|
||||
|
||||
>**Note:**You must restart the server to complete the installation of BitLocker.
|
||||
> [!NOTE]
|
||||
> You must restart the server to complete the installation of BitLocker.
|
||||
|
||||
### Using the servermanager module to install BitLocker
|
||||
|
||||
The `servermanager` Windows PowerShell module can use either the `Install-WindowsFeature` or `Add-WindowsFeature` to install the BitLocker feature. The `Add-WindowsFeature` cmdlet is merely a stub to the `Install-WindowsFeature`. This example uses the `Install-WindowsFeature` cmdlet. The feature name for BitLocker in the `servermanager` module is `BitLocker`.
|
||||
|
||||
By default, installation of features in Windows PowerShell doesn't include optional sub-features or management tools as part of the installation process. This can be seen using the `-WhatIf` option in Windows PowerShell.
|
||||
By default, installation of features in Windows PowerShell doesn't include optional sub-features or management tools as part of the installation process. What is installed as part of the installation process can be seen using the `-WhatIf` option in Windows PowerShell.
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Install-WindowsFeature BitLocker -WhatIf
|
||||
```
|
||||
|
||||
The results of this command show that only the BitLocker Drive Encryption feature is installed using this command.
|
||||
|
||||
To see what would be installed with the BitLocker feature, including all available management tools and sub-features, use the following command:
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Install-WindowsFeature BitLocker -IncludeAllSubFeature -IncludeManagementTools -WhatIf | fl
|
||||
```
|
||||
|
||||
@ -78,17 +90,18 @@ The result of this command displays the following list of all the administration
|
||||
|
||||
The command to complete a full installation of the BitLocker feature with all available sub-features and then to reboot the server at completion is:
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Install-WindowsFeature BitLocker -IncludeAllSubFeature -IncludeManagementTools -Restart
|
||||
```
|
||||
|
||||
>**Important:**Installing the BitLocker feature using Windows PowerShell does not install the Enhanced Storage feature. Administrators wishing to support Encrypted Hard Drives in their environment will need to install the Enhanced Storage feature separately.
|
||||
> [!IMPORTANT]
|
||||
> Installing the BitLocker feature using Windows PowerShell does not install the Enhanced Storage feature. Administrators wishing to support Encrypted Hard Drives in their environment will need to install the Enhanced Storage feature separately.
|
||||
|
||||
### Using the dism module to install BitLocker
|
||||
|
||||
The `dism` Windows PowerShell module uses the `Enable-WindowsOptionalFeature` cmdlet to install features. The BitLocker feature name for BitLocker is `BitLocker`. The `dism` module doesn't support wildcards when searching for feature names. To list feature names for the `dism` module, use the `Get-WindowsOptionalFeatures` cmdlet. The following command will list all of the optional features in an online (running) operating system.
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Get-WindowsOptionalFeature -Online | ft
|
||||
```
|
||||
|
||||
@ -96,16 +109,17 @@ From this output, we can see that there are three BitLocker-related optional fea
|
||||
|
||||
To install BitLocker using the `dism` module, use the following command:
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Enable-WindowsOptionalFeature -Online -FeatureName BitLocker -All
|
||||
```
|
||||
|
||||
This command prompts the user for a reboot. The Enable-WindowsOptionalFeature cmdlet doesn't offer support for forcing a reboot of the computer. This command doesn't include installation of the management tools for BitLocker. For a complete installation of BitLocker and all available management tools, use the following command:
|
||||
|
||||
```powershell
|
||||
``` powershell
|
||||
Enable-WindowsOptionalFeature -Online -FeatureName BitLocker, BitLocker-Utilities -All
|
||||
```
|
||||
## More information
|
||||
|
||||
## Related articles
|
||||
|
||||
- [BitLocker overview](bitlocker-overview.md)
|
||||
- [BitLocker frequently asked questions (FAQ)](bitlocker-frequently-asked-questions.yml)
|
||||
|
||||
@ -30,9 +30,11 @@ sections:
|
||||
questions:
|
||||
- question: How can I authenticate or unlock my removable data drive?
|
||||
answer: |
|
||||
You can unlock removable data drives by using a password, a smart card, or you can configure a SID protector to unlock a drive by using your domain credentials. After you've started encryption, the drive can also be automatically unlocked on a specific computer for a specific user account. System administrators can configure which options are available for users, as well as password complexity and minimum length requirements. To unlock by using a SID protector, use Manage-bde:
|
||||
You can unlock removable data drives by using a password, a smart card, or you can configure a SID protector to unlock a drive by using your domain credentials. After you've started encryption, the drive can also be automatically unlocked on a specific computer for a specific user account. System administrators can configure which options are available for users including password complexity and minimum length requirements. To unlock by using a SID protector, use Manage-bde:
|
||||
|
||||
<code>Manage-bde -protectors -add e: -sid <i>domain\username</i></code>
|
||||
``` syntax
|
||||
Manage-bde.exe -protectors -add e: -sid <i>domain\username</i></code>
|
||||
```
|
||||
|
||||
- question: What is the difference between a recovery password, recovery key, PIN, enhanced PIN, and startup key?
|
||||
answer: |
|
||||
@ -42,22 +44,26 @@ sections:
|
||||
answer: |
|
||||
The recovery password and recovery key for an operating system drive or a fixed data drive can be saved to a folder, saved to one or more USB devices, saved to your Microsoft Account, or printed.
|
||||
|
||||
For removable data drives, the recovery password and recovery key can be saved to a folder, saved to your Microsoft Account, or printed. By default, you cannot store a recovery key for a removable drive on a removable drive.
|
||||
For removable data drives, the recovery password and recovery key can be saved to a folder, saved to your Microsoft Account, or printed. By default, you can't store a recovery key for a removable drive on a removable drive.
|
||||
|
||||
A domain administrator can additionally configure Group Policy to automatically generate recovery passwords and store them in Active Directory Domain Services (AD DS) for any BitLocker-protected drive.
|
||||
A domain administrator can also configure Group Policy to automatically generate recovery passwords and store them in Active Directory Domain Services (AD DS) for any BitLocker-protected drive.
|
||||
|
||||
- question: Is it possible to add an additional method of authentication without decrypting the drive if I only have the TPM authentication method enabled?
|
||||
answer: |
|
||||
You can use the Manage-bde.exe command-line tool to replace your TPM-only authentication mode with a multifactor authentication mode. For example, if BitLocker is enabled with TPM authentication only and you want to add PIN authentication, use the following commands from an elevated command prompt, replacing *4-20 digit numeric PIN* with the numeric PIN you want to use:
|
||||
|
||||
<code>manage-bde -protectors -delete %systemdrive% -type tpm</code>
|
||||
``` syntax
|
||||
manage-bde.exe -protectors -delete %systemdrive% -type tpm
|
||||
```
|
||||
|
||||
<code>manage-bde -protectors -add %systemdrive% -tpmandpin <i>4-20 digit numeric PIN</i></code>
|
||||
``` syntax
|
||||
manage-bde.exe -protectors -add %systemdrive% -tpmandpin <4-20 digit numeric PIN>
|
||||
```
|
||||
|
||||
|
||||
- question: When should an additional method of authentication be considered?
|
||||
answer: |
|
||||
New hardware that meets [Windows Hardware Compatibility Program](/windows-hardware/design/compatibility/) requirements make a PIN less critical as a mitigation, and having a TPM-only protector is likely sufficient when combined with policies like device lockout. For example, Surface Pro and Surface Book do not have external DMA ports to attack.
|
||||
New hardware that meets [Windows Hardware Compatibility Program](/windows-hardware/design/compatibility/) requirements make a PIN less critical as a mitigation, and having a TPM-only protector is likely sufficient when combined with policies like device lockout. For example, Surface Pro and Surface Book don't have external DMA ports to attack.
|
||||
For older hardware, where a PIN may be needed, it's recommended to enable [enhanced PINs](bitlocker-group-policy-settings.md#allow-enhanced-pins-for-startup) that allow non-numeric characters such as letters and punctuation marks, and to set the PIN length based on your risk tolerance and the hardware anti-hammering capabilities available to the TPMs in your computers.
|
||||
|
||||
- question: If I lose my recovery information, will the BitLocker-protected data be unrecoverable?
|
||||
@ -68,7 +74,7 @@ sections:
|
||||
> Store the recovery information in AD DS, along with your Microsoft Account, or another safe location.
|
||||
|
||||
- question: Can the USB flash drive that is used as the startup key also be used to store the recovery key?
|
||||
answer: While this is technically possible, it is not a best practice to use one USB flash drive to store both keys. If the USB flash drive that contains your startup key is lost or stolen, you also lose access to your recovery key. In addition, inserting this key would cause your computer to automatically boot from the recovery key even if TPM-measured files have changed, which circumvents the TPM's system integrity check.
|
||||
answer: While using a USB flash drive as both the startup key and for storage of the recovery key is technically possible, it isn't a best practice to use one USB flash drive to store both keys. If the USB flash drive that contains your startup key is lost or stolen, you also lose access to your recovery key. In addition, inserting this key would cause your computer to automatically boot from the recovery key even if TPM-measured files have changed, which circumvents the TPM's system integrity check.
|
||||
|
||||
- question: Can I save the startup key on multiple USB flash drives?
|
||||
answer: Yes, you can save a computer's startup key on multiple USB flash drives. Right-clicking a BitLocker-protected drive and selecting **Manage BitLocker** will provide you the options to duplicate the recovery keys as needed.
|
||||
@ -80,7 +86,7 @@ sections:
|
||||
answer: You can generate different startup keys for the same computer through scripting. However, for computers that have a TPM, creating different startup keys prevents BitLocker from using the TPM's system integrity check.
|
||||
|
||||
- question: Can I generate multiple PIN combinations?
|
||||
answer: You cannot generate multiple PIN combinations.
|
||||
answer: You can't generate multiple PIN combinations.
|
||||
|
||||
- question: What encryption keys are used in BitLocker? How do they work together?
|
||||
answer: Raw data is encrypted with the full volume encryption key, which is then encrypted with the volume master key. The volume master key is in turn encrypted by one of several possible methods depending on your authentication (that is, key protectors or TPM) and recovery scenarios.
|
||||
@ -93,16 +99,16 @@ sections:
|
||||
|
||||
- question: Why do I have to use the function keys to enter the PIN or the 48-character recovery password?
|
||||
answer: |
|
||||
The F1 through F10 keys are universally mapped scan codes available in the pre-boot environment on all computers and in all languages. The numeric keys 0 through 9 are not usable in the pre-boot environment on all keyboards.
|
||||
The F1 through F10 keys are universally mapped scan codes available in the pre-boot environment on all computers and in all languages. The numeric keys 0 through 9 aren't usable in the pre-boot environment on all keyboards.
|
||||
|
||||
When using an enhanced PIN, users should run the optional system check during the BitLocker setup process to ensure that the PIN can be entered correctly in the pre-boot environment.
|
||||
|
||||
- question: How does BitLocker help prevent an attacker from discovering the PIN that unlocks my operating system drive?
|
||||
answer: |
|
||||
It is possible that a personal identification number (PIN) can be discovered by an attacker performing a brute force attack. A brute force attack occurs when an attacker uses an automated tool to try different PIN combinations until the correct one is discovered. For BitLocker-protected computers, this type of attack, also known as a dictionary attack, requires that the attacker have physical access to the computer.
|
||||
It's possible that a personal identification number (PIN) can be discovered by an attacker performing a brute force attack. A brute force attack occurs when an attacker uses an automated tool to try different PIN combinations until the correct one is discovered. For BitLocker-protected computers, this type of attack, also known as a dictionary attack, requires that the attacker has physical access to the computer.
|
||||
|
||||
The TPM has the built-in ability to detect and react to these types of attacks. Because different manufacturers' TPMs may support different PIN and attack mitigations, contact your TPM's manufacturer to determine how your computer's TPM mitigates PIN brute force attacks.
|
||||
After you have determined your TPM's manufacturer, contact the manufacturer to gather the TPM's vendor-specific information. Most manufacturers use the PIN authentication failure count to exponentially increase lockout time to the PIN interface. However, each manufacturer has different policies regarding when and how the failure counter is decreased or reset.
|
||||
After you've determined your TPM's manufacturer, contact the manufacturer to gather the TPM's vendor-specific information. Most manufacturers use the PIN authentication failure count to exponentially increase lockout time to the PIN interface. However, each manufacturer has different policies regarding when and how the failure counter is decreased or reset.
|
||||
|
||||
- question: How can I determine the manufacturer of my TPM?
|
||||
answer: You can determine your TPM manufacturer in **Windows Defender Security Center** > **Device Security** > **Security processor details**.
|
||||
@ -117,6 +123,6 @@ sections:
|
||||
|
||||
- question: Can PIN length and complexity be managed with Group Policy?
|
||||
answer: |
|
||||
Yes and No. You can configure the minimum personal identification number (PIN) length by using the **Configure minimum PIN length for startup** Group Policy setting and allow the use of alphanumeric PINs by enabling the **Allow enhanced PINs for startup** Group Policy setting. However, you cannot require PIN complexity by Group Policy.
|
||||
Yes and No. You can configure the minimum personal identification number (PIN) length by using the **Configure minimum PIN length for startup** Group Policy setting and allow the use of alphanumeric PINs by enabling the **Allow enhanced PINs for startup** Group Policy setting. However, you can't require PIN complexity by Group Policy.
|
||||
|
||||
For more info, see [BitLocker Group Policy settings](bitlocker-group-policy-settings.md).
|
||||
|
||||
@ -142,9 +142,9 @@ Windows PowerShell cmdlets provide a new way for administrators to use when work
|
||||
|
||||
Similar to manage-bde, the Windows PowerShell cmdlets allow configuration beyond the options offered in the control panel. As with manage-bde, users need to consider the specific needs of the volume they're encrypting prior to running Windows PowerShell cmdlets.
|
||||
|
||||
A good initial step is to determine the current state of the volume(s) on the computer. You can do this using the <code>Get-BitLockerVolume</code> cmdlet.
|
||||
A good initial step is to determine the current state of the volume(s) on the computer. You can do this using the `Get-BitLockerVolume` cmdlet.
|
||||
|
||||
The <code>Get-BitLockerVolume</code> cmdlet output gives information on the volume type, protectors, protection status, and other details.
|
||||
The `Get-BitLockerVolume` cmdlet output gives information on the volume type, protectors, protection status, and other details.
|
||||
|
||||
> [!TIP]
|
||||
> Occasionally, all protectors may not be shown when using `Get-BitLockerVolume` due to lack of space in the output display. If you don't see all of the protectors for a volume, you can use the Windows PowerShell pipe command (|) to format a full listing of the protectors.
|
||||
|
||||
@ -101,7 +101,9 @@ sections:
|
||||
|
||||
The syntax of this command is:
|
||||
|
||||
<code>manage-bde <i>driveletter</i> -lock</code>
|
||||
``` syntax
|
||||
manage-bde <driveletter> -lock
|
||||
````
|
||||
|
||||
Outside of using this command, data drives will be locked on shutdown and restart of the operating system. A removable data drive will also be locked automatically when the drive is removed from the computer.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user