User guide

Table Of Contents

The task appears in the Deployment tasks view. When the task is started, the connected machines’

IP addresses and the task progress are displayed in that view.

When the task is finished, its log entries will be available in the log of the deployment server.

10.4.2.3 Deployment in another subnet

Machines in another subnet (behind a network switch or router) can be woken up through the

Acronis Wake-on-LAN Proxy component.

If Acronis Snap Deploy 5 OS Deploy Server is installed in one subnet (Subnet 1) and the target

machines in another subnet (Subnet 2), prepare deployment as follows:

1. Install Acronis Wake-on-LAN Proxy in Subnet 2.

2. Prepare Acronis PXE Server in either of these ways:

 Install the PXE server in Subnet 2 and configure that PXE server. This way, only machines in

Subnet 2 can boot to the PXE server.

 Install the PXE server in Subnet 1. Enable this PXE server to also work in Subnet 2 by

configuring the network switch to relay the PXE traffic. The PXE server’s IP addresses are

configured on a per-interface basis using IP helper functionality in the same way as DHCP

server addresses. For more information, see

http://support.microsoft.com/default.aspx/kb/257579. This way, machines from both

subnets can boot to this PXE server.

Deployment in another subnet by using Acronis Wake-on-LAN Proxy. The network switch is

configured to relay the PXE traffic and DHCP traffic.

3. Create the deployment task (p. 105). When creating the deployment task, specify the

Wake-on-LAN proxy and specify the PXE server that you prepared in the previous step.

Note: If your router also acts as a Network Address Translation (NAT) device, see also “Deployment behind an

NAT device” (p. 115).

10.4.3 Deployment to any ready machines

Deployment to any ready machines starts when a specified number of machines becomes ready.

Acronis Snap Deploy 5 OS Deploy Server counts how many machines have connected to it, and starts