Restored (moved) Win7 VM requiring migration - Breaks AD Trust

I am attempting to restore a backup of a Windows 7 VM in Parallels 7 (7.0.1.15107 Rev 796624) on my Mac.

I backed it up using Carbon Copy Cloner (so a copy from disk to disk) and restored it by copying the .pvm back to the ~/Documents/Parallels/ directory with my other machines.

I used this machine roughly a month ago on this Mac with this build of parallels with no issues, but now each time I try to run it asks me if it was Moved or Copied (I have tried both), and that the machine requires an increase to the Video Memory (256MB is not enough for 3D effects) and then runs through a +20min Migration process and re-installation of the Parallels tools.

When the migration is complete it reboots and lets me get to the log-in prompt, but now the trust relationship with the AD is broken - I assume because the migration process makes it look like a "new" computer with the same host information as the "old" computer - but its really the same computer...

I have been able to backup and move a couple of other machines no problem (including a Win7 VM) but this one seems to be requiring the migration for some reason.

Is there away around this migration?

Remember, it was last used on this computer in this version of parallels so "nothing" has changed since I last used it.

 

Most likely something is indeed different, maybe the assumption that everything is "the same" is incorrect. What's the difference? I don't know, from the AD perspective, maybe it's something as simple as a different ethernet address (MAC).

 

I'm sure the migration does end up creating a different MAC or the like and that's what breaks the AD trust, I just can't figure out why it's requiring the migration in the first place and that's what I'm trying to get around.

 

If you know the original MAC address you can change it in the VM settings (Hardware > Network ).

 

Understood - but that's the problem, I don't know what it was before and I don't understand the reasons that a VM from the same version would require migration to open after restore.

I could appreciate if it was an old pvm from PD 6 or something, but it was created on this Mac with Parallels Transporter and used multiple times before I backed it up and many times after the backup. But when I restore this backup is when the migration occurs.

I was hoping I was missing something simple, I guess I'll open a case.

 

There's likely a reason for the migration process to occur, something may indeed be different with that VM to trigger the migration.