In this blog, I will walk you through the process of creating a clone or capturing an image of a virtual machine (VM) in Microsoft Azure.
A relatively typical task for an administrator is one where they replicate a VM with its current state and software in order to save time. Another benefit of this task is that the administrator knows the configuration is exactly the same as the original VM, which becomes incredibly useful when testing or ensuring security by design.
Learning how to create a clone or capture an image of a virtual machine in Azure will allow you to quickly deploy VM's from the gallery when you select images.
To create an image with both Windows and Linux, you need to prepare the virtual machine for what I call generalization. Then remove the identifiable bits of the virtual machine to Azure. There is a slightly different approach with Linux vs. Windows, but they do sort of the same thing.
In Windows, the tool to help us with generalization is called sysprep it is located in "system32/sysprep."
Click on ”Start” then ”Run” and just type ”sysprep” and the folder will pop up.
When sysprep executes, make sure the settings are ”OOBE (Out-Of-Box-Experience)” and the VM is set to “Shutdown.”
Once you click “OK”, the generalization with continue and the VM will show shutdown in the Azure Portal.
Let's stop here for an IMPORTANT note. Some applications or custom software installed on VM's can be affected by a sysprep. Please check this first. If you find out that you cannot sysprep the VM, you can still clone or replicate it. You can shutdown the VM, then delete the VM but keep the disks. In the storage account container where the VHD resides just copy it to another container.
Now head over to Virtual Machines again and click on "Images." At the top click “Create” and fill out the form to add an image of the VM you want to clone.
Next, select the VM now in a ”Shutdown” state and click “Capture.” This action will delete the original VM so if you want a copy use the method above to copy the Virtual Hard Disk (VHD).
With Linux in the SSH console run "sudo waagent –deprovision." This will remove the Azure Agent no matter what version is installed on the box.
Here is a list of what's done:
Now use PowerShell or Azure CLI to run "azure vm capture -t <your-virtual-machine-name> <new-image-name>" this will capture the image and add it to the image list in the Azure Portal and "azure vm image list."
Now you can see the image in the create new VM gallery as well.
Director of Magic
I am ready to share some strategies for restoring a SQL Azure database to SQL Server 2012 now that the Internal Eroror has been corrected.
SmartSearch users running Kentico CMS on Windows Azure may be experience a time-out error. By adjusting the web.config, the error should be removed.
Learn how to connect to Microsoft Azure Virtual Networks to other services like Azure Web Apps, Cloud Services, and even your own On-Premises Resources.
Unfortunately, cloud failures are not impossible, there are ways to plan for the best possible outcome.
RT @tmaund: How organizations are connecting their on-premises identities to Azure AD https://t.co/k22K6g1uA4
RT @msclouditpro: Time for Episode 40! – @ciphertxt and @benstegink go over some of the big @Office365 News for November 2017 - #Microsoft…