Deploy

Use the "Files to transfer" option to transfer all the drivers necessary for Acronis Universal Deploy

The cause is in the deployment template that has some options set which do not fit multiple machines deployment. As a result, some of the machines are left out

Collect the log and send it to Acronis Support for investigation

Create a custom Windows PE image with deployment script using asdcmd tool

Deployment on Dell Precision workstations results in drive letters in reverse order

Deployment fails because there is no disk at all, Acronis Linux fails to detect it, or there is not enough free space

Start the Acronis Scheduler2 Service to fix the issue

Acronis Snap Deploy 4 licensing scheme

Table of operating systems supported by older Acronis products

With the "Occupy disk space entirely" option selected in the Deployment Template Wizard, only the last partition is resized

As a user you are responsible to have the necessary third party software licenses when deploying, cloning, restoring or in any other way transferring operating systems or applications

A short overview of the network connections between Acronis OS Deploy Server and Acronis Snap Deploy Agent during image deployment process

This article describes the troubleshooting steps in case of a Virtual Appliance installation failure

It recommended to use Acronis Universal Restore to deploy the image of a Windows system to a machine with different hardware

This means that the backup task creation has failed due to an external factor. In the log, look for the lines preceding the error message to find out the cause

Acronis Snap Deploy started supporting disks with GUID partition tables (GPT) and dynamic disks in version 4.

Acronis Snap Deploy 5 supports GUID Partition Table (GPT) partitioning scheme. Dynamic volumes (in Windows) can be deployed as basic volumes only.

Acronis Snap Deploy 4 supports GUID Partition Table (GPT) partitioning scheme. Dynamic disks currently are not supported for imaging and deployment. Detailed information here.

Deploying the Agent for ESX(i) if it hasn't been deployed automatically during vCenter Server integration

Symptoms

  1. You create a deployment task with the default option "Shut down" enabled for an Agent on Windows 8;
  2. After you perform a successful deployment, the Agent reboots instead of shutting down.

Cause

This is an irregular known issue.

Solution

As a workaround, please shut down the Agent machine manually (or through Remote Desktop).

How to receive an upgrade license for an Acronis Business Product provided that you have a respective support option

How to install, configure and update Virtual Appliance

This article applies to:

  • Acronis Cyber Protect Cloud
  • Acronis Cyber Protect 15 - Cloud deployment

Pages