Bedienungsanleitung Acronis Snap Deploy 4 (Seite 139 von 145) (Englisch)

624427

139

Zoom out

Zoom in

Vorherige Seite

1/145

Nächste Seite

/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 posi

tion 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

upport 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

(p.

85).

/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 (p. 16

). 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 determin

e 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_licens

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 (p. 16

) to be taken for deploying a

workstation

operating system (p. 15). The server license will be used if no

Missbrauch melden von Frage und/oder Antwort

Libble nimmt den Missbrauch seiner Dienste sehr ernst. Wir setzen uns dafür ein, derartige Missbrauchsfälle gemäß den Gesetzen Ihres Heimatlandes zu behandeln. Wenn Sie eine Meldung übermitteln, überprüfen wir Ihre Informationen und ergreifen entsprechende Maßnahmen. Wir melden uns nur dann wieder bei Ihnen, wenn wir weitere Einzelheiten wissen müssen oder weitere Informationen für Sie haben.

Acronis Snap Deploy 4 Seite 139

Brauchen Sie Hilfe? Stellen Sie Ihre Frage.

Missbrauch melden von Frage und/oder Antwort

Art des Missbrauchs:

Forenregeln

Neu registrieren

Andere Handbücher von Acronis Snap Deploy 4

Das Handbuch wird per E-Mail gesendet. Überprüfen Sie ihre E-Mail.

Ihre Frage wurde zu diesem Forum hinzugefügt

Info