P2V ramblings with OEM server installation

Windows OEM license installed on physical Server can’t really be P2V. Or yes?

It just came it as an evidence for me because it already happened to me in my production environment several times, but it’s not evident for everybody. So just a little remember. Especially when you are just started learning about virtualization and P2V.

When you plan to do a P2V on a server, just check the Licensing model which was used for an installation. There could be a situation when you came across a server at your client’s site, and your client wants you to use P2V and virtualize this server.

Basically what happens after you successfully P2V the server, the Microsoft OS asks for an activation. That’s when the thinks will start to became interesting:

If you use the OEM license key – it won’t work.

If you use the VL license key – it won’t work either (OEM CD media is not the same as the VL media.)

What are the choices for you then?

01. - Doing a fresh install of the OS inside vCenter using a Volume License key (no P2V then..) and reinstalling and configuring all the application that were installed etc…….

02. - You can also run an in-place upgrade after you run the P2V by using VL media and when prompted for the product key,  use a Volume License key.

Don’t forget to uninstall any old hardware left in the VM after the P2V conversion succeed and also the software for managing hardware being used on the physical box. This speeds the VM

I leave up to you what is the best solution for you in your situation. There are some pros and cons …..

Technorati Tags: P2V on OEM, VmWare Converter, VMware P2V, vSphere

Other posts from Server Virtualization

• Adding second service console via CLI
• Disable web access on VMware vCenter
• VMware ESX - Configuration of Service console via CLI
• Basic VMware ESX CLI networking commands
• How to change the default location of updates in vCenter
• Did you know that ESX 3.5 general support will end in less than 90 days?
• Starwind iSCSI HA Connection to ESX Server
• See a list of Storage Array Type Plugins on ESX Server
• New whitepaper released on PVSCSI
• Enable Jumbo Frames in ESXi 4
• How-to troubleshoot iSCSI connection to your SAN
• Starwind with ISCSI SAN Software can do High Availability for you...
• Overview Video from the new vSphere Pro video training from Train Signal
• New upgrade webpage for ESXi 4 pushes us to the right direction?
• You know how to collect diag information when your ESXi does PSOD?
• Use PVSCSI or not for lower intensive workloads
• Hardening guides for vSphere 4
• NTLDR missing - silly but can happend
• How To Shrink VMware Virtual Disk Files and disable shrinking
• vSphere Quick Start guide bonus download..
• ESXi - the past, the present and the future
• Farm commander - management tool for VI and TS or Citrix Farms
• How to collect log information from vCenter Server 4
• How to know where is my VM if vCenter is down?
• New patches for ESX 4 and ESXi 4
• Use VMware Converter to import 3rd party VMs, for example Virtual Iron's VMs
• Windows XP installation as a VM - trouble to see the disk or not?
• Vmware HCL for ESXi 4
• Time keeping for Windows VM's best practices
• Virtu-Al releasing 3rd update of PowerPack