Here's the problem.
From the perspective of the operating system post migration, it's got entirely new parts. That's why yours is lit up asking to be activated.
Windows, and I'll offer this authoritatively for XP and hesitantly for Windows Vista/7/2008, has ten items it monitors for WPA - these items are devices unique to individual physical machines, some of which translate to the virtual world at diffferent levels - MAC address of NIC (if installed) SCSI controller serial numbers, VSN of processor, etc. The details of the list are easily found on the internet if you search. These change when you migrate/clone a VM, host specific. Are you running mixed processors in your cluster?
When you change any 3 of these items, Windows will decide it's being messed with and light up the activation request/warning that you are seeing.
How it knows is Windows makes a hash of these numbers and identifiers, and it keeps this hash in the c:\windows\system32 directoy as wpa.dlb (I think on the extension, been a while since I looked this up) and wpa.bak - the backup to the dlb file. Deleting these files will not help you. There are some antics you can play here that may or may not work, but it depends on your system and other variables (use google.).
Quite frankly, if you have legit licenses, the easiest route forward is to just let the VMs activate themselves. If you've burned through your authorized number of activations for that key and believe you are still legit, phone it in and explain the situation to M$.
My .02. Good luck trooper.
- abe
Integritas!
Abe Lister
Just some guy that loves to virtualize
==============================
Ain't gonna lie. I like points. If what I'm saying is something useful to you, consider sliding me some points for it!
