First published on TECHNET on Dec 14, 2017
Whenever I want to replace or reinstall a system which is used to run
virtual machines with a virtual trusted platform module
(vTPM), I’ve been facing a challenge: For hosts that are not part of a
, the new system does need to be authorized to run the VM.
Some time ago, I wrote a blog post focused on
running VMs with a vTPM on additional hosts
, but the approach highlighted there does not solve everything when the original host is decommissioned. The VMs can be started on the new host, but without the original owner certificates, you cannot change the list of allowed guardians anymore.
This blog post shows a way to export the information needed from the source host and import it on a destination host. Please note that this technique only works for
mode and not for a host that is part of a guarded fabric. You can check whether your host runs in local mode by running
. The property
as a value.
Exporting the default owner from the source host
The following script exports the necessary information of the default owner (”
“) on a host that is configured using local mode. When running the script on the source host, two certificates are exported: a signing certificate and an encryption certificate.
Importing the UntrustedGuardian on the new host
On the destination host, the following snippet creates a new guardian using the certificates that have been exported in the previous step.
Please note that importing the “UntrustedGuardian” on the new host has to be done before creating new VMs with a vTPM on this host — otherwise a new guardian with the same name will already be present and the creation with the PowerShell snippet above will fail.
With these two steps, you should be able to migrate all the necessary bits to keep your VMs with vTPM running in your dev/test environment. This approach can also be used to back up your owner certificates, depending on how these certificates have been created.