Softpedia >Windows >Network Tools >Network Tools Suites >Acronis Snap Deploy >  Changelog

Acronis Snap Deploy Changelog

What's new in Acronis Snap Deploy 6.0.4569

Jul 28, 2023
  • [ASD-4922] A duplicate entry showing the same MAC address for a machine may appear in the machines list if the machine had default BIOS ID equal to "00020003-0004-0005-0006-000700080009" (default ID set by hardware manufacturer).
  • [ASD-4923] The TCP port 8081 used for API endpoint cannot be changed.
  • Solution: This port can now be changed under HKLMSoftwareAcronisSnapDeploySettings → ApiPort value in Windows registry on the machine which has OS Deploy Server component installed.
  • [ASD-4779] The C:ProgramDataAcronis folder permissions are not restricted to privileged users only.
  • [ASD-4499] Option Make ready for deployment is available in Actions after deployment in Standalone Deployment media UI, while it should not be.

New in Acronis Snap Deploy 6.0.4100 (Nov 7, 2022)

  • Post-deployment action: "Exit the application":
  • The new post-deployment action allows to further customize post-deployment operations, when deployment is performed by Acronis Snap Deploy Agent running under WinPE-based bootable media. With this post-deployment action, instead of rebooting or shutting down, the machine remains in WinPE environment after deployment
  • Fixed:
  • [ASD-4828] Sorting by "Machines" column doesn't work for deployment task details.
  • [ASD-4812] Deployment tasks are not properly shown in the Management Console if some of these tasks contain 500+ machines.
  • [ASD-4811] German locale: Linux-based bootable media with Master Image Creator component does not allow to switch to German keyboard layout.
  • [ASD-4810] Deployment tasks and/or templates cannot be created after update in rare cases (too many entries in the internal database).
  • [ASD-4809] Joining a machine to domain does not work if the target domain parameters were defined both in "Individual machine" settings and in the deployment template settings at the same time.
  • [ASD-4782] Deployment fails when using "Deploy to: The machines listed below" option.
  • [ASD-4781] Management Console crashes when selecting a master image captured from a Linux-based system which contains LVM volumes (image created by Acronis Cyber Protect 15/Acronis Cyber Protect Cloud), instead of showing proper error message.
  • [ASD-4640] Deployment fails if there are multiple folders from network shares selected in "Files to transfer" deployment option.
  • [ASD-4547] Japanese locale: master images are not shown when browsing for master image and using "Image (*.tib)" pattern.
  • [ASD-2599] Sorting by "Created" column doesn't work for deployment templates view.

New in Acronis Snap Deploy 6.0.1.3040 (Mar 28, 2022)

  • Simultaneous deployment tasks:
  • It is now possible to create and run multiple deployment tasks on a single OS Deploy Server in parallel, thus allowing to deploy different master images to different machines simultaneously.
  • You can also configure multicast addresses range used by OS Deploy Server to minimize networking conflicts, for example when you run 2 or more OS Deploy Servers in the same network.
  • Deployment via “Task Name” option:
  • This option solves the scenarios where you need to deploy multiple different master images to different target machines simultaneously and avoid situations where any machine gets a wrong master image.
  • With this option enabled in the deployment task, the machines will be deployed only if they have a value for the "Task name" parameter configured before connecting to the OS Deploy Server, and this value matches the deployment task name.
  • Deployment from TIBX archives:
  • Archives created by Acronis Cyber Protect Cloud and Acronis Cyber Protect 15 can now be used as master images for deployment.
  • Windows 11 and Windows Server 2022 support:
  • Windows 11 and Windows Server 2022 are now supported for both installation of Acronis Snap Deploy 6 components and for creation/deployment of the master images.

New in Acronis Snap Deploy 6.0.2.3030 (Aug 23, 2021)

  • Deployment over WiFi networks:
  • It is now possible to configure automatic connection of Acronis Snap Deploy 6 bootable media to WiFi networks and perform multicast and unicast deployments. The WiFi configuration is defined when creating the bootable media via Media Builder or right in the bootable media UI.
  • 64-bit architecture:
  • The product can be installed as native 64-bit application, thus ensuring compatibility with Acronis Cyber Protect 15 and Acronis Cyber Backup 12.5: you can install components altogether on the same machine, including PXE server compatibility.
  • Windows activation after deployment:
  • You can specify a unique Windows activation key to be used per each target machine for Windows activation after deployment. This key is defined as "individual machine" setting.
  • Preserve original machine name after deployment:
  • When performing Online Deployment, the guest OS machine name can now be optionally inherited from the OS rather than taken from the master image
  • Correct licenses assignment when deploying to machines connected via docking station:
  • The machines connected to a docking station share the same MAC address which caused licensing issues when tracking deployment usage, for example for tablets. Now this problem is gone with the new licensing algorithm which tracks machine BIOS ID in addition to MAC address for truly unique identification.
  • VLAN tags support in bootable media:
  • The bootable media now inherits the VLAN settings fro

