Vmware V center migration of VM to new ESXi Server causes windows reactivation

Hi

We tried doing a V center cold migration from a ESXi 4.0 Host on local storage to a ESXi 4.1 host with SAN storage.  (windows 2003 VM)

ESXi 4.0 running on Dell 2850

ESXi 4.1 running on Dell 2950


The cold migration worked fine, except that now I need to reactivate the windows license is this normal?

Error:  since windows was first activated on this computer the hardware on the computer has changed
pancho15Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
Danny McDanielClinical Systems AnalystCommented:
ESX doesn't mask all of the hardware details to the guests, so windows would see the change in the processor.  When you powered on the VM, did you get a question if you moved or copied the VM, too?  That would have changed the GUID depending upon how you answered it.

If you changed it to virtual hardware version 7, that would be another change that Windows would key off of.
0
 
pancho15Author Commented:
Well when I did the migration from within V center it didnt ask if I copied or moved the VM. I know you get this option if you copy the files manually.

I would have thought that if you do a miogration from within V center - it wouldnt cause this issue ?  Or did this happen because I had two different ESXi hosts (Dell 2850 and dell 2950)

I assume I wont have issues if I just reactivate?>
0
 
Paul SolovyovskySenior IT AdvisorCommented:
If you had moved it to the same hardware platform it wouldn't have asked to re-activate.  In this case you went from a P4 based CPU to an Core2 based CPU with Intel VT.  The Windows OS deemed this a critical enough change to ask for windows re-activation.
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
pancho15Author Commented:
anyone else any comments on reactivation when moving VM's
0
 
Paul SolovyovskySenior IT AdvisorCommented:
You are correct.  You will not have any issues after re-activating.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
There are enough differences between the host Dell 2850 and Dell 2950 two cause a Re-activation, because the hardware has changed. If you were going to keep both in the "farm", it's likely you would have issues using vMotion between them without using CPU Masks.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
one of the elements of Windows Activations is using the Processor Type and Serial Number, as this has now changed, this is likely to cause a re-activation.
0
 
bgoeringCommented:
Are you running a retail or OEM license on your Windows? If that is the case I am not surprised you are asked to reactivate. If it is an OEM license it shouldn't be on VMware to start with as that license is irrevokably tied to its original hardware. If it is a retail license you should be able to reactivate and run fine. However retail licenses still have some limits to how often it can be transferred.

I have not run into the reactivation issue using volume licenses, even going between AMD and Intel processor architectures. That licensing is what you should pursue if you need to have your VMs be portable between systems.

Good Luck
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and also technically if using vMotion or DRS you may want to check what Microsoft licensing model you have, because technically you'll need a license for every HOST you vmotion to in the farm. So if you have three ESX hosts in your VMware Cluster, a VM could be on one of three hosts = 3 Microsoft Server licenses.

It can be beneficial to license with the datacenter edition.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
a good article here to read through, although Microsoft have moved the License Calculators.

http://www.b3rg.nl/blog/blog-it/microsoft-server-2008-licensing-and-virtual-environments.html
0
 
CrunchedCommented:
Also read up about EVC - Enhanced VMotion Compatibility.  No need to license each host in a VMware cluster either.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.