Switches Used with DeployAnywhere
search cancel

Switches Used with DeployAnywhere

book

Article ID: 151771

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

What switches can be used when using the DeployAnywhere?

Resolution

The following switches are available:
Be aware that these switches are case sensitive and must be put in exactly as they are shown.

The diagnostic switches should be used with the build 2166 (or later) of DeployAnywhere.

DeployAnywhere (DA) command line switches:
/target
/ddb
/eval
/managed
/debug
/logPath
/logId
/findactivewindows
/capturesupportinfo
/byPassdrvVali
/notUseLegacyDriverInstaller

/target:
This switch should be used to indicate the location of the OS to be retargeted. An example: /target=c:

        /target=
        This switch is mandatory [it is the only one that is]
        /target=c: [DA searches c: for a suitable target]
        /target=c:\windows
        /target=1.1:
        /target=1.1:\windows

If /target is specified using a drive letter, it must be the drive letter as seen from the PreOS.

If positional notation is used DA will translate from the positional notation to the driver letter currently pointing to that physical partition. In GSS 2.5 DA uses GhConfig32.exe to perform the translation.

If /eval is not specified with /target then the target OS will be modified. If the retargeting does not succeed the target is left in an indeterminate state and the target may need to be re-imaged before another attempt at retargeting can be made.
If there are errors then they will be logged to GhDplyAw32.txt in the Current Working Directory (CWD).

Note:
* This file is always overwritten
* This file is never deleted

/ddb
This switch is used to indicate the location of the Deploy Anywhere Driver Database. An example: /ddb=d:\windrivers
        /ddb=
        Network drives need to be mapped using ‘net use’ command.
               Not specifying /ddb is equivalent to saying "do not use a driver database"
/eval
Performs an evaluation of the restored OS to ensure that mass storage controller driver and NIC drivers required for the retargeting to take place are present in the driver database
        Run in ‘evaluate’ mode – does not change the target in any way. i.e. it doesn’t perform the actual retargeting.
        Requires /target to be specified
        May be used with or without /ddb.
        If /ddb is not specified then /eval will report all critical drivers missing from the target
               If /ddb is specified then /eval will report all critical drivers missing from the target that are not in the driver database
/managed
        Outputs missing driver information to driver_list.txt in DAs CWD
        Cannot be used with both /eval and /debug but can be used with either
        In GSS 2.5 this switch is used to run DA from the Ghost console
        Example output:
        {
        v=0×8086 [vendor]
        d=0×10BD [device]
        s=0×02111028 [subsystem]
        r=02 [revision]
        o=XP [OS]
        m=Y [mandatory – always Y for critical devices]
        i= type = RETARGET_NETWORK_DEVICE PCI ID = PCI\VEN_8086&DEV_10BD&SUBSYS_02111028&REV_02 Desc = @oem36.inf,%e10bdnc.devicedesc%;Intel® 82566DM-2 Gigabit Network Connection [the information in a more presentable format]
        t=N [type N==network, S==storage]
               }
/debug
        Produces very verbose logging to GhDplyAw32.txt. By default this file is in the current working directory and it is overwritten each time it is created. each time it is created.
Note:
* The file is overwritten
* Is never deleted by DA/logPath
        /logPath=
        The path to ghdplyaw32.txt and driver_list.txt are affected by this parameter.
               May be used with /logId
/logId

                           /logId=

                           The names of ghdplyaw32.txt and driver_list.txt are affected by this parameter.
                           May be used with /logPath

/findactivewindows
                           This switch is used to locate the drive letter that Windows is installed on

 

/byPassDrvVali

                           =yes

                           This bypasses driver certificate validation

 

/notUseLeagacyDriverInstaller

                           As of GSS 3.3 RU10+ driver injection uses DISM instead of DPInst. To force driver injection to use DPInst then omit this parameter

 

Powered by Wolken Software