4.0
Table Of Contents
- 1 Introducing Acronis Snap Deploy 4
- 1.1 Overview
- 1.2 What you can do with Acronis Snap Deploy 4
- 1.2.1 Taking an image of the master system
- 1.2.2 Deployment to specific machines (immediate, manual, and scheduled deployment)
- 1.2.3 Deployment to any ready machines (event-driven deployment)
- 1.2.4 Stand-alone deployment
- 1.2.5 Deployment with individual deployment settings
- 1.2.6 User-initiated deployment (custom deployment)
- 1.2.7 Deployment of a disk volume and MBR
- 1.2.8 Command-line mode and scripting under WinPE
- 1.3 Features of Acronis Snap Deploy 4
- 1.3.1 New: List of machines
- 1.3.2 New: List of deployment tasks
- 1.3.3 New: Per-deployment licensing
- 1.3.4 New: Support for the VHD format
- 1.3.5 New: Graphical user interface in WinPE
- 1.3.6 New: E-mail notifications about deployment
- 1.3.7 New: Compatibility with Acronis True Image, Acronis Backup & Recovery 10, and Acronis Backup & Recovery 11 backups
- 1.3.8 New: Support for multiple network adapters
- 1.3.9 Multicast TTL and network bandwidth throttling
- 1.3.10 New: Falling back to unicast
- 1.3.11 Encrypted communication
- 1.3.12 Password protection
- 1.4 Supported operating systems for imaging and deployment
- 1.5 Licensing policy
- 1.6 Upgrading to Acronis Snap Deploy 4
- 1.7 Technical Support
- 2 Understanding Acronis Snap Deploy 4
- 3 Getting started with Acronis Snap Deploy 4
- 4 Installation of Acronis Snap Deploy 4
- 4.1 Supported operating systems
- 4.2 Used ports and IP addresses
- 4.3 Typical installation
- 4.4 Custom installation
- 4.4.1 Installation procedure
- 4.4.2 Common installation configurations
- 4.4.3 Installation of components
- 4.4.3.1 Installation of Acronis Snap Deploy 4 Management Console
- 4.4.3.2 Installation of Acronis Snap Deploy 4 License Server
- 4.4.3.3 Installation of Acronis Snap Deploy 4 OS Deploy Server
- 4.4.3.4 Installation of Acronis PXE Server
- 4.4.3.5 Installation of Acronis Wake-on-LAN Proxy
- 4.4.3.6 Installation of Acronis Snap Deploy 4 Management Agent
- 4.4.3.7 Installation of Acronis Universal Deploy
- 4.5 Other ways of installation
- 4.6 Upgrading Acronis Snap Deploy 4
- 4.7 Uninstalling Acronis Snap Deploy 4
- 5 Using Acronis Snap Deploy 4 Management Console
- 6 Using Acronis Snap Deploy 4 License Server
- 7 Deployment tools
- 8 Creating a master image
- 9 Validating a master image
- 10 Deploying a master image
- 10.1 Files supported as master images
- 10.2 Licenses for deployment
- 10.3 Deployment templates
- 10.4 Deployment through a deployment task
- 10.5 Stand-alone deployment
- 10.6 User-initiated deployment (custom deployment)
- 11 Managing the list of machines (the Machines view)
- 12 Individual deployment settings
- 13 Managing deployment tasks (the Deployment tasks view)
- 14 Command-line mode and scripting under WinPE
- 15 Collecting system information
79 Copyright © Acronis, Inc., 2000-2011
10 Deploying a master image
This section describes how to deploy a master image to one or more machines.
Caution: Deployment to a machine involves deleting some or all data that is currently stored on that machine.
Make sure that you are performing deployment to the correct machines and to the correct disks on those
machines.
10.1 Files supported as master images
Acronis Snap Deploy 4 can perform deployment from any of the following files:
§ A master image created by Acronis Snap Deploy 4 or by an earlier version of the software
§ A disk-level backup created by the Acronis True Image, Acronis Backup & Recovery 10, or Acronis
Backup & Recovery 11 product family
§ A Virtual Hard Disk (VHD) file
Support for Acronis True Image, Acronis Backup & Recovery 10, and Acronis Backup
& Recovery 11 backups
These Acronis products save the disks and volumes of a machine to a file called a backup.
Similarly to master images, backups are stored as .tib files. You can specify such file as you would the
master image.
Some backups (known as incremental and differential backups) depend on other backups. To ensure
that Acronis Snap Deploy 4 finds all of the backups it needs, we recommend leaving the backup in the
location where it was created by your Acronis product.
If the backup is split into two or more parts, make sure that all these parts are in the same folder. To
specify such a backup, specify any one of these parts.
The backup can contain disks of various types, but only basic disks whose partitioning scheme is
master boot record (MBR) are available for deployment.
Support for VHD files
These files store disks and volumes of a machine. Such a file can be created by the following
programs:
§ Microsoft Virtual PC 2007 SP 1.0, Windows Virtual PC, and Microsoft Virtual Server
§ Windows Backup (in Windows 7)
§ Acronis True Image Home 2010 and later
You can perform deployment from a VHD file that contains both basic and dynamic volumes.
However, any dynamic volumes, such as simple or spanned volumes, will be deployed as basic
volumes. You can deploy only disks whose partitioning scheme is master boot record (MBR).
Important: If you created the VHD file by using the Windows Backup program, we recommend leaving such a
file in its original location. If you must move the VHD file to a new location, make sure to move the entire folder
containing this file, including subfolders and supplementary files such as .xml files. Otherwise, the deployment
operation may fail.