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 21
2.5 What is Acronis Universal Deploy
This section describes the Acronis proprietary technology that helps deploy and boot up Windows on
dissimilar hardware. Acronis Universal Deploy saves you from configuring a new master system for
each make of hardware you have to deploy on.
If you plan to deploy Windows on multiple computers that are identical to each other, but differ from
the master computer hardware; deploy the master image on one of the identical computers using
Acronis Universal Deploy. This will adjust Windows to the dissimilar hardware. Then image the
adjusted system and deploy it to the identical computers.
The Acronis Universal Deploy option is not available in the standalone mode.
2.5.1 Acronis Universal Deploy purpose
A system disk image can be deployed easily on the hardware where it was created or to identical
hardware. However, if you change a motherboard or use another processor version, the deployed
system could be unbootable. An attempt to transfer the system to a new, much more powerful
computer will usually produce the same unbootable result because the new hardware is incompatible
with the most critical drivers included in the image.
Using Microsoft System Preparation Tool (Sysprep) does not solve this problem, because Sysprep
permits adding drivers only for Plug-and-Play devices (sound cards, network adapters, video cards
etc.). As for the system Hardware Abstraction Layer (HAL) and mass storage device drivers, they must
be identical on the source and the target computers (see Microsoft Knowledge Base, articles 302577
and 216915).
Acronis Universal Deploy technology provides an efficient solution for hardware-independent system
deployment by adding the crucial Hardware Abstraction Layer (HAL) and mass storage device drivers.
2.5.2 Acronis Universal Deploy general principles
1. Automatic HAL and mass storage drivers selection
Acronis Universal Deploy searches the Windows default driver storage folders (in the image being
deployed) for HAL and mass storage device drivers and installs drivers that better fit the target
hardware. You can specify a custom driver repository (a folder or folders on a network share or CD)
which will also be used for drivers search.
The Windows default driver s
torage folder is determined in the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current version\DevicePath. This
storage folder is usually WINDOWS/inf.
2. Manual selection of mass storage device driver
If the target hardware has a specific mass storage controller (such as a SCSI, RAID, or Fibre Channel
adapter) for the hard disk, you can install the appropriate driver manually, bypassing the automatic
driver search-and-install procedure.
3. Installing drivers for plug and play devices
Acronis Universal Deploy relies on built-in plug and play discovery and configuration process to handle
hardware differences in devices that are not critical for the deployed system start-up, such as video,
audio and USB. Windows takes control over this process during the logon phase, and if some of the
new hardware is not detected, you will have a chance to install drivers for it later manually.