Windows system imaging is more robust for redeploying an image to other endpoints but it is also more complex. So, the last thing you want to do is 'clone' an image unless you are going to reapply it to the exact same machine and hardware. MDT's built-in task sequences take care of that for you. That is why WinPE is designed to strip drivers and identifiers before you capture an image. If you don't, it will create duplicate GUIDs in AD because it will literally be a clone and that isn't good for SIDs and GUIDs. In fact, you should also make sure that you run all phases of WinPE to prep and finalize the image. If you are going to capture an image using dism or imagex, make sure that the image you are capturing is not domain joined. The target image can also handle the domain join. This allows you to fully automate the build process and use a base image to deploy with other applications and drivers added through the target image. If you are not familiar with virtual machines we recommend installation Home Assistant OS directly on a Raspberry Pi or an ODROID. Follow the instructions to create a reference image and target image task sequence to capture (reference) and deploy (target) an image to machines from the MDT repository. VirtualBox (.vdi) KVM (.qcow2) Vmware Workstation (.vmdk) Hyper-V (.vhdx) Follow this guide if you already are running a supported virtual machine hypervisor. If you want to have some real fun, download and install MDT.

Windows 10 virtual image