Operation Manual
Table Of Contents
- Table of Contents
- 1. Introducing Acronis® Snap Deploy®
- 1.1 Overview
- 1.2 What you can do with Acronis Snap Deploy 3
- 1.2.1 Take an image of the master system (Acronis Snap Deploy 2.0 functionality)
- 1.2.2 Manual deployment (Acronis Snap Deploy 2.0 functionality)
- 1.2.3 Scheduled deployment (new in v 3)
- 1.2.4 Event-driven deployment (new in v 3)
- 1.2.5 Command line and scripting under Win PE (new in v 3)
- 1.2.6 Standalone deployment (new in v 3)
- 1.2.7 Custom Deployment (User-initiated deployment) (new in v 3)
- 1.2.8 Deployment of a disk partition or MBR (new in v 3)
- 1.2.9 Selective deployment (MAC filtering) (new in v 3)
- 1.2.10 Password protection (new in v 3)
- 1.2.11 Manage a remote computer (Acronis Snap Deploy 2.0 functionality)
- 1.3 What else is new in v 3?
- 1.4 Supported operating systems
- 1.5 License policy
- 1.6 Upgrade to v 3
- 1.7 Technical support
- 2. Understanding Acronis Snap Deploy
- 3. Installation
- 3.1 System requirements
- 3.2 Used ports and IP addresses
- 3.3 General rules of installation
- 3.4 Installation of Acronis Snap Deploy Management Console
- 3.5 Installation of Acronis License Server
- 3.6 Installation of Acronis OS Deploy Server
- 3.7 Installation and setup of Acronis PXE Server
- 3.8 Installation of Acronis WOL Proxy
- 3.9 Installation of Acronis Snap Deploy Management Agent
- 3.10 Installation of Acronis Universal Deploy
- 3.11 Extracting the Acronis Snap Deploy components
- 3.12 Using Acronis License Server
- 4. Using Acronis Snap Deploy Management Console
- 5. Creating Acronis bootable media
- 6. Configuring PXE Server
- 7. Taking an image
- 8. Checking the master image
- 9. Deployment templates
- 9.1 Why save templates?
- 9.2 Creating templates
- 9.2.1 Master image selection
- 9.2.2 Disk/partition selection
- 9.2.3 Target disk and partition selection
- 9.2.4 User accounts
- 9.2.5 Computer names and domain/workgroup
- 9.2.6 Network settings
- 9.2.7 Security identifiers
- 9.2.8 Transferring files
- 9.2.9 Executing applications
- 9.2.10 Using Acronis Universal Deploy
- 9.2.11 Deployment options
- 9.2.12 Comments and summary
- 10. Standalone deployment
- 11. Manual deployment
- 12. Event-driven deployment
- 13. Scheduled deployment
- 14. Custom deployment mode
- 15. Command line and scripting under Win PE and Bart PE
- 16. Managing a remote computer

8 © Acronis, Inc
Scenarios:
1. An organization receives a shipment of computers from a manufacturer along with the list of
their MAC addresses. The IT department has to deploy the operating system to the new
hardware.
2. An Internet café, school or university lab has 100 computers with known MAC addresses. The
nightly deployment of the initial standard image on these computers is needed.
1.2.4 Event-driven deployment (new in v 3)
Deployment can be run when the predefined number of computers is ready. The program counts how
many computers have connected to the deployment server and starts multicasting when the
predefined number of computers is connected.
The administrator can specify a time-out period. On time-out, deployment will start on the computers
that are ready despite that the predefined number is not reached.
Scenario:
1. An organization receives 100 computers from a manufacturer. The IT department has to
deploy systems, preconfigured according to the employees’ roles, to the predefined number of
computers. For example, 10 computers for accountants, 10 computers for the marketing
department, 70 computers for sales and 10 for the managers.
1.2.5 Command line and scripting under Win PE (new in v 3)
Acronis Snap Deploy provides a command line utility that can be added to a Windows Preinstallation
Environment (Win PE) image. The administrator uploads the customized PE image to a PXE server or
transfers the PE image onto removable media.
Having booted a machine in the Preinstallation Environment, the administrator can perform imaging or
deployment in the command line mode or execute scripts.
Using Acronis Snap Deploy in Windows Preinstallation Environment allows a combination of both the
products facilities and provides more functionality than using only-Acronis bootable media. The
following scenarios can be implemented using Acronis Snap Deploy command line and Win PE.
Scenarios:
1. The administrator might need to deploy diverse images on each of the networked computers.
The administrator writes a deployment script that can read the target’s MAC address (for example, 01-
02-03-04-05-06) and pull an image with a name corresponding to the MAC address (for example,
image-01-02-03-04-05-06.tib) from any convenient location. The script can be executed on any
number of targets.
2. The administrator might need to start imaging or deployment automatically each time a
networked computer boots from the PXE server.
The administrator creates an imaging or deployment script, adds the script to the PE and includes the
script in the
startnet.cmd
file. On booting into the PE, the operation will be performed automatically.
3. The administrator might need to automatically execute pre-deployment operations (disk
partitioning, for example) on the networked computers.