4.0
Table Of Contents
- 1 Introducing Acronis Snap Deploy 4
- 1.1 Overview
- 1.2 What you can do with Acronis Snap Deploy 4
- 1.2.1 Taking an image of the master system
- 1.2.2 Deployment to specific machines (immediate, manual, and scheduled deployment)
- 1.2.3 Deployment to any ready machines (event-driven deployment)
- 1.2.4 Stand-alone deployment
- 1.2.5 Deployment with individual deployment settings
- 1.2.6 User-initiated deployment (custom deployment)
- 1.2.7 Deployment of a disk volume and MBR
- 1.2.8 Command-line mode and scripting under WinPE
- 1.3 Features of Acronis Snap Deploy 4
- 1.3.1 New: List of machines
- 1.3.2 New: List of deployment tasks
- 1.3.3 New: Per-deployment licensing
- 1.3.4 New: Support for the VHD format
- 1.3.5 New: Graphical user interface in WinPE
- 1.3.6 New: E-mail notifications about deployment
- 1.3.7 New: Compatibility with Acronis True Image, Acronis Backup & Recovery 10, and Acronis Backup & Recovery 11 backups
- 1.3.8 New: Support for multiple network adapters
- 1.3.9 Multicast TTL and network bandwidth throttling
- 1.3.10 New: Falling back to unicast
- 1.3.11 Encrypted communication
- 1.3.12 Password protection
- 1.4 Supported operating systems for imaging and deployment
- 1.5 Licensing policy
- 1.6 Upgrading to Acronis Snap Deploy 4
- 1.7 Technical Support
- 2 Understanding Acronis Snap Deploy 4
- 3 Getting started with Acronis Snap Deploy 4
- 4 Installation of Acronis Snap Deploy 4
- 4.1 Supported operating systems
- 4.2 Used ports and IP addresses
- 4.3 Typical installation
- 4.4 Custom installation
- 4.4.1 Installation procedure
- 4.4.2 Common installation configurations
- 4.4.3 Installation of components
- 4.4.3.1 Installation of Acronis Snap Deploy 4 Management Console
- 4.4.3.2 Installation of Acronis Snap Deploy 4 License Server
- 4.4.3.3 Installation of Acronis Snap Deploy 4 OS Deploy Server
- 4.4.3.4 Installation of Acronis PXE Server
- 4.4.3.5 Installation of Acronis Wake-on-LAN Proxy
- 4.4.3.6 Installation of Acronis Snap Deploy 4 Management Agent
- 4.4.3.7 Installation of Acronis Universal Deploy
- 4.5 Other ways of installation
- 4.6 Upgrading Acronis Snap Deploy 4
- 4.7 Uninstalling Acronis Snap Deploy 4
- 5 Using Acronis Snap Deploy 4 Management Console
- 6 Using Acronis Snap Deploy 4 License Server
- 7 Deployment tools
- 8 Creating a master image
- 9 Validating a master image
- 10 Deploying a master image
- 10.1 Files supported as master images
- 10.2 Licenses for deployment
- 10.3 Deployment templates
- 10.4 Deployment through a deployment task
- 10.5 Stand-alone deployment
- 10.6 User-initiated deployment (custom deployment)
- 11 Managing the list of machines (the Machines view)
- 12 Individual deployment settings
- 13 Managing deployment tasks (the Deployment tasks view)
- 14 Command-line mode and scripting under WinPE
- 15 Collecting system information
61 Copyright © Acronis, Inc., 2000-2011
§ No autostart: The Acronis loader will display the boot menu and wait for someone to select
whether to boot the operating system or one of the Acronis components.
§ Start operating system: The operating system, if present on the booting machine’s hard disk,
will start after the time-out. This option is designed to make the target machine boot into the
deployed operating system after deployment. The main usage scenario is as follows.
You use this wizard to configure the PXE server for deployment on a schedule (p. 100).
You set up Acronis Snap Deploy 4 Agent to start automatically. After the deployment is
completed, the target machine reboots into the agent again and might be deployed by
another deployment operation. How to avoid this situation?
To ensure that the target machine boots into the deployed operating system after the
deployment, choose the Start operating system option in this step of the wizard. To
ensure that the target machine boots into the agent before the deployment, tune the PXE
server to work with your deployment server when setting up the deployment (p. 102).
5. Under Start automatically after, specify the time-out interval in seconds. For example, if you
choose to automatically start Acronis Snap Deploy 4 Agent, and set this parameter to 10, the
agent will launch 10 seconds after the boot menu is displayed.
6. If you are placing Acronis Snap Deploy 4 Agent on the media, specify whether the agent will
connect to a particular Acronis Snap Deploy 4 OS Deploy Server. This setting allows you to have
multiple deployment servers that perform different functions on the same network.
To specify a deployment server, type its name or IP address in Server name/IP.
The deployment server (along with the network settings for the agent) can also be specified
onsite (on the target machine’s side) when booting the agent. To be able to configure the agent
onsite, set up a reasonable delay before the default network settings will be applied. For details,
see “Booting the target machines” (p. 108).
If not configured in either way, the deployment server will be found automatically. The agent will
start the search after the number of seconds you specify in Timeout (sec).