mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 01:07:23 +00:00
Update bitlocker-basic-deployment.md - 4318240
This commit is contained in:
parent
652e9bbbd7
commit
b68de39d2a
@ -27,9 +27,9 @@ This topic for the IT professional explains how BitLocker features can be used t
|
|||||||
|
|
||||||
## Using BitLocker to encrypt volumes
|
## Using BitLocker to encrypt volumes
|
||||||
|
|
||||||
BitLocker provides full volume encryption (FVE) for operating system volumes, as well as fixed and removable data volumes. To support fully encrypted operating system volumes, BitLocker uses an unencrypted system volume for the files required to boot, decrypt, and load the operating system. This volume is automatically created during a new installation of both client and server operating systems.
|
BitLocker provides full volume encryption (FVE) for operating system volumes, as well as fixed and removable data drives. To support fully encrypted operating system drives, BitLocker uses an unencrypted system partition for the files required to boot, decrypt, and load the operating system. This partition is automatically created during a new installation of both client and server operating systems.
|
||||||
|
|
||||||
In the event that the drive was prepared as a single contiguous space, BitLocker requires a new volume to hold the boot files. BdeHdCfg.exe can create these volumes.
|
In the event that the drive was prepared as a single contiguous space, BitLocker requires a new partition to hold the boot files. BdeHdCfg.exe can create these volumes.
|
||||||
|
|
||||||
> **Note:** For more info about using this tool, see [Bdehdcfg](https://technet.microsoft.com/library/ee732026.aspx) in the Command-Line Reference.
|
> **Note:** For more info about using this tool, see [Bdehdcfg](https://technet.microsoft.com/library/ee732026.aspx) in the Command-Line Reference.
|
||||||
|
|
||||||
@ -42,12 +42,12 @@ BitLocker encryption can be done using the following methods:
|
|||||||
|
|
||||||
### Encrypting volumes using the BitLocker control panel
|
### Encrypting volumes using the BitLocker control panel
|
||||||
|
|
||||||
Encrypting volumes with the BitLocker control panel (click **Start**, type **bitlocker**, click **Manage BitLocker**) is how many users will utilize BitLocker. The name of the BitLocker control panel is BitLocker Drive Encryption. The BitLocker control panel supports encrypting operating system, fixed data and removable data volumes. The BitLocker control panel will organize available drives in the appropriate category based on how the device reports itself to Windows. Only formatted volumes with assigned drive letters will appear properly in the BitLocker control panel applet.
|
Encrypting volumes with the BitLocker control panel (click **Start**, type **bitlocker**, click **Manage BitLocker**) is the mechanism implemented by many users to utilize BitLocker. The name of the BitLocker control panel is BitLocker Drive Encryption. The BitLocker control panel supports encrypting operating system, fixed data- and removable data volumes. The BitLocker control panel will organize available drives in the appropriate category based on how the device reports itself to Windows. Only formatted volumes with assigned drive letters will appear properly in the BitLocker control panel applet.
|
||||||
To start encryption for a volume, select **Turn on BitLocker** for the appropriate drive to initialize the BitLocker Drive Encryption Wizard. BitLocker Drive Encryption Wizard options vary based on volume type (operating system volume or data volume).
|
To start encryption for a volume, select **Turn on BitLocker** for the appropriate drive to initialize the BitLocker Drive Encryption Wizard. BitLocker Drive Encryption Wizard options vary based on volume type (operating system volume or data volume).
|
||||||
|
|
||||||
### Operating system volume
|
### Operating system volume
|
||||||
|
|
||||||
Upon launch, the BitLocker Drive Encryption Wizard verifies the computer meets the BitLocker system requirements for encrypting an operating system volume. By default, the system requirements are:
|
Upon launch, the BitLocker Drive Encryption Wizard verifies whether the computer meets the BitLocker system requirements for encrypting an operating system volume. By default, the system requirements are:
|
||||||
<table>
|
<table>
|
||||||
<colgroup>
|
<colgroup>
|
||||||
<col width="50%" />
|
<col width="50%" />
|
||||||
@ -97,14 +97,13 @@ Upon launch, the BitLocker Drive Encryption Wizard verifies the computer meets t
|
|||||||
Upon passing the initial configuration, users are required to enter a password for the volume. If the volume does not pass the initial configuration for BitLocker, the user is presented with an error dialog describing the appropriate actions to be taken.
|
Upon passing the initial configuration, users are required to enter a password for the volume. If the volume does not pass the initial configuration for BitLocker, the user is presented with an error dialog describing the appropriate actions to be taken.
|
||||||
Once a strong password has been created for the volume, a recovery key will be generated. The BitLocker Drive Encryption Wizard will prompt for a location to save this key. A BitLocker recovery key is a special key that you can create when you turn on BitLocker Drive Encryption for the first time on each drive that you encrypt. You can use the recovery key to gain access to your computer if the drive that Windows is installed on (the operating system drive) is encrypted using BitLocker Drive Encryption and BitLocker detects a condition that prevents it from unlocking the drive when the computer is starting up. A recovery key can also be used to gain access to your files and folders on a removable data drive (such as an external hard drive or USB flash drive) that is encrypted using BitLocker To Go, if for some reason you forget the password or your computer cannot access the drive.
|
Once a strong password has been created for the volume, a recovery key will be generated. The BitLocker Drive Encryption Wizard will prompt for a location to save this key. A BitLocker recovery key is a special key that you can create when you turn on BitLocker Drive Encryption for the first time on each drive that you encrypt. You can use the recovery key to gain access to your computer if the drive that Windows is installed on (the operating system drive) is encrypted using BitLocker Drive Encryption and BitLocker detects a condition that prevents it from unlocking the drive when the computer is starting up. A recovery key can also be used to gain access to your files and folders on a removable data drive (such as an external hard drive or USB flash drive) that is encrypted using BitLocker To Go, if for some reason you forget the password or your computer cannot access the drive.
|
||||||
|
|
||||||
You should store the recovery key by printing it, saving it on removable media, or saving it as a file in a network folder or on your OneDrive, or on another drive of your computer that you are not encrypting. You cannot save the recovery key to the root directory of a non-removable drive and cannot be stored on the encrypted volume. You cannot save the recovery key for a removable data drive (such as a USB flash drive) on removable media. Ideally, you should store the recovery key separate from your computer. After you create a recovery key, you can use the BitLocker control panel to make additional copies.
|
You should store the recovery key by printing it; saving it on a removable media; or saving it as a file in a network folder, on your OneDrive, or on another drive of your computer that you are not encrypting. You cannot save the recovery key to the root directory of a non-removable drive and cannot store it on the encrypted volume. You cannot save the recovery key for a removable data drive (such as a USB flash drive) on a removable media. Ideally, you should store the recovery key separate from your computer. After you create a recovery key, you can use the BitLocker control panel to make additional copies.
|
||||||
|
|
||||||
When the recovery key has been properly stored, the BitLocker Drive Encryption Wizard will prompt the user to choose how to encrypt the drive. There are two options:
|
When the recovery key has been properly stored, the BitLocker Drive Encryption Wizard will prompt the user to choose how to encrypt the drive. There are two options:
|
||||||
|
Encrypt used disk space only—Encrypts only disk space that contains data
|
||||||
|
Encrypt entire drive—Encrypts the entire volume including free space
|
||||||
|
|
||||||
- Encrypt used disk space only - Encrypts only disk space that contains data
|
It is recommended that drives with little-to-no data utilize the **used disk space only** encryption option and that drives with data or an operating system utilize the **encrypt entire drive** option.
|
||||||
- Encrypt entire drive - Encrypts the entire volume including free space
|
|
||||||
|
|
||||||
It is recommended that drives with little to no data utilize the **used disk space only** encryption option and that drives with data or an operating system utilize the **encrypt entire drive** option.
|
|
||||||
|
|
||||||
> **Note:** Deleted files appear as free space to the file system, which is not encrypted by **used disk space only**. Until they are wiped or overwritten, deleted files hold information that could be recovered with common data forensic tools.
|
> **Note:** Deleted files appear as free space to the file system, which is not encrypted by **used disk space only**. Until they are wiped or overwritten, deleted files hold information that could be recovered with common data forensic tools.
|
||||||
|
|
||||||
@ -116,13 +115,13 @@ Until encryption is completed, the only available options for managing BitLocker
|
|||||||
|
|
||||||
### Data volume
|
### Data volume
|
||||||
|
|
||||||
Encrypting data volumes using the BitLocker control panel interface works in a similar fashion to encryption of the operating system volumes. Users select **Turn on BitLocker** within the control panel to begin the BitLocker Drive Encryption wizard.
|
Encrypting data volumes using the BitLocker control panel interface works in a fashion similar to encryption of the operating system volumes. Users select **Turn on BitLocker** within the control panel to launch the BitLocker Drive Encryption wizard.
|
||||||
Unlike for operating system volumes, data volumes are not required to pass any configuration tests for the wizard to proceed. Upon launching the wizard, a choice of authentication methods to unlock the drive appears. The available options are **password** and **smart card** and **automatically unlock this drive on this computer**. Disabled by default, the latter option will unlock the data volume without user input when the operating system volume is unlocked.
|
Unlike for operating system volumes, data volumes are not required to pass any configuration tests for the wizard to proceed. Upon launching the wizard, a choice of authentication methods to unlock the drive appears. The available options are **password** and **smart card** and **automatically unlock this drive on this computer**. Disabled by default, the latter option will unlock the data volume without user input when the operating system volume is unlocked.
|
||||||
|
|
||||||
After selecting the desired authentication method and choosing **Next**, the wizard presents options for storage of the recovery key. These options are the same as for operating system volumes.
|
After selecting the desired authentication method and choosing **Next**, the wizard presents options for storage of the recovery key. These options are the same as for operating system volumes.
|
||||||
With the recovery key saved, selecting **Next** in the wizard will show available options for encryption. These options are the same as for operating system volumes; **used disk space only** and **full drive encryption**. If the volume being encrypted is new or empty, it is recommended that used space only encryption is selected.
|
With the recovery key saved, selecting **Next** in the wizard will show available options for encryption. These options are the same as for operating system volumes—**used disk space only** and **full drive encryption**. If the volume being encrypted is new or empty, it is recommended that **used disk space only** is selected.
|
||||||
|
|
||||||
With an encryption method chosen, a final confirmation screen displays before beginning the encryption process. Selecting **Start encrypting** will begin encryption.
|
With an encryption method chosen, a final confirmation screen is displayed before the encryption process begins. Selecting **Start encrypting** will begin encryption.
|
||||||
|
|
||||||
Encryption status displays in the notification area or within the BitLocker control panel.
|
Encryption status displays in the notification area or within the BitLocker control panel.
|
||||||
|
|
||||||
@ -130,7 +129,7 @@ Encryption status displays in the notification area or within the BitLocker cont
|
|||||||
|
|
||||||
There is a new option for storing the BitLocker recovery key using the OneDrive. This option requires that computers are not members of a domain and that the user is using a Microsoft Account. Local accounts do not give the option to utilize OneDrive. Using the OneDrive option is the default, recommended recovery key storage method for computers that are not joined to a domain.
|
There is a new option for storing the BitLocker recovery key using the OneDrive. This option requires that computers are not members of a domain and that the user is using a Microsoft Account. Local accounts do not give the option to utilize OneDrive. Using the OneDrive option is the default, recommended recovery key storage method for computers that are not joined to a domain.
|
||||||
|
|
||||||
Users can verify the recovery key was saved properly by checking their OneDrive for the BitLocker folder which is created automatically during the save process. The folder will contain two files, a readme.txt and the recovery key. For users storing more than one recovery password on their OneDrive,
|
Users can verify whether the recovery key was saved properly by checking their OneDrive for the BitLocker folder which is created automatically during the save process. The folder will contain two files, a readme.txt and the recovery key. For users storing more than one recovery password on their OneDrive,
|
||||||
they can identify the required recovery key by looking at the file name. The recovery key ID is appended to the end of the file name.
|
they can identify the required recovery key by looking at the file name. The recovery key ID is appended to the end of the file name.
|
||||||
|
|
||||||
### Using BitLocker within Windows Explorer
|
### Using BitLocker within Windows Explorer
|
||||||
@ -139,7 +138,7 @@ Windows Explorer allows users to launch the BitLocker Drive Encryption wizard by
|
|||||||
|
|
||||||
## <a href="" id="bkmk-dep2"></a>Down-level compatibility
|
## <a href="" id="bkmk-dep2"></a>Down-level compatibility
|
||||||
|
|
||||||
The following table shows the compatibility matrix for systems that have been BitLocker enabled then presented to a different version of Windows.
|
The following table shows the compatibility matrix for systems that have been BitLocker-enabled and then presented to a different version of Windows.
|
||||||
|
|
||||||
Table 1: Cross compatibility for Windows 10, Windows 8.1, Windows 8, and Windows 7 encrypted volumes
|
Table 1: Cross compatibility for Windows 10, Windows 8.1, Windows 8, and Windows 7 encrypted volumes
|
||||||
|
|
||||||
@ -188,7 +187,7 @@ Table 1: Cross compatibility for Windows 10, Windows 8.1, Windows 8, and Window
|
|||||||
## <a href="" id="bkmk-dep3"></a>Encrypting volumes using the manage-bde command line interface
|
## <a href="" id="bkmk-dep3"></a>Encrypting volumes using the manage-bde command line interface
|
||||||
|
|
||||||
Manage-bde is a command-line utility that can be used for scripting BitLocker operations. Manage-bde offers additional options not displayed in the BitLocker control panel. For a complete list of the options, see [Manage-bde](https://technet.microsoft.com/library/ff829849.aspx).
|
Manage-bde is a command-line utility that can be used for scripting BitLocker operations. Manage-bde offers additional options not displayed in the BitLocker control panel. For a complete list of the options, see [Manage-bde](https://technet.microsoft.com/library/ff829849.aspx).
|
||||||
Manage-bde offers a multitude of wider options for configuring BitLocker. This means that using the command syntax may require care and possibly later customization by the user. For example, using just the `manage-bde -on` command on a data volume will fully encrypt the volume without any authenticating protectors. A volume encrypted in this manner still requires user interaction to turn on BitLocker protection, even though the command successfully completed because an authentication method needs to be added to the volume for it to be fully protected.
|
Manage-bde offers a multitude of wider options for configuring BitLocker. This means that using the command syntax may require care and, possibly later, customization by the user. For example, using just the `manage-bde -on` command on a data volume will fully encrypt the volume without any authenticating protectors. A volume encrypted in this manner still requires user interaction to turn on BitLocker protection, even though the command successfully completed, because an authentication method needs to be added to the volume for it to be fully protected.
|
||||||
Command line users need to determine the appropriate syntax for a given situation. The following section covers general encryption for operating system volumes and data volumes.
|
Command line users need to determine the appropriate syntax for a given situation. The following section covers general encryption for operating system volumes and data volumes.
|
||||||
|
|
||||||
### Operating system volume
|
### Operating system volume
|
||||||
@ -205,7 +204,7 @@ This command returns the volumes on the target, current encryption status and vo
|
|||||||
|
|
||||||
**Enabling BitLocker without a TPM**
|
**Enabling BitLocker without a TPM**
|
||||||
|
|
||||||
For example, suppose that you want to enable BitLocker on a computer without a TPM chip. To properly enable BitLocker for the operating system volume, you will need to use a USB flash drive as a startup key to boot (in this example, the drive letter E). You would first create the startup key needed for BitLocker using the –protectors option and save it to the USB drive on E: and then begin the encryption process. You will need to reboot the computer when prompted to complete the encryption process.
|
For example, suppose that you want to enable BitLocker on a computer without a TPM chip. To properly enable BitLocker for the operating system volume, you will need to use a USB flash drive as a startup key to boot (in this example, the drive letter E). You would first create the startup key needed for BitLocker using the –protectors option, save it to the USB drive on E: and begin the encryption process. You will need to reboot the computer when prompted to complete the encryption process.
|
||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
manage-bde –protectors -add C: -startupkey E:
|
manage-bde –protectors -add C: -startupkey E:
|
||||||
@ -218,17 +217,17 @@ It is possible to encrypt the operating system volume without any defined protec
|
|||||||
|
|
||||||
`manage-bde -on C:`
|
`manage-bde -on C:`
|
||||||
|
|
||||||
This will encrypt the drive using the TPM as the protector. If a user is unsure of the protector for a volume, they can use the -protectors option in manage-bde to list this information with the command:
|
This will encrypt the drive using the TPM as the protector. If users are unsure of the protector for a volume, they can use the -protectors option in manage-bde to list this information by executing the following command:
|
||||||
|
|
||||||
`manage-bde -protectors -get <volume>`
|
`manage-bde -protectors -get <volume>`
|
||||||
|
|
||||||
**Provisioning BitLocker with two protectors**
|
**Provisioning BitLocker with two protectors**
|
||||||
|
|
||||||
Another example is a user on non-TPM hardware who wishes to add a password and SID-based protector to the operating system volume. In this instance, the user adds the protectors first. This is done with the command:
|
Another example is a user on a non-TPM hardware who wishes to add a password and SID-based protector to the operating system volume. In this instance, the user adds the protectors first. This is done with the command:
|
||||||
|
|
||||||
`manage-bde -protectors -add C: -pw -sid <user or group>`
|
`manage-bde -protectors -add C: -pw -sid <user or group>`
|
||||||
|
|
||||||
This command will require the user to enter and then confirm the password protector before adding them to the volume. With the protectors enabled on the volume, the user just needs to turn BitLocker on.
|
This command will require the user to enter and then confirm the password protectors before adding them to the volume. With the protectors enabled on the volume, the user just needs to turn BitLocker on.
|
||||||
|
|
||||||
### Data volume
|
### Data volume
|
||||||
|
|
||||||
@ -374,15 +373,15 @@ Windows PowerShell cmdlets provide an alternative way to work with BitLocker. Us
|
|||||||
</table>
|
</table>
|
||||||
|
|
||||||
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 are encrypting prior to running Windows PowerShell cmdlets.
|
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 are 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-BitLocker</code> volume cmdlet. The output from this cmdlet displays information on the volume type, protectors, protection status, and other useful information.
|
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-BitLocker</code> volume cmdlet. The output from this cmdlet displays information on the volume type, protectors, protection status and other useful information.
|
||||||
Occasionally, all protectors may not be shown when using <b>Get-BitLockerVolume</b> due to lack of space in the output display. If you do not see all of the protectors for a volume, you can use the Windows PowerShell pipe command (|) to format a listing of the protectors.
|
Occasionally, all protectors may not be shown when using <b>Get-BitLockerVolume</b> due to lack of space in the output display. If you do not see all of the protectors for a volume, you can use the Windows PowerShell pipe command (|) to format a listing of the protectors.
|
||||||
|
|
||||||
> **Note:** In the event that there are more than four protectors for a volume, the pipe command may run out of display space. For volumes with more than four protectors, use the method described in the section below to generate a listing of all protectors with protector ID.
|
> **Note:** In the event that there are more than four protectors for a volume, the pipe command may run out of display space. For volumes with more than four protectors, use the method described in the section below to generate a listing of all protectors with protector ID.
|
||||||
|
|
||||||
`Get-BitLockerVolume C: | fl`
|
`Get-BitLockerVolume C: | fl`
|
||||||
|
|
||||||
If you wanted to remove the existing protectors prior to provisioning BitLocker on the volume, you can utilize the `Remove-BitLockerKeyProtector` cmdlet. Accomplishing this requires the GUID associated with the protector to be removed.
|
If you want to remove the existing protectors prior to provisioning BitLocker on the volume, you can utilize the `Remove-BitLockerKeyProtector` cmdlet. Accomplishing this requires the GUID associated with the protector to be removed.
|
||||||
A simple script can pipe the values of each **Get-BitLockerVolume** return out to another variable as seen below:
|
A simple script can pipe out the values of each **Get-BitLockerVolume** return to another variable as seen below:
|
||||||
```powershell
|
```powershell
|
||||||
$vol = Get-BitLockerVolume
|
$vol = Get-BitLockerVolume
|
||||||
$keyprotectors = $vol.KeyProtector
|
$keyprotectors = $vol.KeyProtector
|
||||||
@ -392,12 +391,12 @@ Using this information, we can then remove the key protector for a specific volu
|
|||||||
```powershell
|
```powershell
|
||||||
Remove-BitLockerKeyProtector <volume>: -KeyProtectorID "{GUID}"
|
Remove-BitLockerKeyProtector <volume>: -KeyProtectorID "{GUID}"
|
||||||
```
|
```
|
||||||
> **Note:** The BitLocker cmdlet requires the key protector GUID enclosed in quotation marks to execute. Ensure the entire GUID, with braces, is included in the command.
|
> **Note:** The BitLocker cmdlet requires the key protector GUID (enclosed in quotation marks) to execute. Ensure the entire GUID, with braces, is included in the command.
|
||||||
|
|
||||||
### Operating system volume
|
### Operating system volume
|
||||||
|
|
||||||
Using the BitLocker Windows PowerShell cmdlets is similar to working with the manage-bde tool for encrypting operating system volumes. Windows PowerShell offers users a lot of flexibility. For example, users can add the desired protector as part command for encrypting the volume. Below are examples of common user scenarios and steps to accomplish them using the BitLocker cmdlets for Windows PowerShell.
|
Using the BitLocker Windows PowerShell cmdlets is similar to working with the manage-bde tool for encrypting operating system volumes. Windows PowerShell offers users a lot of flexibility. For example, users can add the desired protector as part command for encrypting the volume. Below are examples of common user scenarios and steps to accomplish them using the BitLocker cmdlets for Windows PowerShell.
|
||||||
To enable BitLocker with just the TPM protector. This can be done using the command:
|
To enable BitLocker with just the TPM protector, execute the following command:
|
||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
Enable-BitLocker C:
|
Enable-BitLocker C:
|
||||||
@ -409,16 +408,16 @@ Enable-BitLocker C: -StartupKeyProtector -StartupKeyPath <path> -SkipHardwareTes
|
|||||||
```
|
```
|
||||||
### Data volume
|
### Data volume
|
||||||
|
|
||||||
Data volume encryption using Windows PowerShell is the same as for operating system volumes. You should add the desired protectors prior to encrypting the volume. The following example adds a password protector to the E: volume using the variable $pw as the password. The $pw variable is held as a SecureString value to store the user defined password. Last, encryption begins.
|
Data volume encryption using Windows PowerShell is the same as for operating system volumes. You should add the desired protectors prior to encrypting the volume. The following example adds a password protector to the E: volume using the variable $pw as the password. The $pw variable is held as a SecureString value to store the user-defined password. Last, encryption begins.
|
||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
$pw = Read-Host -AsSecureString
|
$pw = Read-Host -AsSecureString
|
||||||
<user inputs password>
|
<user inputs password>
|
||||||
Enable-BitLockerKeyProtector E: -PasswordProtector -Password $pw
|
Enable-BitLockerKeyProtector E: -PasswordProtector -Password $pw
|
||||||
```
|
```
|
||||||
### Using a SID based protector in Windows PowerShell
|
### Using an SID-based protector in Windows PowerShell
|
||||||
|
|
||||||
The ADAccountOrGroup protector is an Active Directory SID-based protector. This protector can be added to both operating system and data volumes, although it does not unlock operating system volumes in the pre-boot environment. The protector requires the SID for the domain account or group to link with the protector. BitLocker can protect a cluster-aware disk by adding a SID-based protector for the Cluster Name Object (CNO) that lets the disk properly failover and be unlocked to any member computer of the cluster.
|
The ADAccountOrGroup protector is an Active Directory SID-based protector. This protector can be added to both operating system and data volumes, although it does not unlock operating system volumes in the pre-boot environment. The protector requires the SID for association with a domain account or group. BitLocker can protect a cluster-aware disk by adding a SID-based protector for the Cluster Name Object (CNO) that lets the disk properly failover and be unlocked to any member computer of the cluster.
|
||||||
|
|
||||||
>**Warning:** The SID-based protector requires the use of an additional protector (such as TPM, PIN, recovery key, etc.) when used on operating system volumes.
|
>**Warning:** The SID-based protector requires the use of an additional protector (such as TPM, PIN, recovery key, etc.) when used on operating system volumes.
|
||||||
|
|
||||||
@ -434,14 +433,14 @@ get-aduser -filter {samaccountname -eq "administrator"}
|
|||||||
```
|
```
|
||||||
> **Note:** Use of this command requires the RSAT-AD-PowerShell feature.
|
> **Note:** Use of this command requires the RSAT-AD-PowerShell feature.
|
||||||
>
|
>
|
||||||
> **Tip:** In addition to the Windows PowerShell command above, information about the locally logged on user and group membership can be found using: WHOAMI /ALL. This does not require the use of additional features.
|
> **Tip:** In addition to the Windows PowerShell command above, information about the locally logged-on user and group membership can be found using: WHOAMI /ALL. This does not require the use of additional features.
|
||||||
|
|
||||||
In the example below, the user wishes to add a domain SID based protector to the previously encrypted operating system volume. The user knows the SID for the user account or group they wish to add and uses the following command:
|
In the example below, the user wishes to add a domain SID-based protector to the previously encrypted operating system volume. The user knows the SID for the user account or group they wish to add and uses the following command:
|
||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
Add-BitLockerKeyProtector C: -ADAccountOrGroupProtector -ADAccountOrGroup "<SID>"
|
Add-BitLockerKeyProtector C: -ADAccountOrGroupProtector -ADAccountOrGroup "<SID>"
|
||||||
```
|
```
|
||||||
> **Note:** Active Directory-based protectors are normally used to unlock Failover Cluster enabled volumes.
|
> **Note:** Active Directory-based protectors are normally used to unlock Failover Cluster-enabled volumes.
|
||||||
|
|
||||||
## <a href="" id="bkmk-dep5"></a> Checking BitLocker status
|
## <a href="" id="bkmk-dep5"></a> Checking BitLocker status
|
||||||
|
|
||||||
@ -458,7 +457,7 @@ Checking BitLocker status with the control panel is the most common method used
|
|||||||
| **Suspended** | BitLocker is suspended and not actively protecting the volume |
|
| **Suspended** | BitLocker is suspended and not actively protecting the volume |
|
||||||
| **Waiting for Activation**| BitLocker is enabled with a clear protector key and requires further action to be fully protected|
|
| **Waiting for Activation**| BitLocker is enabled with a clear protector key and requires further action to be fully protected|
|
||||||
|
|
||||||
If a drive is pre-provisioned with BitLocker, a status of "Waiting for Activation" displays with a yellow exclamation icon on the volume. This status means that there was only a clear protector used when encrypting the volume. In this case, the volume is not in a protected state and needs to have a secure key added to the volume before the drive is fully protected. Administrators can use the control panel, manage-bde tool, or WMI APIs to add an appropriate key protector. Once complete, the control panel will update to reflect the new status.
|
If a drive is pre-provisioned with BitLocker, a status of "Waiting for Activation" displays with a yellow exclamation icon on the volume. This status means that there was only a clear protector used when encrypting the volume. In this case, the volume is not in a protected state and needs to have a secure key added to it before the drive is fully protected. Administrators can use the control panel, manage-bde tool, or WMI APIs to add an appropriate key protector. Once complete, the control panel will update to reflect the new status.
|
||||||
Using the control panel, administrators can choose **Turn on BitLocker** to start the BitLocker Drive Encryption wizard and add a protector, like PIN for an operating system volume (or password if no TPM exists), or a password or smart card protector to a data volume.
|
Using the control panel, administrators can choose **Turn on BitLocker** to start the BitLocker Drive Encryption wizard and add a protector, like PIN for an operating system volume (or password if no TPM exists), or a password or smart card protector to a data volume.
|
||||||
The drive security window displays prior to changing the volume status. Selecting **Activate BitLocker** will complete the encryption process.
|
The drive security window displays prior to changing the volume status. Selecting **Activate BitLocker** will complete the encryption process.
|
||||||
|
|
||||||
@ -488,7 +487,7 @@ This command will display information about the encryption method, volume type,
|
|||||||
|
|
||||||
### Provisioning BitLocker during operating system deployment
|
### Provisioning BitLocker during operating system deployment
|
||||||
|
|
||||||
Administrators can enable BitLocker prior to operating system deployment from the Windows Pre-installation Environment. This is done with a randomly generated clear key protector applied to the formatted volume and encrypting the volume prior to running the Windows setup process. If the encryption uses the Used Disk Space Only option described later in this document, this step takes only a few seconds and incorporates well into regular deployment processes.
|
Administrators can enable BitLocker prior to operating system deployment from the Windows Pre-installation environment. This is done with a randomly generated clear key protector applied to the formatted volume and by encrypting the volume prior to running the Windows setup process. If the encryption uses the **Used Disk Space Only** option described later in this document, this step takes only a few seconds and incorporates well into regular deployment processes.
|
||||||
|
|
||||||
### Decrypting BitLocker volumes
|
### Decrypting BitLocker volumes
|
||||||
|
|
||||||
@ -496,12 +495,12 @@ Decrypting volumes removes BitLocker and any associated protectors from the volu
|
|||||||
|
|
||||||
### Decrypting volumes using the BitLocker control panel applet
|
### Decrypting volumes using the BitLocker control panel applet
|
||||||
|
|
||||||
BitLocker decryption using the control panel is done using a Wizard. The control panel can be called from Windows Explorer or by opening the directly. After opening the BitLocker control panel, users will select the Turn off BitLocker option to begin the process.
|
BitLocker decryption using the control panel is done using a wizard. The control panel can be called from Windows Explorer or by opening it directly. After opening the BitLocker control panel, users will select the **Turn off BitLocker** option to begin the process.
|
||||||
Once selected, the user chooses to continue by clicking the confirmation dialog. With Turn off BitLocker confirmed, the drive decryption process will begin and report status to the control panel.
|
Once selected, the user chooses to continue by clicking the confirmation dialog. With **Turn off BitLocker** confirmed, the drive decryption process will begin and report status to the control panel.
|
||||||
|
|
||||||
The control panel does not report decryption progress but displays it in the notification area of the task bar. Selecting the notification area icon will open a modal dialog with progress.
|
The control panel does not report decryption progress but displays it in the notification area of the task bar. Selecting the notification area icon will open a modal dialog with progress.
|
||||||
|
|
||||||
Once decryption is complete, the drive will update its status in the control panel and is available for encryption.
|
Once decryption is complete, the drive will update its status in the control panel and becomes available for encryption.
|
||||||
|
|
||||||
### Decrypting volumes using the manage-bde command line interface
|
### Decrypting volumes using the manage-bde command line interface
|
||||||
|
|
||||||
@ -510,14 +509,14 @@ Decrypting volumes using manage-bde is very straightforward. Decryption with man
|
|||||||
```powershell
|
```powershell
|
||||||
manage-bde -off C:
|
manage-bde -off C:
|
||||||
```
|
```
|
||||||
This command disables protectors while it decrypts the volume and removes all protectors when decryption is complete. If a user wishes to check the status of the decryption, they can use the following command:
|
This command disables protectors while it decrypts the volume and removes all protectors when decryption is complete. If users wish to check the status of the decryption, they can use the following command:
|
||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
manage-bde -status C:
|
manage-bde -status C:
|
||||||
```
|
```
|
||||||
### Decrypting volumes using the BitLocker Windows PowerShell cmdlets
|
### Decrypting volumes using the BitLocker Windows PowerShell cmdlets
|
||||||
|
|
||||||
Decryption with Windows PowerShell cmdlets is straightforward, similar to manage-bde. The additional advantage Windows PowerShell offers is the ability to decrypt multiple drives in one pass. In the example below, the user has three encrypted volumes, which they wish to decrypt.
|
Decryption with Windows PowerShell cmdlets is straightforward, similar to manage-bde. The additional advantage Windows PowerShell offers is the ability to decrypt multiple drives in one pass. In the example below, the users have three encrypted volumes, which they wish to decrypt.
|
||||||
|
|
||||||
Using the Disable-BitLocker command, they can remove all protectors and encryption at the same time without the need for additional commands. An example of this command is:
|
Using the Disable-BitLocker command, they can remove all protectors and encryption at the same time without the need for additional commands. An example of this command is:
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user