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 2, the product offers enhancements and addresses issues found in the previous release.
What's new in Update 2
Improvement added in build 1660.
Support for the subscription licensing model.
Support for imaging and deployment of machines running Windows 10.
You can image and deploy machines running this new operating system, and apply any post-deployment operations to them (add the machines to a domain, execute scripts, etc.).
Please carefully read the known issues to check the existing limitations for the Windows 10 support.
Support for WinPE 6.0.
Support for Windows 10 also includes support for the most recent WinPE. WinPE 6.0 can now be used as a pre-boot environment by a WinPE-based bootable media.
Support for creation of 64-bit WinPE-based bootable media.
It is now possible to create a 64-bit WinPE-based media to support certain hardware that has only 64-bit drivers.
Acronis Snap Deploy 5 OS Deploy Server fails to deploy a master image to specific models of HP Probook and Lenovo Thinkpad/Thinkcentre/Thinkstation. The following error appears: "Failed to resolve disk by number '1'."
Stand-alone deployment fails if a master image is located on a USB drive.
It is impossible to deploy corrupted or unrecognized volumes as is.
It is impossible to configure the parameters of the Linux kernel in Acronis Snap Deploy 5 Bootable Media Builder when creating an Acronis bootable media.
A deployed machine is not added to a domain if this domain is specified in the individual machine settings of the deployment task.
[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 Universal Deploy fails to automatically install network card drivers if they are stored on a network share and the network share was specified as a driver repository when configuring the Acronis Universal Deploy option.
Solution: Specify the drivers manually when configuring the Acronis Universal Deploy option.
When working under a WinPE-based bootable media, a static IP address cannot be used for an agent.
Solution: If there is no DHCP server on the network, use an Acronis bootable media and assign the IP address manually.
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.