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 29
3.7 Installation and setup of Acronis PXE Server
Acronis PXE Server allows the network booting of the Acronis Snap Deploy Agent, Acronis Master
Image Creator or Preinstallation Environment on target computers. Using Acronis PXE Server
considerably reduces the time required for booting the computers as compared to using bootable
media. It also eliminates the need to have a technician onsite to install the bootable media into the
system that must be booted. This allows for unattended scheduled deployment.
Using Acronis PXE Server makes sense if there is a Dynamic Host Control Protocol (DHCP) server in
your network, so that the booting computers can automatically get IP addresses. Without DHCP, you
cannot boot computers from PXE.
We recommend that you have only one PXE server within a subnet to ensure predictability of the
booting computers behavior.
3.7.1 Installation of Acronis PXE Server
To install Acronis PXE Server:
1. Run the Acronis Snap Deploy setup program
2. Click Install Acronis PXE Server
3. Follow the on screen Install Wizard instructions.
Acronis PXE Server runs as a service immediately after installation. Later on it will automatically launch
at each system restart. You can stop and start this program in the same way as other services.
3.7.2 Setting up a computer to boot from PXE
For bare metal, it is enough that the machine’s BIOS supports network booting.
On a machine that has an operating system on the hard disk, the BIOS must be configured so that the
network interface card is either the first boot device, or at least prior the Hard Drive device. The
example below shows one of reasonable BIOS configurations. If you don’t insert bootable media, the
computer will boot from the network.
Setting up the BIOS (example) for network boot