Windows 10 Image Capture - Virtual vs Physical
-
Hi,
Do you guys have any reasons why a Virtual Machine Reference Image is better then a Physical Computer Reference Image? Does Microsoft Azure totally throw out any work I put into capturing an Windows Image using a Virtual Machine Reference(or Physical)?
Background:
Previously I have captured (with many failed attempts) Windows 10 WIM files using a Physical Reference Computer using SysPrep and then deploying in WDS on Microsoft Server 2012.A week ago, I decided to create a Windows 10 Reference by using a virtual machine (in Virtual Box)
Ive created a Start Image and did a snapshot. I captured that using Dell's Image Assist and now have a WIM file. It is now time for me to start working on installing the applications that our company will be using.At this point though, my manager asked why I'm using a VM Image vs creating the image on a actual computer and capturing it. He was confused how this will work and if it will have issues due to drivers needed. He also said we are thinking about moving to Office 365 and will possibly be using the tools (Azure to deploy).
-
from Adam Gordon:
"Nate,I hope all is well. Great question(s) about a very important aspect of using Azure. Let's see what we can do to help you get a better understanding of the basics, as well as the actual process that you will use.
The most important things for you to be aware of are the pre-work items that have to be done to prep the VM before you capture the image. See below:
Prepare a Windows VHD or VHDX to upload to Azure:
Prepare a Windows VHD to upload to Azure
docs.microsoft.com
How to prepare a Windows VHD or VHDX before uploading to AzureAfter all the prep work above is done, see the instructions below to capture the VHD image, upload it to Azure and then use it as your reference image:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed
Create a managed Azure VM from a generalized on-premises ...
docs.microsoft.com
Upload a generalized VHD to Azure and use it to create new VMs, in the Resource Manager deployment model.With regards to the physical machine vs virtual machine as the basis for the image, if you are gong to be using the image to create virtualized infrastructure that will be hosted in Azure and run there, then there are no driver issues to be concerned about, as you will be using virtual machines, not physical ones.
Anytime that you create a VM, or an image as a VHD(X) to base VM's off of, you remove the need for hardware specific drivers for the most part, unless you are connecting specific hardware as a "pass through" directly via the underlying host. If that is the case, then you would need to ensure that the required drivers are made available.
I hope that this points you in the right direction and clarifies things for you. If you have any more questions, please let me know. "
Regards,
Adam Gordon
Edutainer
(352) 600-6900
