Also, when you do the conversion, and start Server for the first time, it will put you through the Activation wizard. You will probably have to call the Microsoft Licensing Center to have a phone rep give you an installation key so you can re-activate your software with your OEM key.
I think you can only virtualize on the same hardware since OEM is tied to the physical hardware. Not sure if OEM is allowed, but at the very least it has to be done on the same hardware. So there is no option to purchase copies of Windows and simply run the P2Vs? I'd like to avoid the hassle of having to rebuild 3 servers and then go through the pain and expense of re-installing the legacy applications and migrating the data.
I have one license for the Physical machine which basically can only run the Hyper-V role and 3 Virtual licenses I'm using two, so I can add one more. One of my goals in virtualizing is to move the applications off the old hardware it's running on to new hardware so I'll definitely have to deal with the OEM license being tied to the old hardware.
Thanks for your post. I'm glad to hear the MS licensing process would handle my situation as long as they are willing to offer us the option to allow virtualization. Now my other concern is for disaster planning. Ultimately, I want to have 2 VMware servers that could act as backups to each other. You are right, I'll have to talk to an MS licensing person to find out how this could be done.
I know if I were setting things up from scratch today, this wouldn't be such a pain. The process isn't all that difficult - you'll need to: Install ESXi on a decent brand-name server not all white boxes are compatible.
Install the converter of your choice on your workstation. Walk through the conversion. Power off the physical server. Power up the new Virtual server. A few notes: The conversion is run completely from your workstation. This is important, because the better your workstation the faster the conversion. It's all about the amount of data, but a decent estimation is about minutes per gig of data on the physical server.
That might even be a little high actually. It's rare that a conversion is perfect. Generally, you will need to reconfigure the networking once you've powered up the virtual guest.
If at all possible, I recommend the E network adapter in the virtual machine - I've found that to be the most reliable. You get some goofy issues with the Flexible adapter, which I think is the default.
Don't forget to install the VMware tools! These are a must for decent UI performance on the new VM guest. I could go into much more detail, but really before you do any of this, hop into VMware's site and dig around for infomration in the knowledgbase and communities - there's a ton of good info up there. Best of luck! If you want to avoid future limitations due to not being able to run the full version, it might be worth checking out VirtualBox.
That being said, I've never tried to convert a functioning physical server into a virtual machine of any variety, so I'm not sure how well it would work for your specific use case.
A thing to consider is the Windows license. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How convert physical windows server to virtual machine on box running ESXi for free?
Ask Question. Asked 11 years, 9 months ago. Active 11 years, 9 months ago. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article provides information about Windows Server support and answers some of the most common questions about running Windows Server on Microsoft Azure.
Microsoft ended extended support for Windows Server on July 14, If you are running Windows Server , this may put your applications and business at risk, since there may be no security or software updates.
You can still move a Windows Server VM to Azure, and receive assistance in troubleshooting issues that concern running Windows Server on Azure. However, this support is limited to issues that don't require OS-level troubleshooting or patch. Machines running Windows will no longer receive Microsoft support and may not receive further security updates. Additionally, many compliance requirements include being on a currently supported operating system.
Migrating your applications to Azure instances running a newer version of Windows Server is the recommended approach to ensure that you are effectively leveraging the flexibility and reliability of the Azure cloud. Pre-configured images with different combinations of Windows and SQL Server are available in the Marketplace and enable you to run any compatible solution on our cost-effective, high-performance, reliable cloud computing platform. For more information, see Windows Server migration strategy.
0コメント