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 95
/type:[active | primary
| logical]
Sets the deployed partition to active, primary or logical, if possible
(for example, there cannot be more than four primary partitions on
the disk.) Setting a partition to active always sets it to primary,
while a partition set to primary may stay inactive.
If the type is not specified, the program tries to keep the target
partition type. If the target partition is active, the deployed partition
is set to active. If the target partition is primary, and there are other
primary partitions on the disk, one of them will be set to active,
while the deployed partition becomes primary. If no other primary
partitions remain on the disk, the deployed partition is set to active.
When deploy
ing a partition on unallocated space, the program
extracts t
he partition type from the image. For the primary
partition, the type will be set as follows:
- if the target disk is the 1st according to BIOS and it has no other
primary partitions, the deployed partition will be set to active
- if the target disk is the 1st according to BIOS and there are other
primary partitions on it, the deployed partition will be set to logical
- if the target disk is not the 1st, the deployed partition will be set
to logical.
/preserve_mbr
When deploying a partition over an existing one, the target partition
is deleted from the disk along with its entry in the target disk MBR.
Then, with the /preserve_mbr option, the deployed partition’s
entry will occupy the upper empty position in the target disk MBR.
Thus, the target disk MBR is preserv
ed. If not specified, the
deployed partition’s entry will occupy the same position as in the
source disk MBR saved in the image. If the position is not empty,
the existing entry will be moved to another position.
/patching_sid
Generate the unique s
ecurity identifier (SID) for the target
computer. If not specified, the SID of the master system will be
preserved.
/license_server:[the
server IP]
Specifies the license server if the PE was booted from the PXE
server.
/grant_server_license
Permits to take a server product license for deploying a workstation
operating system (if the PE was booted from PXE server.)
To use the following options you must have the Acronis Universal Deploy add-on in your PE. Also, the
Acronis License Server must be accessible from the computer booted into the PE.
For more
information see
2.5 What is Acronis Universal Deploy.
/ud_path:[path]
/ud_username:[user]
/ud_password:[pwd]
Specifies using Acronis Universal Deploy and the path to the drivers
storage.
/ud_driver:[inf-filename]
Specifies using Acronis Universal Deploy and the mass-storage
driver to be installed.