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
88 Copyright © Acronis, Inc., 2000-2011
By default, all deployed machines will have the same name as the machine in the master image.
Alternatively, you can specify a name pattern for the machines.
Specify whether the machine will be a member of a workgroup or an Active Directory domain. If you
have selected the domain membership, specify the user name and password of a domain
administrator.
Name patterns
A name pattern determines the names that the target machines will have after the deployment.
To specify a single name for all target machines, type that name in Machine name pattern. For
example, type: DeployedMachine
To generate different names for the target machines, include either of the following wildcards or
their combination.
{start}
Generates consecutive numbers starting with start. Each machine name will have its unique
number.
For example, the pattern {1} generates the names 1, 2, 3, and so on up to the number of target
machines. Similarly, the pattern {5} generates the names 5, 6, 7, and so on.
It makes sense to use only one such wildcard in the pattern.
{start,count}
Generates count consecutive numbers starting with start.
For example, the pattern {1,5} generates the names 1, 2, 3, 4, and 5. Similarly, the pattern {8,5}
generates the names 8, 9, 10, 11, and 12.
Make sure that the value of count is big enough. If the number of target machines exceeds count,
deployment to the remaining machines will fail.
You can use two or more of these wildcards. See examples later in this section.
In the wildcards, the value of start must be 0 or greater. The value of count must be 1 or greater.
You can use the wildcards alone or accompany them with text, as in the following examples.
Examples
Machine{1}
This pattern generates the names Machine1, Machine2, …, MachineN, where N is the number of
target machines.
Name{1,3}
This pattern generates the names Name1, Name2, and Name3.
{1,3}{1,4}
This pattern generates the names 11, 12, 13, 14; 21, 22, 23, 24; 31, 32, 33, and 34
{1,9}{0,10}
This pattern generates 90 names: 10, 11, 12, …, 19; 20, 21, 22, …, 29; …; 90, 91, 92, …, 99