New in Acronis Snap Deploy 6.0.2.890 (Jun 29, 2021)

  • Deployment over WiFi networks:
  • It is now possible to configure automatic connection of Acronis Snap Deploy 6 bootable media to WiFi networks and perform multicast and unicast deployments. The WiFi configuration is defined when creating the bootable media via Media Builder or right in the bootable media UI.
  • 64-bit architecture:
  • The product can be installed as native 64-bit application, thus ensuring compatibility with Acronis Cyber Protect 15 and Acronis Cyber Backup 12.5: you can install components altogether on the same machine, including PXE server compatibility.
  • Windows activation after deployment:
  • You can specify a unique Windows activation key to be used per each target machine for Windows activation after deployment. This key is defined as "individual machine" setting.
  • Preserve original machine name after deployment:
  • When performing Online Deployment, the guest OS machine name can now be optionally inherited from the OS rather than taken from the master image
  • Correct licenses assignment when deploying to machines connected via docking station:
  • The machines connected to a docking station share the same MAC address which caused licensing issues when tracking deployment usage, for example for tablets. Now this problem is gone with the new licensing algorithm which tracks machine BIOS ID in addition to MAC address for truly unique identification.
  • VLAN tags support in bootable media:
  • The bootable media now inherits the VLAN settings from Windows where Media Builder was ru

New in Acronis Snap Deploy 5.0.2012 (May 7, 2020)

  • Improved IT productivity:
  • Deploy to Live Machines – no manual booting required
  • Get up to 200% faster with the new Multicast protocol
  • Leverage latest Acronis Backup format
  • Acronis Universal Deploy for deployment to dissimilar hardware is now included in license
  • Improved flexibility:
  • Deploy Windows 10, 8.1 (including WIMBoot), Windows Server 2012 R2
  • Deploy Windows tablets
  • Deploy Linux
  • Use Windows PE 10 and 5.0 for Bootable Media and Live Deployment
  • Deploy Disk Images prepared with Sysprep
  • Enjoy new, cost-efficient site licensing option for larger environments

New in Acronis Snap Deploy 5.0.2003 (Mar 30, 2020)

  • Improved IT productivity:
  • Deploy to Live Machines – no manual booting required
  • Get up to 200% faster with the new Multicast protocol
  • Leverage latest Acronis Backup format
  • Acronis Universal Deploy for deployment to dissimilar hardware is now included in license
  • Improved flexibility:
  • Deploy Windows 10, 8.1 (including WIMBoot), Windows Server 2012 R2
  • Deploy Windows tablets
  • Deploy Linux
  • Use Windows PE 10 and 5.0 for Bootable Media and Live Deployment
  • Deploy Disk Images prepared with Sysprep
  • Enjoy new, cost-efficient site licensing option for larger environments

