What's new in Acronis Snap Deploy 6

Acronis Snap Deploy 6 Update 3

  • 4-year and 6-year licenses are now available, in addition to the existing 1-year, 3-year, and 5-year options.

  • The CLI deployment tool (ASDCMD) flexibility has been improved in the following scenarios:

    • You can now deploy specific partitions, instead of the entire disk, using the /partition:x-x parameter. If the number of partitions on the master image doesn’t match the target disk, the /clean_and_deploy option can prepare the disk for deployment.

    • The /resize parameter now resizes all partitions to fit the target disk instead of resizing only the last partition.

Acronis Snap Deploy 6 Update 2

  • Subscription licensing

    Support for subscription licensing model. Each subscription license is a 'Machine' license type, which enables an unlimited number of deployments to the same machine during the subscription period (TTL).

Acronis Snap Deploy 6 Update 1.2

  • Post-deployment action: "Exit the application"

    The new post-deployment action allows further customization of 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.

Acronis Snap Deploy 6 Update 1

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

Acronis Snap Deploy 6

  • 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 run to create this media. In addition, you can connect the bootable media manually to required VLAN via its native UI. Deployment from VHDX It is now possible to deploy from Microsoft latest virtual disks format VHDX in addition to previously supported VHD.

  • UX enhancements

    Several UX enhancements including ability to sort machines by IP/name in the management console.