Moving VM to new Mac in an MDM environment

Situation: Migration from M1 to M4 Mac (update from v.18 to v.20 of Parallels) both under MDM
Host OS: Sequoia
VM OS: Windows 11

Our team recently got a laptop refresh. We are standard version users. The information on moving a VM from one mac to another includes information about copying over the TPM chip keychain item, but they are convoluted, especially for an MDM setup where you can't access iCloud Keychain, or some of the migration assistant stuff. As a result I tried to recreate the TPM on the new mac using keychain access (having copied over all of the parameters manually) but am still getting "... the TMP-related info cannot be read." The VM does bootup and work despite the warning, but it's annoying and I do wonder if eventually it will stop working.

I don't have access to the older Mac.

I could just create a new VM, but the existing Windows instance is activated and has the settings and tweaks I've built up over the last few years. I sign in with a work-based account so I can't use any Microsoft Account based tools to backup and restore my PC. Any recommendations for this, or is it a "if it ain't broke, don't fix it" situation?

 

Moving a virtual machine (VM) to a new Mac in a managed (MDM) environment needs a bit of planning. Here's what to keep in mind:

1. Check MDM Policies:
   Before moving anything, ensure the MDM on the new Mac allows virtualization tools like VMware Fusion or Parallels. Some organizations block certain apps.
   
   
2. Copy the VM Properly:
   Use an external drive or network transfer to copy the entire VM bundle (usually ends in .vmwarevm or similar). Make sure the VM is shut down (not suspended) before copying.
   
   
3. Install Required Software:
   On the new Mac, install the same VM software version. If you're switching to an Apple Silicon Mac, note that x86-based VMs won't work unless they support ARM architecture.
   
   
4. Reconfigure Network Settings:
   Some VM network settings may break in the new setup. Recheck NAT/bridge modes and IP addresses.
   
   
5. Re-enroll if Needed:
   If your VM interacts with company systems or is enrolled in MDM itself, you may need to re-enroll it or inform your IT team.
   
   
6. Test Everything:
   Once moved, start the VM and test apps, connectivity, and performance to make sure everything works as expected.
   

 

Thanks for your response, but it does not address the primary question which is about transferring the TMP information. Parallels does address this in this article, however the instructions are convoluted and require you to have the older mac. I do a have a working copy of my VM on the new mac, but I want the annoying warning to go away if my instance is indeed stable, and if it's not I want to know what I can do to make my existing VM recognizes the TMP info I copied over from the old mac.