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
93 Copyright © Acronis, Inc., 2000-2011
Using the Unicast transfer mode, the server sends a copy of the data to each recipient. This can
significantly reduce the deployment speed.
For example, suppose that you have a bandwidth of 100 MB per second, and you want to deploy a
system to 10 target machines.
§ With the Unicast mode, the server divides the speed among 10 machines. Therefore, the data
transfer speed will be 10 MB per second for each target machine.
§ With the Multicast mode, the server sends one copy of data to a multicast address, and each
client will receive data at a speed of 100 MB per second.
Multicast configuration has a parameter that specifies the time to live (TTL) for multicast packets.
Use this parameter to limit multicast packets distribution via gateways.
The default value is 15. In practice, this enables the packets to pass up to 15 hops which may be
treated as an unlimited distance. The minimal value 1 will limit the packets circulation to one subnet.
By setting the permitted bandwidth, you can limit the network usage during deployment. The default
value is 1 gigabit (Gbit) per second.
Adjusting network utilization settings
Acronis Snap Deploy 4 uses Internet Group Management Protocol (IGMP) for multicasting. Therefore,
all network hardware (such as routers or network switches) must be IGMP-capable and correctly