About command-line switches for DeployAnywhere.exe
search cancel

About command-line switches for DeployAnywhere.exe

book

Article ID: 185285

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

Description of the command-line switches for DeployAnywhere

Resolution

About command-line switches for DeployAnywhere.exe

The command-line switches for DeployAnywhere lets you troubleshoot the drivers of the DeployAnywhere database.

The command-line switches for DeployAnywhere.exe are as follows:

Table: Switches for DeployAnywhere.exe

Switch

Usages

/target

The usage of this switch is as follows:

/target=<path to target windows dir>

/ddb

The usage of this switch is as follows:

/ddb=<path to driver database>

/bypassDrvVali

The usage of this switch is as follows:

/byPassDrvVali=[All | Inf | Drv]

/Loglevel

The usage of this switch is as follows:

/Loglevel=[1-255]

/eval

This switch runs DeployAnywhere in evaluation mode. It can 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.

/skipMissingCriticalDrivers

The usage of this switch is that DeployAywhere executes even when drivers for critical devices are missing.

/handleNonCriticalDrivers

The usage of this switch is that it turns on non-critical device handling, the switch lets you find and retarget matching non critical drivers. You can provide 3 inputs that are as follows:

  • miniSetup

    non-critical driver installation and upgrading occurs during mini-setup

  • adminLogon

    non-critical driver installation and upgrading occurs at first admin logon. This may require a further reboot after driver installation

  • user

    non-critical driver installation and upgrading occurs when the user runs c:\drivers\symantec\non-critical\run_dpinst.bat. This may require a further reboot after driver installation [requires admin privileges to succeed].

/logPath

The usage of this switch is as follows:

/logPath=<directory for log output>

/logId

/logId=<id prepended to log files >

/managed

The usage of this switch is that it specifies that DeployAnywhere is run in managed mode.

/precheck

-

/targetOS

The usage of this switch is as follows:

/targetOS=[ 2000 | X64_XP | XP | X64_2003 | 2003 | X64_VISTA | VISTA | X64_2008 | 2008 | X64_WINDOWS7 | WINDOWS7 | X64_2008_R2 | X64_WINDOWS8 | WINDOWS8 | X64_2012 | X64_WINDOWS8_1 | WINDOWS8_1 | X64_2012_R2 | X64_WINDOWS10 | WINDOWS10 | X64_2016 | X64_2019 | X64_2022 | X64_WINDOWS11 ]

/reportNonCriticalDevices

The usage of this switch is that it forces DeployAnywhere to report all non-critical devices.

/p2v

The usage of this switch is as follows:

/p2v=[vmdk | vhd]

/pathToVirtualDisk

The usage of this switch is as follows:

/pathToVirtualDisk=<path to the virtual disk>

/loglevel

The usage of this switch is as follows:

/loglevel=[1-255]

/setupApiLogLevel

The usage of this switch is as follows:

/setupApiLogLevel=<logLevel>

/ExportDevicesIntoFile

The usage of this switch is as follows:

/ExportDevicesIntoFile=<path>

If Path is empty, then device_file.xml that contains information about the devices to perform DeployAnywhere operation, is generated in the current working directory.