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 …..

Share

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

Other posts from Server Virtualization

• Create your own Provider Virtual Data Center
• Measure some perf benchs with VMark
• VMware partners with Symantec on ApplicationHA
• Andre Leibovici's Linked cloning storage calculator
• SIOC yes, but not in the SMB kit...
• Best practices KB on how-to install ESX 4.1 and vCenter
• Hyper-V and new linux integration tools
• How to Fix “Transaction log for database ‘VIM_VCDB’ is full” errors
• How to change from ACPI Multiprocessor HAL back to ACPI Uniprocessor HAL in Windows 2003
• AD Integration for ESXi 4.1
• vCenter converter with Hyper-V import
• Serial Port handling in ESXi 4.1
• Four memory optimization techniques available in vSphere 4.1
• Activating remote access via SSH in ESXi4.1
• vSphere Compatibility Matrixes
• 150 new features or enhancements in vSphere 4.1
• Personalized install of VMware tools
• VMware tools download from VMware Website
• How to change virtual SCSI controler
• Microsoft's patch for .NET breaks VI client connection