Acronis acronis snap deploy 3 Manual

 

 

To find the target template in custom boot menu templates list, press a letter key which corresponds to 
the first letter of the template name. The cursor will jump on a template, which name begins with the 
pressed letter.

 

 

The custom deployment mode is intended for continual work without 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. 
 

 

When enabling or configuring the custom deployment mode with PXE, the program first removes all 

bootable utilities (Acronis Snap Deploy Agent, Acronis Master Image Creator, PE image) from the PXE 
server since users might be confused by the unknown items appearing in the boot menu. Then the 

program uploads to the PXE the templates selected by the administrator. So you will have to upload 

the bootable utilities again, if they are needed after switching off the custom deployment mode. 

 

You can use another Acronis OS Deploy Server to perform manual, scheduled or event-driven 

deployment while one OS Deploy Server is in the custom deployment mode. To do so, ensure that the 
targets connect to the appropriate deployment server by specifying the OSDS on the bootable media 

or by configuring the Acronis Snap Deploy Agent at boot up. The deploy servers cannot share the 

Acronis PXE Server though.