User guide
Table Of Contents
- 1 Introducing Acronis Snap Deploy 5
- 1.1 Overview
- 1.2 What's new in Acronis Snap Deploy 5
- 1.3 What you can do with Acronis Snap Deploy 5
- 1.3.1 Taking an image of the master system
- 1.3.2 Deployment to specific machines (immediate, manual, and scheduled deployment)
- 1.3.3 Deployment to any ready machines (event-driven deployment)
- 1.3.4 Stand-alone deployment
- 1.3.5 Deployment with individual deployment settings
- 1.3.6 User-initiated deployment (custom deployment)
- 1.3.7 Deployment of a disk volume and MBR
- 1.3.8 Command-line mode and scripting under WinPE
- 1.4 Features of Acronis Snap Deploy 5
- 1.4.1 List of machines
- 1.4.2 List of deployment tasks
- 1.4.3 Per-deployment licensing
- 1.4.4 Support for the VHD format
- 1.4.5 Graphical user interface in WinPE
- 1.4.6 E-mail notifications about deployment
- 1.4.7 Compatibility with images created by other Acronis products
- 1.4.8 Support for multiple network adapters
- 1.4.9 Multicast TTL and network bandwidth throttling
- 1.4.10 Falling back to unicast
- 1.4.11 Encrypted communication
- 1.4.12 Password protection
- 1.5 Supported operating systems for imaging and deployment
- 1.6 Licensing policy
- 1.7 Upgrading to Acronis Snap Deploy 5
- 1.8 Technical Support
- 2 Understanding Acronis Snap Deploy 5
- 3 Getting started with Acronis Snap Deploy 5
- 4 Installation of Acronis Snap Deploy 5
- 4.1 Supported operating systems
- 4.2 System requirements
- 4.3 Used ports and IP addresses
- 4.4 Typical installation
- 4.5 Custom installation
- 4.5.1 Installation procedure
- 4.5.2 Common installation configurations
- 4.5.3 Installation of components
- 4.5.3.1 Installation of Acronis Snap Deploy 5 Management Console
- 4.5.3.2 Installation of Acronis Snap Deploy 5 License Server
- 4.5.3.3 Installation of Acronis Snap Deploy 5 OS Deploy Server
- 4.5.3.4 Installation of Acronis PXE Server
- 4.5.3.5 Installation of Acronis Wake-on-LAN Proxy
- 4.5.3.6 Installation of Acronis Snap Deploy 5 Management Agent
- 4.6 Other ways of installation
- 4.7 Upgrading Acronis Snap Deploy 5
- 4.8 Uninstalling Acronis Snap Deploy 5
- 5 Using Acronis Snap Deploy 5 Management Console
- 6 Using Acronis Snap Deploy 5 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)
- 10.7 Deploying BIOS-based systems to UEFI-based and vice versa
- 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
140 Copyright © Acronis International GmbH, 2002-2014
/patching_sid
Generates a unique security identifier (SID) for the target machine.
Without this parameter, the target machine will have the same SID as the
master machine.
/ud_path:<path to driver
storage>
/ud_username:<user name>
/ud_password:<password>
Specifies using Acronis Universal Deploy, the path to the drivers storage (in
a network folder), and the user name and password to access the folder.
/ud_driver:<inf-file name>
Specifies using Acronis Universal Deploy, and the mass-storage driver to be
installed. The driver is specified as an .inf file.
The following parameters related to licensing are effective only when booting from Acronis PXE Server. You do
not need to use these parameters when booting from a physical media.
Deployment is performed by using a deployment license or a machine license (p. 16). By default, the software
uses a machine license only if no appropriate deployment license is found on the license server.
By using the /use_deployment_license and /use_machine_license parameters, you can force a
particular type of license to be used for performing the deployment. If you specify both of these parameters,
their order will determine license priority. For example, if you specify
/use_machine_license /use_deployment_license, the software will use a machine license; if no
machine license is found on the license server, the software will use a deployment license instead.
/license_server:<server IP
address>
Specifies the IP address of Acronis Snap Deploy 5 License Server.
/use_deployment_license
Forces a deployment license to be used for deployment. If no deployment
license is found, the deployment will fail.
By using this parameter with the /grant_server_license parameter,
you can allow a server deployment license to be taken if no workstation
deployment license is found on the license server.
/use_machine_license
Forces a machine license to be used for performing the deployment. If no
machine license is found, the deployment will fail.
By using this parameter with the /grant_server_license parameter,
you can allow a server machine license to be taken if no workstation
machine license is found on the license server.
/grant_server_license
Allows a server license (p. 16) to be taken for deploying a workstation
operating system (p. 14). The server license will be used if no workstation
license is found on the license server.
By default, when you use this parameter and deploy a workstation
operating system, the software uses the following priorities for licenses,
from highest to lowest:
1. Deployment workstation licenses
2. Machine workstation licenses
3. Deployment server licenses
4. Machine server licenses
By using this parameter with the /use_deployment_license
parameter, the /use_machine_license parameter, or both, you
can force a particular type of license to be used for performing the
deployment or change the priorities for licenses.
list