User guide
Table Of Contents
- 1 Introducing Acronis Snap Deploy 5
- 1.1 Overview
- 1.2 What's new in Acronis Snap Deploy 5
- 1.3 What you can do with Acronis Snap Deploy 5
- 1.3.1 Taking an image of the master system
- 1.3.2 Deployment to specific machines (immediate, manual, and scheduled deployment)
- 1.3.3 Deployment to any ready machines (event-driven deployment)
- 1.3.4 Stand-alone deployment
- 1.3.5 Deployment with individual deployment settings
- 1.3.6 User-initiated deployment (custom deployment)
- 1.3.7 Deployment of a disk volume and MBR
- 1.3.8 Command-line mode and scripting under WinPE
- 1.4 Features of Acronis Snap Deploy 5
- 1.4.1 List of machines
- 1.4.2 List of deployment tasks
- 1.4.3 Per-deployment licensing
- 1.4.4 Support for the VHD format
- 1.4.5 Graphical user interface in WinPE
- 1.4.6 E-mail notifications about deployment
- 1.4.7 Compatibility with images created by other Acronis products
- 1.4.8 Support for multiple network adapters
- 1.4.9 Multicast TTL and network bandwidth throttling
- 1.4.10 Falling back to unicast
- 1.4.11 Encrypted communication
- 1.4.12 Password protection
- 1.5 Supported operating systems for imaging and deployment
- 1.6 Licensing policy
- 1.7 Upgrading to Acronis Snap Deploy 5
- 1.8 Technical Support
- 2 Understanding Acronis Snap Deploy 5
- 3 Getting started with Acronis Snap Deploy 5
- 4 Installation of Acronis Snap Deploy 5
- 4.1 Supported operating systems
- 4.2 System requirements
- 4.3 Used ports and IP addresses
- 4.4 Typical installation
- 4.5 Custom installation
- 4.5.1 Installation procedure
- 4.5.2 Common installation configurations
- 4.5.3 Installation of components
- 4.5.3.1 Installation of Acronis Snap Deploy 5 Management Console
- 4.5.3.2 Installation of Acronis Snap Deploy 5 License Server
- 4.5.3.3 Installation of Acronis Snap Deploy 5 OS Deploy Server
- 4.5.3.4 Installation of Acronis PXE Server
- 4.5.3.5 Installation of Acronis Wake-on-LAN Proxy
- 4.5.3.6 Installation of Acronis Snap Deploy 5 Management Agent
- 4.6 Other ways of installation
- 4.7 Upgrading Acronis Snap Deploy 5
- 4.8 Uninstalling Acronis Snap Deploy 5
- 5 Using Acronis Snap Deploy 5 Management Console
- 6 Using Acronis Snap Deploy 5 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)
- 10.7 Deploying BIOS-based systems to UEFI-based and vice versa
- 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
47 Copyright © Acronis International GmbH, 2002-2014
4.5.2 Common installation configurations
Acronis Snap Deploy 5 components can be installed in various configurations, to distribute various
components and features among the machines on the network.
a) The minimal configuration that enables only offline imaging (p. 23) and stand-alone deployment
(p. 9) consists of:
Acronis Snap Deploy 5 Management Console
b) The minimal configuration that enables offline imaging, stand-alone deployment, and
deployment through the network with Acronis Snap Deploy 5 OS Deploy Server consists of the
following components:
Acronis Snap Deploy 5 Management Console
Acronis Snap Deploy 5 License Server
Acronis Snap Deploy 5 OS Deploy Server
On the target machines, no Acronis components are required.
c) The configuration that adds the network boot of the target machines to the functionality
described in (b):
Acronis Snap Deploy 5 Management Console
Acronis Snap Deploy 5License Server
Acronis Snap Deploy 5 OS Deploy Server
Acronis PXE Server
The components can be installed all on the same machine, or on different machines. On the
target machines, no Acronis components are required.
This is the recommended elementary configuration that enables most of the Acronis Snap Deploy
5 functionality. This is the configuration for typical installation (p. 45).
If physical access to the powerful server is limited, you can install the console on a separate
machine. Another common configuration is:
Workstation:
Acronis Snap Deploy 5 Management Console
Server:
Acronis Snap Deploy 5 License Server
Acronis Snap Deploy 5 OS Deploy Server
Acronis PXE Server
Generally, you can install all Acronis servers on separate machines. In this case, you will have to
connect the management console to each server separately to manage the server. With all
servers on one machine, only one console connection is needed.
d) To add to any configuration (a)–(c) the online imaging (p. 24) ability and the ability to validate
images integrity, install Acronis Snap Deploy 5 Management Agent.
Online imaging means that the master system is imaged live (without restarting the machine or
suspending operations). You can perform online imaging remotely, by connecting the console to
the management agent installed on the master machine. The management agent will be included
in the master image and deployed to all target machines.
However, having excess software in the master image is not always rational.
We recommend that you create a master image by using the bootable component called Acronis
Snap Deploy 5 Master Image Creator. Nevertheless, having at least one management agent on