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

78 © Acronis, Inc
10. Select Wake-on-LAN.
11. The next window suggests that you tune the PXE server to use with the deployment server you
are connected to. The goal of this setting is to boot the woken machine into Acronis Snap Deploy
Agent even if another component on the PXE server is configured to start automatically.
The tuned PXE Server will redirect the boot menu configuration requests that come from the
booting machines, to the current OS Deploy Server. The deploy server responds with the file
specifying the boot menu item for the given MAC address. If the MAC address of the booting
machine is included in the list of target MAC addresses, the machine will boot into Acronis Snap
Deploy Agent, despite that Booting from HDD is configured as the default boot menu item.
Tuning a PXE server implies that you can guarantee that the woken machines will be served by
this PXE server. Normally, you have only one PXE server in the given subnet.
Once tuned to the certain OSDS, the PXE server remains tuned at this setting unless it is tuned to
another OSDS by another scheduled task. If this setting has never been configured, the woken
machine will boot into the component that is configured to start automatically.
Type in “localhost” if the PXE server and the deployment server are on the same machine.
Tune PXE server
12. Select whether to start deployment one-by-one, as computers connect to the deploy server, or to
wait for all the computers to connect.
In practical situations, some of the listed computers might not connect because they are in use,
for example. One-by-one deployment task will continue waiting for missing computers, while the
rest of the computers are already deployed. Because it may not be practical or efficient for you to
have the task suspended (especially a periodic task), the program allows you to specify the
maximum waiting time and the minimum number of computers on which the deployment will start
when the time is out.