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
6 © Acronis, Inc
1. Introducing Acronis® Snap Deploy®
This chapter gives a general idea of how an IT department can meet various real life challenges using
the Acronis Snap Deploy.
1.1 Overview
1.1.1 What is Acronis Snap Deploy
Acronis Snap Deploy is a flexible, efficient software solution for deployment of a fully configured
operating system (with or without application software and any other data) to multiple computers.
Because the product uses disk imaging technology, it is ideal for rapid bare-metal installations and
flexible centralized provisioning.
1.1.2 Who needs Acronis Snap Deploy?
Acronis Snap Deploy is primarily designed to be used by:
Small and medium-size businesses:
- IT service providers
- Hardware retailers
IT departments of larger corporations
Schools and universities
R&D and software testing labs.
The enterprise features added to Acronis Snap Deploy v 3 (scheduled deployment, support for
Preinstallation Environment, command line and scripting, to name a few) can help automate the tasks
of the IT department in large enterprise environments.
1.1.3 Acronis Snap Deploy infrastructure
Components of the Acronis infrastructure are installed on Windows computers. Centralized imaging,
deployment and managing the Acronis infrastructure is performed using Acronis Snap Deploy
Management Console.
A reference image can be taken either in Windows or in the Acronis or Windows PE environment. The
Acronis environment provides the GUI mode. Under Windows PE, command line mode and scripting
are supported.
Deployment is performed in the Acronis or Windows PE environment.
A dedicated bootable utility enables full functional deployment with GUI on a standalone computer (a
computer isolated from the network or included in a network without Acronis Snap Deploy
infrastructure.)