Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions source/features/migrating-windows-vms-encrypted-with-bitlocker.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,16 @@ If the TPM isn’t available (e.g. due to hardware changes or if the disks have

## Recommended migration procedure

### Prerequisites

The Windows minion image, which Coriolis uses for the temporary worker VM that performs OS morphing, must have the BitLocker feature installed. Without it, the worker can't unlock the volume and OS morphing fails with a missing packages error.

```powershell
Install-WindowsFeature BitLocker
```

### Migration steps

A preconfigured BitLocker recovery password must be specified when initiating the Coriolis transfer. Coriolis will use it to unlock the OS drive during OS morphing, which is performed by a temporary worker VM on the destination cloud.

The following sample calls the WMI API through PowerShell to configure a BitLocker recovery password for the OS drive. Its output is easier to parse than that of the **manage-bde** command and more convenient to use as part of automated scripts. Follow these steps on the Windows instance that is about to be migrated.
Expand Down Expand Up @@ -52,12 +62,6 @@ When initiating the migration, specify the recovery password like so:

In order for the final VM to be able to launch, Coriolis suspends BitLocker during OS morphing. The final VM reconfigures the TPM protector and resumes BitLocker when booted for the first time, which occurs immediately after the OS morphing process.

**Important:** make sure that your Windows minion image has the BitLocker feature installed, otherwise it will not be able to unlock the volume.

```powershell
Install-WindowsFeature BitLocker
```

Feel free to remove the temporary key protector from the source and destination instances after completing the migration.

## Alternative Migration Methods
Expand Down
Loading