User guide

Table Of Contents

Machines that do not support Wake-on-LAN can be booted into the Acronis environment manually

before the deployment starts. Such machines will also be deployed, provided that they are listed for

deployment.

Scenarios

Scenario 1. An organization receives a shipment of machines from a manufacturer along with the list

of their MAC addresses. The IT department has to deploy the operating system to the new hardware.

Scenario 2. An Internet café, school or university lab has 100 machines with known MAC addresses.

The nightly deployment of the initial standard image on these machines is needed.

1.3.3 Deployment to any ready machines (event-driven

deployment)

You can set up deployment to start when a specific number of any machines become ready. Unlike

deployment to specific machines (p. 8), this way of deployment does not require knowing the MAC

addresses of the machines.

The software counts how many machines have connected to the deployment server and starts

deployment when the number of machines you specified (for example, 10) is connected.

This way of deployment is also called event-driven deployment or deployment upon an event.

You can specify a time-out period. After the time-out, deployment will start on the machines that are

ready despite the fact that the predefined number is not reached.

Scenario

Your organization receives 100 machines from a manufacturer. You want to deploy the operating

system and programs to all these machines at once.

1. You set up a deployment operation that waits until any 100 machines are ready.

2. You boot each machine into the Acronis environment, by using either Acronis bootable media or

Acronis PXE (Preboot Execution Environment) Server.

3. Acronis Snap Deploy 5 uses multicasting to perform the deployment to all machines at once.

1.3.4 Stand-alone deployment

The administrator might need to perform deployment to a machine that is isolated from a network

or is included in a network without an Acronis Snap Deploy 5 infrastructure (such as the deployment

server or the license server). A dedicated bootable utility enables a fully-functional deployment with

the graphical user interface on a stand-alone machine.

The master image for deployment can be located in a network folder or on a removable drive (such

as a DVD) on the machine you are performing deployment to. The image cannot be located on the

local hard disk of the machine, because deployment usually involves overwriting the contents of the

disk.

1.3.5 Deployment with individual deployment settings

You can set up individual deployment settings (p. 130) for a machine. These settings will override the

general settings of the deployment operation (the deployment template).