Acronis acronis snap deploy 3 Manuel

Page de 103
 
© Acronis, Inc
                                                                                                                    
9
 
The administrator creates a script that performs pre-deployment operations, adds the script along with 
deployment script to the PE and includes both scripts in the 
startnet.cmd
 file. On booting into the PE, 
both operations will be performed automatically. 
 
4.  The administrator might need to execute imaging or deployment in Win PE environment if the 
Acronis environment lacks Linux drivers for some exotic hardware. 
 
Limitation: 
 
Acronis Snap Deploy command line utility can generate a new SID but cannot adjust other 
settings on the fly. To change the computer name, domain or workgroup membership and 
other settings, apply the Microsoft System Preparation Tool (Sysprep) to the master system 
and specify the new settings in the Sysprep.inf answer file. 
 
1.2.6  Standalone deployment (new in v 3) 
 
The administrator might need to deploy on a computer isolated from a network or included in a 
network without Acronis Snap Deploy infrastructure. A dedicated bootable utility enables full functional 
deployment with GUI on a standalone computer.  
 
The Acronis Universal Deploy option is not available in the standalone mode. 
 
1.2.7  Custom Deployment (User-initiated deployment) (new in v 3) 
 
Acronis Snap Deploy can be configured in such a way that users will be able to deploy and re-deploy 
their computers with one click on the boot menu.  
 
Scenarios: 
 
1.  Software testers have to deploy clean operating systems or preconfigured systems on test 
machines. A test team leader creates custom bootable media or a PXE package that provides a 
fixed set of choices on the target side. A test team member reboots a test computer and 
selects what to deploy from the boot menu with one click. The deployment starts immediately. 
 
The choices can be various operating systems, various editions of the same operating system, 
the same operating system with various settings or various applications, to name a few. The 
deployment proceeds independently on each computer. 
 
2.  The same scenario fits in a university or school lab when switching between exercises requires 
reconfiguring the computer entirely. Students can switch or restart exercises without the 
teacher’s assistance. 
 
If a student messes up the machine (deletes a file, changes configuration, etc.) then he/she 
could choose a self-restore option from the boot menu.  
 
The custom deployment mode is intended for continual work without the administrator’s assistance. 
Once the mode is set, other methods of deployment (manual, scheduled, event-driven deployment) 
become unavailable. Any scheduled task that has to start while the custom deployment mode is on, 
will not start. Only users (the ones on the target side) can initiate deployment. However, the 
administrator can view logs, create new deployment templates, change the custom deployment 
configuration (add, edit or remove boot menu items) and perform other management operations 
except for deployment. 
 
To initiate deployment on the console side, the administrator switches off the custom deployment 
mode.