New in Acronis Snap Deploy 5.0.1993 (Oct 24, 2019)

  • What's new in Update 5:
  • Sector-by-sector imaging mode
  • If this option is enabled, the master image will contain all sectors of the selected disks or volumes, including unallocated space and those sectors that are free of data. During the deployment, these disks or volumes will be copied to the target machine "as is", without volume resizing.
  • Support for the Assessment and Deployment Kit (ADK) for Windows 10, version 1903
  • You can use the latest Windows ADK versions for Windows 10 to create WinPE-based bootable media with the Acronis Snap Deploy 5 PE Builder wizard.
  • Support for Windows Server 2019
  • Acronis Snap Deploy 5 Update 5 now supports installation of its components, including OS Deploy Server, PXE Server, and other, onto Windows Server 2019 as well as capturing and deployment images of this OS.
  • Issues fixed in Update 5:
  • This section describes issues that have been fixed in Update 5.
  • [ASD-4041] Deployment of the master image to a non-initialized disk may fail with the "Failed to assign volume" error.
  • [ASD-4035] Deployment of the GPT-based Windows 10 image may result in the change of partition order on the target system (MSR partition is always placed first).
  • [ASD-4031] Deployment of the GPT-based Windows 10 image onto the GPT disk onto the disk of the same size as original fails when using deployment “as is” (without resize) method.
  • [ASD-4020] When enabling the "User-initiated deployment" mode, the "Start operating system" (upon timeout) option settings are not applied to the machines booted from Acronis PXE server.
  • [ASD-3875] The "User accounts" settings specified in the deployment template incorrectly override the "User accounts" parameters from the individual settings defined for this machine.
  • [ASD-3869] Linux-based bootable media fail to boot on Gen2 Hyper-V virtual machine.
  • [ASD-3833] Deployment to the target system booted into Acronis Snap Deploy 5 Agent via a USB flash drive, with the default settings may fail with "Failed to resolve target disk" -> “Cannot deploy to bootable media” errors due to improper detection of disk order caused by presence of the USB media.
  • [ASD-3820] The Ubuntu source system which contains the ‘ext4’ file system may become unbootable after deployment to the same machine.
  • [ASD-3819] Deployment of the Ubuntu system which contains the ‘ext4’ file system shows improper deployment progress.
  • [ASD-3616] ISO images created by Acronis Media Builder cannot be saved to the USB flash drives by 3rd party tools (for example Rufus) due to the incompatible ISO image format.
  • [ASD-3366] The master image captured from systems which contain the ‘ext4’ file system is always performed in the sector-by-sector mode, while it should not.
  • [ASD-3350] The "Run file on target machine" checkbox setting under the "Files to transfer" deployment setting is not saved in GUI when trying to edit this setting.

New in Acronis Snap Deploy 5.0.1877 (Feb 18, 2019)

  • What's new in Update 4:
  • Export and import of individual deployment settings
  • You can export individual deployment settings of multiple machine to a text file, mass-change the settings in this file, specify new machines with their own deployment settings to add to Acronis Snap Deploy 5 OS Deploy Server, and import the file back. This functionality can be used to maintain or update the settings of multiple machines at once.
  • Support for the Assessment and Deployment Kit (ADK) for Windows 10, versions 1703, 1803, and 1809
  • You can use the latest Windows ADK versions for Windows 10 to create WinPE-based bootable media with the Acronis Snap Deploy 5 PE Builder wizard.
  • Acronis Snap Deploy 5 Standalone Utility can be included in WinPE-based bootable media
  • A stand-alone deployment can be performed by using WinPE-based bootable media in addition to using Acronis bootable media.
  • Support for the "/resize" parameter in the "deploy" command of Acronis Snap Deploy 5 Command-Line Utility
  • This parameter defines whether the volumes of a deployed disk will be proportionally resized on the target disk to occupy its enitre space or the size of the volumes will remain as it is in the master image. This is an equivalent of the Disk space utilization setting in a deployment template.
  • Fixed issues:
  • In Acronis bootable media, it is not possible to browse a network folder that is located on a machine with the disabled SMB1 protocol.
  • In WinPE-based bootable media, the Computers near me section is missing when selecting a location for the master image creation in Acronis Snap Deploy 5 Master Image Creator.
  • Online deployment of a machine running Windows fails if this machine is using static IP addresses.
  • If a deployment template contains a machine running Windows 7, there are more than seven users accounts in this operating system, and the Generate a unique SID for each target machine option is enabled in the template, some of the user accounts dissappear after deploying this machine.
  • Deployment of an UEFI machine to an UEFI machine may fail. The following message appears: "Internal error: write outside of allowed area."
  • If Acronis Snap Deploy 5 Management Console is installed on a machine without Acronis PXE Server, it is not possible to browse network folders via the console.
  • Bootable media with the default boot option set to Start operating system hangs up after a specified timeout instead of starting an operating system.

New in Acronis Snap Deploy 5.0.1780 (Sep 12, 2018)

  • 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.

New in Acronis Snap Deploy 5.0.1.1660 (Feb 24, 2016)

  • Improved IT productivity:
  • Deploy to Live Machines – no manual booting required
  • Get up to 200% faster with the new Multicast protocol
  • Leverage latest Acronis Backup format
  • Acronis Universal Deploy for deployment to dissimilar hardware is now included in license
  • Improved flexibility:
  • Deploy Windows 10, 8.1 (including WIMBoot), Windows Server 2012 R2
  • Deploy Windows tablets
  • Deploy Linux
  • Use Windows PE 10 and 5.0 for Bootable Media and Live Deployment
  • Deploy Disk Images prepared with Sysprep
  • Enjoy new, cost-efficient site licensing option for larger environments

