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
134 Copyright © Acronis, Inc., 2000-2011
email_n_test
Use this command instead of the email_n command, with the same set of parameters, to test the
configuration of e-mail notifications.
14.1.4 Usage examples
Example 1. The following command creates an image arc.tib of hard disk 1, and places the image to
the network folder \\server1\folder. The operation log file log1.log is saved in another network
folder: \\server2\dir\. Credentials for both network folders are provided:
asdcmd /create /harddisk:1 /filename:\\server1\folder\arc.tib /net_user:user1
/net_password:pw1 /log:\\server2\dir\log1.log /log_net_user:user2
/log_net_password:pw2
Example 2. The following command creates an image of the volume 1-2 sector-by-sector (in the raw
mode) and saves the image to volume H:
asdcmd /create /filename:h:\raw.tib /partition:1-2 /raw /log:c:\log.txt
Example 3. The following command deploys the hard disk 2 from the password-protected image
1.tib that is located in the network folder \\server1\folder, to the disk with the same number, 2.
asdcmd /deploy /filename:\\server1\folder\1.tib /password:qwerty /harddisk:2
14.2 Sample scenarios
14.2.1 Deploying images assigned to target machines
Scenario
An administrator needs to deploy a different master image to each target machine.
Solution
The administrator puts the images in a shared location that can be accessed from each target
machine.
The administrator renames each image according to the target machine’s MAC address. The image
destined to the machine with MAC address 01-02-03-04-05-06 will have the name, for example,
image-01-02-03-04-05-06.tib.
The administrator writes a deployment script that can read the target machine’s MAC address and
pull an image with a name corresponding to the MAC address from the shared location. The script
can be executed on any number of target machines.










