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
100 Copyright © Acronis, Inc., 2000-2011
§ Deployment as soon as a specified number of any machines become ready for deployment (p.
106). You (or users in your organization) will need to make the machines ready.
A machine becomes ready for deployment after it boots to Acronis Snap Deploy 4 Agent from a
bootable media or a PXE server, and then connects to Acronis Snap Deploy 4 OS Deploy Server.
In addition, you can run any deployment task manually from the Deployment tasks view (p. 124).
A deployment task runs according to a deployment template (p. 80). When creating the task, you can
create a deployment template or specify an existing one.
10.4.1 Prerequisites
Before proceeding with the deployment, make sure that:
§ You have installed the following components: Acronis Snap Deploy 4 Management Console,
Acronis Snap Deploy 4 License Server, Acronis Snap Deploy 4 OS Deploy Server, and (optionally)
Acronis PXE Server. All these components are already installed if you performed a typical
installation (p. 40).
§ You imported a sufficient number of licenses (p. 15) to Acronis Snap Deploy 4 License Server.
§ You created a master image by using either bootable media (offline imaging (p. 68)) or Acronis
Snap Deploy 4 Management Agent (online imaging (p. 68)).
Procedures in this section assume that you have performed these steps.
10.4.2 Deployment to specific machines
Deployment to a specified list of machines can run immediately, manually, or on a schedule.
When the deployment is about to start, the software uses the Wake-on-LAN (WOL) functionality of
the BIOS to wake up (turn on) the machines in the list.
Acronis Snap Deploy 4 wakes up each machine by sending a special packet, called the magic packet,
to all network adapters of the machine.
Machines in another subnet can be woken up through the Acronis Wake-on-LAN Proxy component,
which is delivered with Acronis Snap Deploy 4.
The woken up machines then boot into Acronis Snap Deploy 4 Agent.
You can manually boot machines that do not support Wake-on-LAN, before the task starts. Such
machines will also be deployed, provided that they are listed for deployment.
A best practice for this type of deployment is to use Acronis PXE Server for booting the machines.
Alternatively, you can boot the machines by using a bootable media.
10.4.2.1 Preparation steps
This section describes how to prepare deployment to a specified list of machines.
Getting MAC addresses
Media Access Control address (MAC address) is a 48-bit physical (hardware) address of a network
device. In Windows, the physical address can be obtained by running the command ipconfig /all