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
8 Copyright © Acronis, Inc., 2000-2011
1.2.1 Taking an image of the master system
First, you create the desired system configuration and save the image of the system hard disk to a
network folder, detachable media (such as a USB hard drive) or removable media (such as a DVD). An
image, also called a master image, is a file that contains the system in a packaged form.
Scenarios
Scenario 1
Each department in your organization, such as accounting, sales, and technical support, uses a
fixed set of applications for daily work.
You create a library of master images. For example, you create one image for each department.
You then deploy these images to new hardware without having to manually configure the
operating system and applications.
Scenario 2
You need to deploy a standard configuration included in a master image, to machines with
different hardware.
You use the separately-sold Acronis Universal Deploy add-on. This add-on configures Windows
system drivers so that Windows is able to boot on dissimilar hardware. Without this add-on, the
motherboard, processors, and mass-storage devices of the imaged and the target hardware must
be identical. The same applies to non-Windows operating systems.
1.2.2 Deployment to specific machines (immediate, manual, and
scheduled deployment)
You can perform deployment to a specific list of machines with known physical addresses (called
MAC addresses). The deployment can run immediately after you set it up, on a schedule, or when
you start it manually.
These ways of deployment are also known as manual deployment and scheduled deployment.
When the deployment is about to start, the software will power on the target machines with
predefined MAC addresses by using the BIOS Wake-on-LAN (WOL) functionality.
Machines in another subnet can be woken up through a component called Wake-on-LAN Proxy,
which is delivered with Acronis Snap Deploy 4. The machines typically boot into the PXE server that is
installed in the same subnet.
Machines that do not support Wake-on-LAN can be booted into the Acronis environment manually
before the deployment starts. Such machines will also be deployed, provided that they are listed for
deployment.
Scenarios
Scenario 1. An organization receives a shipment of machines from a manufacturer along with the list
of their MAC addresses. The IT department has to deploy the operating system to the new hardware.
Scenario 2. An Internet café, school or university lab has 100 machines with known MAC addresses.
The nightly deployment of the initial standard image on these machines is needed.










