Primary-Client.exe Commands
The following describes the available commands for primary-client.exe:
Notes:
- Be sure to wrap all complex passwords like "&()[]{}^=;!'+,`~ my c0mpl3x PW" and paths that include a space in double quotes.
- Double quotes cannot be used in passwords or AES secrets.
/InstallerArgs(if any) must be quoted, be the last parameter, and inner quotes must be escaped with \- If
/Installerpoints to a .msi, then/InstallerArgswill automatically be set to/i "<installer.msi>" /qnand/Installerwill implicitly become msiexe.exe, but you can still use/InstallerArgsto provide additional args in this scenario. - If multiple paths are provided to network shares, multiple credentials are provided, and they are to the same server then either only use one set of credentials, or make the second reference to the server be via ip.
- If a PackagesFile contains a parameter already set in DefaultsJSON, PackagesFile wins. If parameter also included on CLI, CLI wins.
| Command | Description |
|---|---|
|
Help |
Displays the command line options |
|
Add PackagesFile |
Creates or appends to a PackageFile
...
|
|
List PackagesFile
|
List package information from an existing PackagesFile |
|
Remove PackagesFile |
Removes <package name> from an existing PackagesFile |
|
Clear PackagesFile |
Removes ALL entries from an existing packages file |
|
Create DefaultsJSON |
Creates optional DefaultsJSON with default params used by packaging jobs |
|
List DefaultsJSON |
List parameters from a DefaultsJSON file |
|
Create Packages |
Creates the packages listed on the CLI or in the specified file(s) |
|
Status Packages |
Retrieves the status of Create Packages batch jobs |
|
Wait Packages |
Waits for a currently running create packages batch job to complete |
|
Add Agent |
Adds a Capture Agent to the Primary Packaging Manager |
|
Remove Agent |
Removes a Capture Agent from the Primary Packaging Manager |
|
List Agent |
Lists all Capture Agents currently added to the Primary Packaging Manager |
|
Clear Agent |
Deletes ALL Capture Agents from the Primary Packaging Manager |
Footnotes:
* /Path –Specifies the folder where the packages will be created
-
Specifying a
* /Pathending in a FlexApp package's filename.vhdx will perform an extend of that existing package. -
Specifying a
* /PathUsernameof"IAM"will attempt to use the Agent machine's assigned IAM roles to access the S3 bucket. -
There are several ways to use
* /Path, depending on your target storage platform:-
/Path "<\\server\share\target-path>" [/PathUsername "<domain\user>" /PathPassword "<pass>"] -
/Path <s3://bucket/folder> /PathUsername <access key> /PathPassword <secret key> -
/Path <s3://bucket/folder> /PathUsername "IAM" -
/Path <az://bucket/folder> /PathUsername <account name> /PathPassword <account key> -
/Path <gs://bucket/folder> /PathPassword "<path\credential.json>"
-
** /Installer –Specifies what should be installed, or executed and captured
-
/Installer–Supports several file types beyond EXE's and depending on the file extension, are automatically called by the associated interpreter:-
MSI files will be automatically run via:
msiexec.exe /i /qn.
Additional Arguments can be passed in via/InstallerArgs. -
Batch scripts (bat,cmd) are run via:
cmd.exe /C “installerscript.bat” "</InstallerArgs>" -
Windows Script Host files (vbs,vbe,wsf,wsc,js) are run via:
cscript.exe /b /nologo “installerscript.vbs” "</InstallerArgs>" -
Powershell (ps1) are run via:
powershell.exe -ExecutionPolicy Bypass -NoProfile -WindowStyle Hidden -NonInteractive -File “installerscript.ps1” "</InstallerArgs>"
-
-
/Installer–Copies the specified file into the local temp folder before executing it unless/DontCopyInstallerLocalis specified.-
If the file specified is a script, then
/CopyInstallerFolderLocalwill be enabled so that supporting files are included. -
The "InstallerFolder" is the folder containing the specified
/Installerfile unless otherwise specified using/InstallerFolder. -
/InstallerFolderimplies/CopyInstallerFolderLocal.
-
-
/Installer–Supports local disk paths, CIFS shares and http(s) URLs.
