VMs created before recreation will not boot due to missing KMS Key

Products

• VMware vCenter Server

Issue/Introduction

VMs do not recognize KMS key on current vCenter.

Environment

Corrected vm's to VMs as requested.

Cause

Current VMs were created & registered to old vCenter. 

Resolution

Retrieve old KMS key from previous vCenter & reregister VMs after applying old KMS key to new vCenter. 

• Power down the current vCenter, power up the previous vCenter & backup the key. When applying the old key just set it as the default. 
• Re-register the vm's to the new vCenter. 
• Re-encrypt VMs:

• In the vSphere client, select the VMs that were previously encrypted with the native key provider.

• Right-click the selected VMs and choose "VM Policies" > "Re-Encrypt".

• Follow the on-screen prompts to re-encrypt the virtual machines.

Additional Information

NOTE: Always ensure a backup is available of encryption keys.

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/configuring-and-managing-vsphere-native-key-provider/recovering-a-vsphere-native-key-provider/restore-a-vsphere-native-key-provider-using-the-vsphere-client.html 

https://www.vmware.com/docs/vsphere-native-key-provider-nkp-questions-answers