Option |
Description |
create |
|
/harddisk:<disk number> |
Specifies the hard disks to include into the image. An image may contain data of more than one hard disk. In that case, separate disk numbers by commas, for example: /harddisk:1,3 To view the list of available hard disks, use the /list command. |
/partition:<disk number>-<volume number> |
Specifies the volumes to include into the image file. Volume numbers are specified as <disk number>-<volume number>, for example: /partition:1-1,1-2,3-1 See also the /oss_numbers parameter. To view the list of available volumes, use the /list command. |
/raw |
Use this parameter to create an image of a volume with an unrecognized or unsupported file system, or of a disk that contains such volume. With this parameter, all contents of the disk or volume will be copied sector-by-sector. Without this parameter, only the sectors containing useful system and user data are imaged (for the supported file systems). |
/progress:<on|off> |
Shows or hides the progress information (percent completed). The progress is shown by default. |
deploy |
|
/harddisk:<disk number> |
Specifies the hard disk in the image. |
/partition:<disk number>-<volume number> |
Specifies the volumes in the image. |
/target_harddisk:<disk number> |
Specifies the target hard disk. |
/target_partition:<volume number> |
Specifies the target volume number for deploying a volume over an existing one. If this parameter is not specified, the software assumes that the target volume number is the same as the volume number specified with the /partition parameter. |
/start:<start sector> |
Sets the start sector for deploying a volume to the unallocated space on the hard disk. |
/size:<volume size in sectors> |
Sets the new size of the volume in sectors. The size of a sector is considered to be 512 bytes, regardless of the physical sector size on the hard disk drive. For example, if you want the volume size to be 512 MB (a megabyte is 1 048 576 bytes), specify the size as follows: /size:1048576 Specify this size even if you are using a hard disk drive with 4-KB sectors. To see the size of the volume in the master image, use the /list command. |
/fat16_32 |
Enables the file system conversion from FAT16 to FAT32 if the volume size after deployment is likely to exceed 2 GB. Without this parameter, the deployed volume will inherit the file system from the image. |
/restore_bootable:<auto|on|off> |
Sets the rule of deployment for the master boot record (MBR) when deploying a volume (when deploying a disk, MBR is always deployed):
|
/type:<active|primary|logical> |
Sets the deployed volume to active, primary or logical, if possible (for example, there cannot be more than four primary volumes on a disk). Setting a volume to active always sets it to primary, but a volume that is set to primary may remain non-active. If the type is not specified, the software tries to keep the target volume type. If the target volume is active, the deployed volume is set to active. If the target volume is primary and there are other primary volumes on the disk, one of them will be set to active, and the deployed volume becomes primary. If no other primary volumes remain on the disk, the deployed volume is set to active. When deploying a volume to unallocated space, the software extracts the volume type from the image. For a primary volume, the type will be set as follows:
|
/preserve_mbr |
When deploying a volume over an existing one, the target volume is deleted from the disk along with its entry in the target disk’s master boot record (MBR). Then, with the /preserve_mbr parameter, the deployed volume’s entry will occupy the upper empty position in the target disk’s MBR. Thus, the target disk’s MBR is preserved. Without this parameter, the deployed volume’s entry will occupy the same position as in the source disk MBR saved in the image. If the position is not empty, the existing entry will be moved to another position. |
/preserve_disk_layout |
When deploying an MBR disk or volume with a convertible OS, and the target drive is larger than 2 TB, the target drive is converted to GPT by default. To disable this default behavior and preserve the MBR disk layout on the deployed machine, use /preserve_disk_layout parameter. This may be useful when are deploying an image to a machine that does not support UEFI architecture and thus cannot boot from a GPT volume. This parameter is an equivalent for the deployment template option Convert disk to GPT if target disk is larger than 2 TB. |
/patching_sid |
Generates a unique security identifier (SID) for the target machine. Without this parameter, the target machine will have the same SID as the master machine. |
The following parameters related to licensing are effective only when booting from Acronis PXE Server. You do not need to use these parameters when booting from a physical media. Deployment is performed by using a deployment license or a machine license. By default, the software uses a machine license only if no appropriate deployment license is found on the license server. By using the /use_deployment_license and /use_machine_license parameters, you can force a particular type of license to be used for performing the deployment. If you specify both of these parameters, their order will determine license priority. For example, if you specify /use_machine_license /use_deployment_license, the software will use a machine license; if no machine license is found on the license server, the software will use a deployment license instead. |
|
/license_server:<server IP address> |
Specifies the IP address of Acronis Snap Deploy 4 License Server. |
/use_deployment_license |
Forces a deployment license to be used for deployment. If no deployment license is found, the deployment will fail. By using this parameter with the /grant_server_license parameter, you can allow a server deployment license to be taken if no workstation deployment license is found on the license server. |
/use_machine_license |
Forces a machine license to be used for performing the deployment. If no machine license is found, the deployment will fail. By using this parameter with the /grant_server_license parameter, you can allow a server machine license to be taken if no workstation machine license is found on the license server. |
/grant_server_license |
Allows a server license to be taken for deploying a workstation operating system. The server license will be used if no workstation license is found on the license server. By default, when you use this parameter and deploy a workstation operating system, the software uses the following priorities for licenses, from highest to lowest:
By using this parameter with the /use_deployment_license parameter, the /use_machine_license parameter, or both, you can force a particular type of license to be used for performing the deployment or change the priorities for licenses. |
To use the following parameters, you must have a license for the Universal Deploy add-on. Acronis Snap Deploy 4 License Server with the licenses must be available from the machine booted into the PE. For more details, see “What is Acronis Universal Deploy”. |
|
/ud_path:<path to driver storage> |
Specifies using Acronis Universal Deploy, the path to the drivers storage (in a network folder), and the user name and password to access the folder. |
/ud_driver:<inf-file name> |
Specifies using Acronis Universal Deploy, and the mass-storage driver to be installed. The driver is specified as an .inf file. |
list |
|
/filename:<file name> |
Displays the image content. When listing image content, volume numbers may not coincide with those in the list of disks and volumes if the image does not contain all the volumes. For example, if the image contains only volumes 2-3 and 2-5, they will be listed as 2-1 and 2-2. If the deploy /partition command cannot find a volume in the image by its physical number, use the list command to obtain the volume number in the image. Then, use the /partition:<number in the image> /target_partition:<physical number of the target volume> parameters. In the example above, to deploy the volume 2-5 to its original place, use: /partition:2-2 /target_partition:2-5 |
email_n |
|
/email_from:<sender address> |
Specifies the e-mail address of the sender. For example: /email_from:user@example.com |
/email_to:<recipient address> |
Specifies the e-mail address of the recipient. For example: /email_to:admin@example.com |
/email_subject:<message subject> |
Specifies the custom text in the subject line of the e-mail message. For example: /email_subject:"Deployment notification" In addition to the custom text, the subject line will include the text “[ASD4]”, and the MAC address and the IP address of the machine being deployed. |
/email_smtp:<SMTP server address> |
Specifies the name or IP address of the outgoing (SMTP) server. For example: /email_smtp:smtp.example.com |
/email_port:<SMTP server port> |
Specifies the port of the SMTP server. For example: /email_port:465 Without this parameter, port 25 is used. |
/email_user:<SMTP server user name> |
Specifies the user name to log on to the SMTP server. For example: /email_user:user |
/email_password:<SMTP server user password> |
Specifies the password to log on to the SMTP server. For example: /email_password:MyPassWd |
/email_encryption:<no|ssl|tls> |
Specifies the type of encryption that is used by the SMTP server. For example: /email_encryption:tls Without this parameter, no encryption is used. |
email_n_test |
|
Use this command instead of the email_n command, with the same set of parameters, to test the configuration of e-mail notifications. |
|