An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
How to P2V a Physical Windows server?
This is a planning to do a P2V conversion on few old MS Windows 2003 OEM servers. I know that I can use VMware convertor to do the conversion. But, how about the server license? can these OEM server works as VM with the oem license? As I heard that a product key is prompting upon the first bootup, and it normal won't accept the OEM product key. Does this mean that I have to change by upgrading to a volume license?
Please help!
Please help!
Asked:
Who is Participating?
here is the deal.
the OEM license is technically only valid on the OEM hardware.
Your getting bit because the P2V process changes the hardware and the OS picks that up.
Microsoft has been cool about this: check out the following URL. MS gives you keys to get yourself sorted when you run into this.
https://technet.microsoft.com/en-us/library/dd727762.aspx
the OEM license is technically only valid on the OEM hardware.
Your getting bit because the P2V process changes the hardware and the OS picks that up.
Microsoft has been cool about this: check out the following URL. MS gives you keys to get yourself sorted when you run into this.
https://technet.microsoft.com/en-us/library/dd727762.aspx
If you have a Microsoft Open License to cover this you can perform a P2V and perform a repair using the VLK disk and license.
Hi Matthew and Andrew,
I need to setup a test lab to really visualize the p2v process. I will only able to start this on next monday (23/2) due to lunar chinese new year long weekends.
I need to setup a test lab to really visualize the p2v process. I will only able to start this on next monday (23/2) due to lunar chinese new year long weekends.
Look at my videos and articles with screenshots P2Vs are often misunderstood and many think point and click some P2V can be others maybe more difficult see my FAQ.
Also, in support of what Andrew is saying, while much of the P2v can be simple, do not just "next" your way through. Google the settings if you not sure what they are.
Last but not least, shutdown any databases on the system, back the data up! Shutdown any application services that may be running (if you have anything funky going on). This way, when you initiate the process, your not dealing with any "live" files or open tables.
Granted, the process should not impact the source, but an ounce of prevention is worth a pound of cure.
Last but not least, shutdown any databases on the system, back the data up! Shutdown any application services that may be running (if you have anything funky going on). This way, when you initiate the process, your not dealing with any "live" files or open tables.
Granted, the process should not impact the source, but an ounce of prevention is worth a pound of cure.
Hi Andrew and Matthew,
Please see how I did the conversion, and moved it to the hyperv:
- Copy Disk2VHD folder into the C:\ drive
- Double-click the exe file to open the console
- Select a drive at a time, click Create to start the conversion
- Tick Volume Shadow Copy option; if failed, untick it to continue (Does this matter?)
On MS HyperV Manager, select to create new virtual machine and continue with the activities as follows:
- Select Edit to convert the disk to fixed disk
- Choose the values for vCPU, RAM, NIC
- Boot up the virtual machine, select to skip when prompted for Windows activation (as NIC not recognized)
- Select to insert the HyperV Integrated Services CD; proceed with the setup
- HyperV display, NIC, and other components are installed
- Configure the IP Addressing, and then reboot the system
- Upon rebooting, select to proceed with the Windows Activation via Internet connection; browse to C:\Windows\System32\oobe, and run “msoobe /A”
So far, I tried on 2 physical servers, and they can be converted and run as HyperV VMs without any problem. I think the most important part is, get ready the w2k3 R2 standard edition w/sp2 ISO VL (although they are not needed). In both cases, the original physical servers are installed with VL license, so no issue. The second important part is the NIC, as it wasn't identified until the hyperv integrated services are installed successfully.
Appreciate a lot with the guidance and link references to get the confusions un-rooted.
Please see how I did the conversion, and moved it to the hyperv:
- Copy Disk2VHD folder into the C:\ drive
- Double-click the exe file to open the console
- Select a drive at a time, click Create to start the conversion
- Tick Volume Shadow Copy option; if failed, untick it to continue (Does this matter?)
On MS HyperV Manager, select to create new virtual machine and continue with the activities as follows:
- Select Edit to convert the disk to fixed disk
- Choose the values for vCPU, RAM, NIC
- Boot up the virtual machine, select to skip when prompted for Windows activation (as NIC not recognized)
- Select to insert the HyperV Integrated Services CD; proceed with the setup
- HyperV display, NIC, and other components are installed
- Configure the IP Addressing, and then reboot the system
- Upon rebooting, select to proceed with the Windows Activation via Internet connection; browse to C:\Windows\System32\oobe, and run “msoobe /A”
So far, I tried on 2 physical servers, and they can be converted and run as HyperV VMs without any problem. I think the most important part is, get ready the w2k3 R2 standard edition w/sp2 ISO VL (although they are not needed). In both cases, the original physical servers are installed with VL license, so no issue. The second important part is the NIC, as it wasn't identified until the hyperv integrated services are installed successfully.
Appreciate a lot with the guidance and link references to get the confusions un-rooted.
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.
-
Course of the Month7 days, 20 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Some P2V with OEM licenses have been found to re-activate with no issues!
Microsoft will state this...
Original Equipment Manufacturers (OEM) versions
Note: Physical-to-virtual hard drive migration of a Windows installation is a valid function for customers with Software Assurance and full retail copies of Windows XP, Windows Vista, and Windows 7. Software Assurance provides users valuable benefits—please contact Microsoft Corporation for further information. Windows XP, Windows Vista and Windows 7 installed by Original Equipment Manufacturers (OEM) using OEM versions of these products may not be transferred to a virtual hard drive in accordance with Microsoft licensing terms.
Source
http://technet.microsoft.com/en-us/sysinternals/ee656415
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/A_3721-Can-I-transfer-my-OEM-version-of-Windows-to-another-PC.html
Best thing is to go ahead and try it, also Microsoft at the moment, are encouraging sites to move off Windows 2003, and move to Azure for FREE!