?
Solved

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

Posted on 2010-11-27
11
Medium Priority
?
1,180 Views
Last Modified: 2012-05-10
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
0
Comment
Question by:pancho15
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
  • 2
  • +3
11 Comments
 
LVL 16

Expert Comment

by:danm66
ID: 34224107
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
 

Author Comment

by:pancho15
ID: 34224145
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
 
LVL 42

Accepted Solution

by:
paulsolov earned 2000 total points
ID: 34224347
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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:pancho15
ID: 34224348
anyone else any comments on reactivation when moving VM's
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 34224349
You are correct.  You will not have any issues after re-activating.
0
 
LVL 123
ID: 34224815
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
 
LVL 123
ID: 34224820
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
 
LVL 28

Expert Comment

by:bgoering
ID: 34226981
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
 
LVL 123
ID: 34227138
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
 
LVL 123
ID: 34227142
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
 
LVL 5

Expert Comment

by:Crunched
ID: 34227782
Also read up about EVC - Enhanced VMotion Compatibility.  No need to license each host in a VMware cluster either.
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question