Acronis Snap Deploy 4 - User Guide - Manual (Page 100)

100 Copyright © Acronis International GmbH, 2002-2012
The preset is: Extend or reduce the volumes being deployed, according to the available space on
the target disk
 Machine name and membership (p. 88)
The preset is: The same as of the master system
 TCP/IP properties (p. 90)
The preset is: The network settings of the master system
 User accounts (p. 91)
The preset is: Create no additional user accounts
 Security identifiers (p. 92)
The preset is: Generate a unique security identifier (SID) for each target machine
 Action after deployment (p. 92)
The preset is: Shut down the machine after the deployment
 Network utilization (p. 93)
The preset is:
 Perform deployment by using multicast
 Switch to unicast if multicast fails
 Licensing (p. 95)
The preset is:
 Use a deployment license of the corresponding type (a server license or a workstation
license)
 If no such deployment license is found, use a machine license of the same type
 Stop deployment otherwise
10.3.3 Managing deployment templates
In the Templates window, you can create, view, edit, and delete the deployment templates that are
saved on Acronis Snap Deploy 4 OS Deploy Server.
To open this window, click Actions -> Manage templates. If prompted, specify the name or IP
address of the machine with the deployment server, and the user name and password of an
administrator on that machine.
To create a deployment template
1. Connect the management console to Acronis Snap Deploy 4 OS Deploy Server.
2. On the Actions menu, click Manage templates.
3. Click Create new, and then follow the steps of the Create Deployment Template Wizard (p. 81).
10.4 Deployment through a deployment task
By using a deployment task, you can perform deployment in either of these ways:
 Deployment to a specified list of machines (p. 101). Acronis Snap Deploy 4 will use the Wake-on-
LAN functionality to wake up the machines that are turned off and thus are not ready for
deployment.
 Deployment as soon as a specified number of any machines become ready for deployment (p.
107). You (or users in your organization) will need to make the machines ready.