New in Acronis Snap Deploy 5.0.1.1656 (Dec 16, 2015)

  • 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.).
  • 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.
  • Fixed issues:
  • 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.

New in Acronis Snap Deploy 5.0.1.1366 (Oct 27, 2014)

  • Deployment to a machine running Windows can be started while the machine is online:
  • You can instruct Acronis Snap Deploy 5 OS Deploy Server to start deployment to a registered machine while the machine is online. There is no need to manually reboot the machine into a bootable environment - it will happen automatically.
  • Optional installation of Acronis Snap Deploy 5 Management Agent into the deployed systems is added:
  • You can instruct the program to automatically install Acronis Snap Deploy 5 Management Agent into the deployed systems. The agent will be automatically registered on Acronis Snap Deploy 5 OS Deploy Server, thus simplifying future re-deployments.
  • Support for stand-alone deployment to 32-bit UEFI systems:
  • It is now possible to perform stand-alone deployment to machines running 32-bit UEFI systems (for example, Lenovo ThinkPad Tablet 2).
  • Acronis PXE Server now supports UEFI booting:
  • Both 32-bit and 64-bit UEFI systems can now be booted from Acronis PXE Server. However, Acronis PXE Server cannot boot a WinPE-based bootable media on a UEFI system.
  • Automatic switch to unicast if multicast fails during deployment is disabled:
  • If a deployment via the multicast transfer mode fails, there will be no automatic switch to the much slower unicast transfer mode.
  • Additional adjustments to deployment speed:
  • The size of the blocks being written to the target disk has been adjusted to improve the speed of the deployment.
  • Fixed issues:
  • Upgrade from the european english version of Acronis Snap Deploy 4 to Acronis Snap Deploy 5 requires the uninstallation of Acronis Snap Deploy 4.
  • Acronis PXE Server fails to boot a machine. The following error appears: "Acronis Loader fatal error: At least 512 Kb of conventional memory required to start Acronis Loader."

New in Acronis Snap Deploy 5.0.1.134 (Oct 8, 2014)

  • Improved IT productivity:
  • Deploys twice as fast as Acronis Snap Deploy 4
  • Deploys master images created with Acronis Backup and Acronis Backup Advanced products
  • Deploys a master disk image to both large and small disks without complications
  • Includes Acronis Universal Deploy (which enables deployment to new, dissimilar hardware)
  • Improved flexibility:
  • Includes full support for Windows 8.1 and Windows Server 2012 R2
  • Deploys to Windows tablet to get your mobile users up and running quickly
  • Installs on and deploys to Linux machines
  • Deploys images prepared with Sysprep
  • Includes new site licensing option for larger environments

