Create Windows Server 2012 R2 VM in Azure after Oct 2023

Question

I have just tried to create a Windows Server 2012 R2 VM in a developer subscription in Azure, but it appears Windows Server 2012 R2 is no longer available as an image.

I am aware it is EOL as of Oct 2023, but Microsoft are offering free extended support for three more years in Azure (see https://cloudblogs.microsoft.com/sqlserver/2021/07/14/know-your-options-for-sql-server-2012-and-windows-server-2012-end-of-support/), so surely it should still be available as a VM image?

We require 2012 R2 to create a development environment that matches our customers, who is still using 2012 R2, and can't use a more recent version. Is there a way to request an image for Windows Server 2012 R2, or will we have to create our own image to use?

Any advice much appreciated.

Answer 1

Hi,

Yes you are correct in this instance I will suggest you use your own custom built image, but I guess the responsibility of securing the servers will be on you as it EOL as of Oct23.

Also you can raise a support case with Microsoft to get a clarity in case there is an issue- https://azure.microsoft.com/en-ca/support/create-ticket/

Hope this helps.

JS

==

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

Answer 2

Thanks for confirming. After some trial and error I have been able to create a Windows Server 2012 R2 generalised image and use this to create a VM in Azure. For anyone else trying to do similar, the steps I used were:

1. Create the VM using Hyper-V (on Windows 10). I created a Gen 1, fixed size VHD. See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/create-virtual-machine.
2. Installed Windows Server 2012 R2 using an iso from Visual Studio downloads.
3. Enabled .net 3.5 feature that is required for SQL Server 2012. This needs to be done prior to apply any updates, otherwise it will fail.
4. Installed all important updates (restarting multiple times and checking again).
5. Prepared the VM for Azure, including installing virtual machine agent - see https://learn.microsoft.com/en-gb/azure/virtual-machines/windows/prepare-for-upload-vhd-image.
6. Uploaded the resulting VHD to Azure using powershell Add-AzVHD to create a managed disk - see https://learn.microsoft.com/en-gb/azure/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell#use-add-azvhd.
7. Created an Image Version (and version definition) in an Azure Compute Gallery from the managed disk - see https://learn.microsoft.com/en-gb/azure/virtual-machines/vm-generalized-image-version?tabs=portal%2Ccli2%2Ccli3%2Ccli4
8. Created a new VM using the new image version from the gallery.

One thing I've noticed is that the resulting VM seems to be missing the temporary disk (D:) even though it says one will be created and the instance (B4ms) is supposed to support one. I've not been able to find a resolution to that yet, but it's not critical.

The process is not straightforward by any means and the MS documentation doesn't help as there doesn't seems to be a set of concise steps anywhere, you just have to piece it all together from various places!

Answer 3

According to my experience, the quickest option to get a virtual machine in Azure running a particular OS you need is to create such a virtual machine on your desktop's/laptop's Hyper-V and then use the free V2V converter tool to push that VM directly into Azure. The routine is pretty simple and quick. You can check the following guide for details https://www.starwindsoftware.com/v2v-help/VMfromMicrosoftHyperVServertoMicrosoftAzure.html.