Restore from Image created in VM ?

Discussion in 'backup, imaging & disk mgmt' started by frank7, Aug 30, 2016.

  1. frank7

    frank7 Registered Member

    Joined:
    May 14, 2011
    Posts:
    130
    Is it possible to restore a Macrium Reflect image that was created in a Virtual Box VM?

    I am really looking for a way to make a clean base image that I can restore to various hardware and add drivers and software from there onwards.

    Is it possible at all to create such a base image in a VM?

    How about if I wipe the disk of a dummy laptop and make a clean Win install there and take that image x.
    Would I be able to use that image x on another laptop?

    More info..
    Been looking at this thread the past days in order to get Win 7 on the Yoga 3 Pro 1370 running, but am so far failing due to the slipstreamed drivers not being loaded for a reason.
    There are plenty of posts and info about various ways to do this and I might add what I found overcoming quite a few error entires in DISM logs to above linked thread once I fully succeed. This not quite there.

    Also can try with the Windows 7* USB 3.0 Creator Utility but since I don't run Win 10 natively I am doing so in a VM, let's see if this works as a backup method.

    In case things don't work I am thinking of just using a clean base image y either from a VM or dummy laptop and add a folder with all the drivers for USB3 to the root partition and then make a Macrium image z of that and then just restore with image z to the Yoga and by keyboard navigate to the folder with the drivers and fingers crossed they will install.

    Coming back to, how to make a clean base Win image that can be used across hardware?
     
  2. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    3,051
    Location:
    The Pond - USA
    You should be able to do this with almost any image and using the "Re_Deploy" function from the Recovery Media following the actual restoration prior to reBOOTing LIVE. Of course you'll have the appropriate driver issues when you do this but it is Re-Deploy's job to get enough generic drivers in place for your System to BOOT.

    But remember... there will be a good chance you will have licensing issues associated with the image you're restoring on a different platform (Windows for sure and most likely other licensed software located in your baseline image). And if that image is nothing more than a Windows partition, your re-deployed System's BOOTing architecture may be in conflict with the System you're deploying to (both BiOS and disk layout).
     
  3. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,048
    Heed the froggies warning. I did extensive testing with a similiar approach of Shadowprotect. It's only point is to get you booted. Far from a totally working system.

    Here is what I would do.

    1. Forget the working across hardware. It will cost you more time, and poorer results.
    2. Image your system. Then test the image by restoring it.
    3. Do a clean windows installation on the system in question.
    4. Set the image aside
    5. Restore the first image you made.

    Now you will have what you need.
     
  4. frank7

    frank7 Registered Member

    Joined:
    May 14, 2011
    Posts:
    130
    Thank you for your replies.

    Can you explain this process a bit more detailed please?
    What do you mean with "Recovery Media" (actual Win .iso file?), "actual restoration" and "prior to rebooting live" please?
    Regarding the licensing issues people always have their key/serial to put in, what I am more worried about is "may be in conflict with the System you're deploying to (both BiOS and disk layout)".
    Does that mean it could simply crash or BSOD and all data lost?

    I like to have Win 7 on a laptop that has only got USB3 connections.
    For that I need to add USB3 drivers to the Win 7 install.
    edit:
    I have done a clean image with all the default factory partitions and Win 10, that I have.

    Running the Win 7 USB3 creator tool in a freshly created Win 10 VM resulted in this.
    FlashUtility Error 002.png

    (Did not find anything about the "FlashUtility" error online..)
    It seemed to me that the Win 7 USB3 creator tool from Intel went mounting all the indices in the install.wim and crashed when it got to loading the boot.wim.
    All other tutorials online mention to only use the index you need from both .wim files.
    So Setup from boot.wim with index 2 and Ultimate from install.wim with index 4.
    Have not tried the drivers from Intel yet so that is still an option.

    Regarding that I am now going the DISM route trying with the drivers that are included in the Win 7 USB3 creator tool from Intel.

    Code:
    dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:4 /mountdir:c:\win7usb3\mount
    
    dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /recurse /forceunsigned
    
    dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Doing this for the install.wim and boot.wim.
    Though I am not sure to use all indices in either .wim files or just the one I want?
    edit:
    Oh and I was always getting an Error 5 when adding the drivers to the install.wim, so in the end I created a Macrium Reflect PE v 3.1 and ran the DISM commands from the X:admin prompt in the Macrium PE. That was the only way to avoid the Error 5 - Access Denied in the DISM log. Tried another laptop, tried a freshly installed Win on a real laptop, no security apps etc. and still got Error 5. Glad that the commands can be run from inside the Macrium PE.

    Looking at the post here I am also wondering the following.
    When Win 7 is installed in the fresh VM and before the user is entered during Win 7 setup/install, audit mode is started and then at the very end after all the editing, a simple VM snapshot is taken.
    But then how can I turn such a VM snapshot into a Macrium image or any image to use on other hardware?
    How do I extract a VM snapshot to an image?
    (no clue if that talks about getting the VM snapshot to an image one can work with.. ??)

    What I would do, while being in the running VM ideally I would clean and generalize the image as outlined here in the "Clean Up the Image" and "Generalize the Image" sections.
    Is it possible to install Macrium in the VM while running in audit mode and simply take an image of that?
    Would that then be an image that I could try and use on other hardware?
    Last step, I would simply add the usb3 folder with the drivers to the C drive while making an image with Macrium in the VM so that the drivers are on the root when being restored since mouse and touchpad wont be working due to USB3 not supported in Win 7. So once this image is restored I can hopefully install the USB3 drivers via keyboard from?

    tl;dr
    If I could have Win 7 on the laptop with USB3 drivers enabled I will surly take an image of that to keep.
    It is just a matter of getting there.
    Does all this make sense?
     
    Last edited: Aug 30, 2016
  5. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    3,051
    Location:
    The Pond - USA
    Macrium Reflect's "Re-Deploy" function is only available in their Recovery Media (BOOTable WinPE CD/DVD). It functions by allowing you to do a Standard RESTORE of any image to any computer via the Reflect Recovery Media. While in the Recovery environment, there is a "Re-Deploy" option which may be activated. The purpose of Re-Deploy is to allow you to take any image (with any driver set) and load it up on a completely different computer (with different hardware), then it massages that image so it becomes BOOTable on your new hardware. At this point, your new hardware drivers will have to be found and installed as with any machine having just done a Clean Install... difference being a Clean Install just has Windows in place, this process has not only Windows but any applications/data that were installed in the imaged system being Re-Deployed.

    Licensing is not as simple as you state. If you're using a RETAIL Windows license, yes you can easily enter your license for re-activation, most likely after contacting MicroSloth and explaining what you've done. Remember, MicroSloth thinks this license is in use on another piece of hardware... this will have to be cleared up prior to activcvation on a new machine. This same process may have to be followed through on other licensed software that activates itself based on machine configurations. If you're trying to use an OEM Windows license for re-activation (one that came with a pre-configured System from a manufacturer), it cannot be used on any machine except the original machine it came with.

    Lastly, if you're producing a BASELINE re-deployable image based on one machine's hardware configuration (say Legacy-MBR configuration), it will not restore successfully to another machine's different hardware configuration (say UEFI-GPT configuration). BiOS changes will have to be made and possibly disk configurations may have to change.

    The process is not as simple as it may seem...
     
  6. frank7

    frank7 Registered Member

    Joined:
    May 14, 2011
    Posts:
    130
    Thanks for the detailed reply. Got it all fine now.

    Yes I think the Re-Deploy function is also available in their paid products range.
    Yes, made sure the hardware config and BIOS is set for legacy support and msdos partition table on the laptop drive.
    Same as on the VM host. Used gparted-live USB to do that on the laptop.

    If I got this right, a baseline Win image is a Win install with audit mode, changes made to system if wanted (drivers/software/settings/profiles) and then running
    Code:
    %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown
    
    ,then booting into a WinPE or MacriumPE and create an image of the disk (since there is only 1 partition in the VM the option to backup the partitions needed to restore the OS is not present I assume??) and store that on an external USB stick.
     
  7. frank7

    frank7 Registered Member

    Joined:
    May 14, 2011
    Posts:
    130
    In the end I saw that there is two USB3 drivers from Intel, one for none Core M and one for Core M hardware. I was trying to get it to work with the not for Core M driver so far. Of course it would not work.
    If you check the Intel 8 series download and there the Release Notes, the link to the PDF document there it says it is the right USB3 driver for Win 7 with Intel Core M hardware. Well hidden! Cheeky folks..

    In the end I took a syspreped default Win 7 image with the the Series 8 USB3 extracted folder with driver setup.exe therein on root C:\ and restored that with Macrium Reflect.
    All went along nicely. Could select all options with the keyboard during inital OOBE phase and then once loaded into Windows, with the keyboard could quickly navigate to the setup.exe of the Series 8 Intel USB8 driver for Windows 7 and bang, mouse started working flawless on the Yoga 3 Pro 1370. ;)

    Now I wonder what is better?
    Using the baseline image I created in the VM alongside the driver setup.exe on root or going for the DISM road, this time with correct drivers (Core M USB3 Series 8 Intel) for the install- and boot.wim files.
    Must say I am curious to run the DISM commands, now that I feel the solution with properly slipstreaming the drivers is at fingertips..

    edit:
    Even though I have the correct USB3 drivers for Win 7 since they install fine from the booted OS I cannot get them to work when adding them to the .wim files.
    Even though all commands complete there is no mouse support during OOBS phase and following setup.

    install.wim index 4 and boot.wim index 2
    Code:
    Microsoft Windows [Version 6.1.7601]
    
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:4 /m
    ountdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\install.wim
    Image Index : 4
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\boot.wim /index:2 /moun
    tdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\boot.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>
    

    install.wim index 1- 4 and boot.wim index 1-2
    Code:
    Microsoft Windows [Version 6.1.7601]
    
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:1 /m
    ountdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\install.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:2 /m
    ountdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\install.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:3 /m
    ountdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\install.wim
    Image Index : 3
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\install.wim /index:4 /m
    ountdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\install.wim
    Image Index : 4
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\boot.wim /index:1 /moun
    tdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\boot.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /mount-wim /wimfile:c:\win7usb3\boot.wim /index:2 /moun
    tdir:c:\win7usb3\mount
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>dism /image:c:\win7usb3\mount /add-driver:c:\win7usb3\usb3 /
    recurse
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image Version: 6.1.7600.16385
    
    Searching for driver packages to install...
    Found 3 driver package(s) to install.
    Installing 1 of 3 - c:\win7usb3\usb3\HCSwitch\x64\iusb3hcs.inf: The driver packa
    ge was successfully installed.
    Installing 2 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3hub.inf: The driver package w
    as successfully installed.
    Installing 3 of 3 - c:\win7usb3\usb3\Win7\x64\iusb3xhc.inf: The driver package w
    as successfully installed.
    The operation completed successfully.
    
    X:\windows\system32>dism /unmount-wim /mountdir:c:\win7usb3\mount /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    
    Image File : c:\win7usb3\boot.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\windows\system32>
    
    I assume alongside the USB3 driver for Win 7 Core M there is also a Chipset driver needed to make sure the hardware knows it is a Core M and can then accept the USB3 driver added to the .wim files. I suspect something like that, though not sure.

    Since things work with the baseline Win 7 image and the added folder with the UBS3 Series 8 Core M driver, things are starting to look better and I am not wasting more time with DISM or .wim files. I think Intel did not make these to be added to .wim files but installed only per setup.exe from the running OS. Don't know.

    If anyone has a suggestion, let me know please.
     
    Last edited: Aug 30, 2016
Loading...