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
© Acronis, Inc 79
Triggering conditions for scheduled deployment
13. Select the deployment template.
14. Set up the deployment schedule:
- One time only – the task will be executed once at the specified time and day
- Daily (or several times a day) - the task will be executed once a day or once in several days
- Weekly - the task will be executed once a week or once in several weeks on the selected day
- Monthly - the task will be executed once a month on the selected day
Do not forget that the target computers must be powered off or booted into the Acronis Snap
Deploy Agent before the scheduled time comes.
15. Review the scheduled task summary and click Proceed to save the task.
16. Select the Scheduled Deployment Tasks tab and make sure that the task is saved.
17. When the task is started, the connected computers’ IPs and the task progress will be displayed on
the Deployment tab.
18. When the task is finished, its log will be available in the Acronis OS Deploy Server log.
19.
13.3 Scheduled deployment in other subnet
Computers in other subnets can be woken through a WOL proxy. The WOL Proxy agent is delivered
with Acronis Snap Deploy.
When the scheduled time comes, Acronis OS Deploy Server sends out magic packets according to the
predefined list of MAC addresses. (A magic packet is a packet that contains 16 contiguous copies of
the receiving NIC's Ethernet address.) Acronis WOL Proxy transfers the packets to targets located in
other subnet. The targets wake, boot into Acronis Snap Deploy Agent from the Acronis PXE Server and
connect to the deploy server. When all (or some, depending on your choice) targets connect, the
deploy server starts multicasting.