Problem with restoring True Image images with Snap Deploy 5 CLI utility on WinPE
Hi.
Following this topic
Since then, I found Microsoft's native imaging solution,, DISM, and it worked perfectly with my PXE server and automation (I built it in a way that for different PC serial number it chooses a different image).
Now there is another challenge.
For my testing lab, I have to deploy OS images created by someone else with Acronis True Image 2017. Now I know that I can use True Image myself, but I found that I can automate the process with Snap Deploy, and also it's much faster and cheaper for somebody who has to buy only licenses for like 30 PCs (from what I understood, I don't need the server for standalone deployments, I have my own solution).
However, I ran into another problem. When I tried to backup and deploy the OS image with Snap Deploy on my test laptop, with image taken with Snap Deploy command line utility under WinPE, everything worked fine.
But when I am trying to restore a pre-made .tib image (taken by somebody else), I get this error:
I looked on the partition structure on the image and on my hard drive, and found that it's numbered differently. Apparently, the person who took this image, just removed the HDD from his laptop, connected to his work PC, where it was recognized as disk 5, drive E: , and took image with True Image. Here is a comparison of naming partitions in the OS image and on my test laptop hard drive:
With True Image,, restoring it is not a problem, as True Image changes automatically what's needed, but with the Snap Deploy CLI utility, I am running into the above problem.
I wish to automate the process, so I don't want to use True Image. How can I deploy something like this, so the Snap Deploy CLI restores the image contents to the target drive (disk 1)?
Thanks kindly for the answer,
Vadim

- Log in to post comments

Solved the above issue, too.
Now there is another one.
I am trying to restore an image of a larger drive to smaller one (from 256GB SSD to 128GB)
In True Image, I did not have this issue, resizing was done automatically.
In Snap Deploy, I am getting this error:
Target Drive Is Too Small
Where the same image deploys fine on the same machine with Acronis True Image.
Can somebody please help?
Thanks,
Vadim
- Log in to post comments

Anybody?
- Log in to post comments