Acronis Snap Deploy 5 new build for Update 4
Dear Acronis Community,
we've just published a new build for Acronis Snap Deploy 5 Update 4.
Build number: 1924
New build and iso files are available under Acronis Account:
This build contains fixes for the following issues:
- Acronis Snap Deploy 5 Agent does not automatically start after booting into the WinPE-based bootable media environment even if the Autostart option was enabled when creating the media.
- Acronis Snap Deploy 5 PE builder may crash if the Windows system locale is set to Japanese.
- The state of the Run the file on target machine check box in the Files to transfer deployment setting is not preserved when re-opening this setting in Acronis Snap Deploy 5 Management Console.
- The default Target disk layout deployment settings do not contain the When deploying a single volume setting - only disk mapping settings are present.
I have run into a little problem when trying to deploy an image to a HP zbook 17" G5.
Since I have updated to the latest versaion I have been able to get into the agaent.
I have setup a user initiated preset and when I select the required setting, the agent starts to boot into serving image.
Then the agent restarts and repeats the process unitl I shut down pc.
The image is not served. I have older pc laptop which still work without a problem.
I can confirm what Spiro is saying. We purchased a new Dell Latitude 3500 and are trying to boot into master image configurator and it gets stuck at "Reading all physical volumes. This may take awhile". It appears the new generation NVME SSD is not recognized by the software. I cannot deploy images either using standalone utility.
If it helps your dev team, the exact SSD that is not getting recognized is a KBG30ZMS256G NVMe Toshiba 256GB
Also, we can get the bootable media to launch into master image creator only if BIOS SATA operation mode is set to AHCI and not RAID.
Ok I have been able to get the image I have on file to work. Currently I have an image from a HP zbook 17" G4 and I was able to get it to load and deploy from a standalone boot media using the current version. I was thinking my problem might have been the old image was created by an older version of Snap deploy. I will be creating a new image file and hoping to try and serve this on monday. I will keep you posted.
We found that the Windows PE version of Snap Deploy Build 1924 works well with the new computers.
This build also fixes an EXT4 capture issue. Previously, certain EXT4 partitions would be recognized incorrectly and need sector by sector capturing.
Support confirmed that the fix is in this build (though it's not listed in the changelog). I can confirm that this build fixed the issue for us.