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
70 © Acronis, Inc
While creating bootable media or uploading Acronis Snap Deploy Agent on the PXE server, the
agent can be configured to start automatically on timeout.
5. The agent has to establish network connection to be able to connect to Acronis OS Deploy Server.
A dialog box comes up suggesting that you configure the network connection used by Acronis
Snap Deploy Agent.
Prompt for configuring the agent on the target side
By default, the agent will use DHCP auto configuration and connect to the first deploy server that
is found on the network. You can ignore the prompt (click Cancel) if there is a DHCP server and
only one Acronis OS Deploy Server on the network. The agent can be pre-configured to apply the
default settings automatically on timeout.
To configure the network connections manually, click OK in the prompt window. You can set up:
- TCP/IP settings for each network interface of the target computer.
Acronis Snap Deploy Agent uses DHCP auto configuration by default. The manual configuration is
needed if auto configuration is not possible (no DHCP server on the network) or does not succeed.
- The Acronis OS Deploy Server the agent will connect to.
This setting allows you to have multiple deployment servers that perform different functions on
the same network. The deployment server can be specified also when creating bootable media
with Acronis Snap Deploy Agent. If not specified in either way, the server will be found
automatically.
Configuring the agent on the target side
Set the preferable values and click OK.