New in Acronis Snap Deploy 4.0.540 (Oct 26, 2012)

  • General improvements:
  • [New feature] UEFI architecture support for imaging and deployment
  • [New feature] GPT disks support for imaging and deployment. Images taken on machines with BIOS architecture can be also deployed to UEFI machines – disk layout will be converted to GPT automatically.
  • Limitations: Linux GPT volumes are not supported for imaging and deployment.
  • [New feature] Windows 8 and WAIK 4 support
  • Limitations: Deployment of *.vhdx master images with Windows 8 OS is not supported
  • Fixed compatibility issues with Acronis Backup and Recovery PXE Server
  • Acronis SnapAPI driver was updated
  • A Linux kernel has been updated for the better hardware support in Linux bootable media.
  • List of issues fixed:
  • Installation:
  • Acronis Snap Deploy 4 PXE service is not started automatically after installing Acronis Snap Deploy PXE server over Acronis Backup and Recovery PXE server
  • Acronis Managed Machine Service is stopped and not restarted automatically if Acronis Snap Deploy 4 is installed on the machine after Acronis Backup and recovery 10\11
  • There is no warning during installation if only Acronis Snap Deploy 4 upgrade serial number is specified without full Acronis Snap Deploy 3 license
  • Acronis File Server files are not overwritten during installation of Acronis Snap Deploy 4 over Acronis Backup and Recovery 10\11 until reboot or Acronis File Server service restart
  • Impossible to install Acronis Snap Deploy 4 PXE server over Acronis backup and Recovery 10 PXE
  • Management Console:
  • It is not possible to create new user-initiated deployment after you delete the old one and reboot
  • “Enable\Disable PXE server” button does not make any affect until Management Console is restarted
  • “Help->Collect system information” menu option does not work in Acronis Snap Deploy if Acronis Backup and Recovery 11 is installed on the same machine
  • Template changes made during editing are not shown when template is being edited second time
  • Credentials are not accepted in deployment template wizard if Acronis Snap Deploy 4 was installed on the machine after Acronis Backup and Recovery 11
  • Option “Repeat the task every X hours until …” in deployment template wizard not working
  • Deployment:
  • Universal Deploy does not install drivers for NIC on deployed machine
  • Universal Deploy fails with error “Failed to download file” if “Specify mass storage drivers to install anyway” option was selected
  • Machine is not joined to domain after deployment if credentials are specified as “domain\user” if only first level domain name is specified in credentials instead of FQDN
  • Deployment fails with "Failed to start multicast session on FileServer" error if target machine is started from PXE server installed with Acronis Backup and Recovery 10\11 on the same machine
  • Deployment fails with "Failed to start multicast session on FileServer" error if Acronis Backup and Recovery 10\11 PXE server service is started on Acronis OS Deploy Server machine
  • “Application to run” option does not work - after deployment transferred script is not executed on the deployed machine
  • Deployment of password–protected master image fails if image password contains Unicode symbols
  • Deployment fails if master image is located on a network share and credentials were not specified in deployment template
  • Deployment fails with “Failed to start multicast session” if OS Deploy Server has additional network connections (e.g. Wi-Fi, Bluetooth, etc) besides regular Ethernet connection used to communicate with target machines
  • Deployment template option “Default gateway” is not applied to deployed machines
  • Acronis Universal Deploy does not inject NIC drivers into the deployed machine if they are stored on the network share
  • Bootable Media:
  • It is not possible to upload Acronis Snap Deploy 4 components to PXE server with Acronis Bootable Media Builder if ASD and ABR11 are installed on the same machine
  • OS Autostart feature is not working if password-protected components are uploaded to PXE
  • User-initiated deployment fails if target machine has NIC adapters not connected to the network
  • TCP\IP settings in deployment template of Standalone Utility are not accepted even if filled correctly (e.g. same values as those that work in deployment template wizard in Windows)
  • IP address for Standalone utility media cannot be specified manually
  • Acronis Bootable Media Agent hangs if there are no NIC adapters on the machine
  • Documentation:
  • Description Security Identifiers in deployment template is updated – SID is not changed after deployment for master images of servers with Domain Controller role enabled.
  • Note for Acronis Bootable Media has been added – bootable CD cannot resolve machine names correctly if name contains non-English characters. IP address should be used instead for such scenarios.
  • Other fixes:
  • Acronis File Server crashes after service is restarted if there are two network adapters in the system and one of them is disabled in device manager
  • Sporadic crashes of Acronis Snap Deploy PXE server
  • Wrong error message “Failed to start multicast session on FileServer.” instead of “Failed to start unicast session on FileServer.” when unicast session on File Server fails to start
  • Remote Assistance does not work on the deployed machine if SID was changed during deployment
  • Creation of master image from machine containing Dell OEM fails with “Failed to read from sector ‘63’ of hard disk” error
  • Known issues:
  • Deployment fails with “Host ‘X.X.X.X’ has failed the deployment” error if Jumbo Packet property of network adapter is enabled on OS Deploy Server
  • Booting Hyper-V 3.0 virtual machines from Acronis PXE is very slow
  • Incorrect error “Deployment has failed” appears after successful deployment from external network via VPN connection
  • Windows 8 App Store applications cannot be updated/re-installed after deployment if deployment template option “Generate a unique SID for each deployed machine” was used

New in Acronis Snap Deploy 2.0 build 2105 (Dec 16, 2006)

  • Deploy to different hardware with Acronis Universal Deploy*� Ensure that your new systems will boot by allowing you to add drivers and create templates for specific hardware
  • New media builder � Facilitate deployment by providing more options for creating bootable media. Create ISOs, Microsoft Remote Installation Service (RIS) packages, and place multiple configurations on one CD
  • 64-bit Windows support � Deploy both new and older systems using one solution
  • Customizable deployment options � Maximize the performance of new machines by allowing partitions to be resized. Ensure that machines are properly deployed by providing options to reboot or shutdown after the master image is applied
  • Enhanced PXE server � More easily create a PXE by specifying default configurations and timeout parameters for reboot.