Acronis Snap Deploy 5 is a comprehensive deployment solution that enables IT organizations to deploy or restore laptops and desktops quickly and easily. With Update 3, the product offers enhancements and addresses issues found in the previous release.
What's new in Update 3
Support for Windows Server 2016.
You can image and deploy a machine running this operating system and apply any post-deployment operations to it (add the machine to a domain, execute scripts on it, etc.). All Acronis Snap Deploy 5 components can be installed in this operating system.
Compatibility with backups created by Acronis Backup 11.7.
You can deploy an image created by Acronis Backup 11.7 via Acronis Snap Deploy 5.
Support for imaging and deployment of systems with the enabled Secure Boot.
You can image and deploy a machine with the UEFI Secure Boot option enabled.
All components of Acronis Snap Deploy 5 are now fully compatible with Windows 10.
It is now possible not only to image and deploy a machine running Windows 10, but also to use this machine as a deployment server by installing the Acronis Snap Deploy 5 components on it.
Fixed issues
Acronis Snap Deploy 5 License Server may consume additional per-machine licenses for the same MAC address.
An entire folder is not transferred to a deployed machine via the Files to transfer option.
Acronis Snap Deploy 5 PE Builder does not detect Assessment and Deployment Kit (ADK) for Windows 10, version 1607.
It is impossible to deploy an image to a non-initialized disk via Acronis Snap Deploy 5 Standalone Utility. The disk is displayed as unsupported in the user interface.
The database of Acronis Snap Deploy 5 OS Deploy Server may grow excessively.
The sysinfo command of the Acronis bootable media shell cannot capture the Linux system report due to the invalid sysinfo.sh script.
Known issues
[Windows 10 specific] Acronis Snap Deploy 5 Management Agent can be remotely installed on a target machine running Windows 10 only when the built-in administrator credentials are specified or UAC is disabled on the machine.
An Acronis bootable media may incorrectly detect a machine’s hardware.
Solution: Use a WinPE-based bootable media instead.
The "Access is denied" message appears when trying to remotely install Acronis Snap Deploy 5 components if UAC on a target machine is enabled and the machine is not a member of Active Directory.
Solution: Disable UAC on the remote machine to be able to use remote installation or use a domain administrator account if the remote machine is in a domain.
A machine’s security identifier (SID) does not change after deployment of Windows Small Business Server 2011.
Acronis PXE Server of Acronis Snap Deploy 5 conflicts with the one of Acronis Backup & Recovery or Acronis Backup if they are installed on the same machine.
Solution: Install PXE servers on different machines.
If you start the Master Image Creator wizard and then connect or disconnect one of the USB drives, there will be multiple errors related to all drives, such as, "Failed to read from the sector 0 of the hard disk 1. Sector was skipped."
Solution: Do not plug or unplug any USB drives while a master image is being created.
The Applications to run setting does not work after deployment of Windows 7 or Windows 2008.
Solution: To run an application or a script automatically under the operating system, use the Files to transfer setting to copy the file, the script, or the link to the script to the Startup folder of the target machine, such as the folder C:\Users\USER1\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.
Deployment fails and the "Host 'X.X.X.X' has failed the deployment" error appears if the Jumbo Packet property of the network adapter is enabled on OS Deploy Server.
Booting Hyper-V 3.0 virtual machines from Acronis PXE Server is very slow.
The "Deployment has failed" error appears after successful deployment from an external network via a VPN connection.
It is impossible to update or reinstall Windows Store applications after deployment if the Generate a unique SID for each deployed machine check box was selected in the deployment template.
The Use PXE server for booting into agent check box does not work if the Start operating system option was selected under When booting from the media, automatically start when uploading Acronis Snap Deploy 5 Agent to Acronis PXE Server.