CSM 10.4 Documentation

Home

Auto-Deploy Command-Line Options

Use the Command-Line Configuration (CLC) /autodeploy and autodeployfromsettings major commands to create an Auto-Deploy package that automatically distributes preconfigured Desktop Client and CSM Administrator installations and connections.

Arguments passed through the /autodeploy are saved to the C:\ProgramData\Trebuchet\trebuchet.settings file. You can then use /autodeployfromsettings to create the Auto-Deploy package from those settings.

Note: In the following examples, square brackets (example: [Common]) denote placeholder variables for customer data. Replace these variables, including the brackets, with your own values.

/autodeploy

Example with minimally required commands:

                                Trebuchet.CommandLineConfigure.exe /autodeploy /adconnectionname="[Common]3TierConnectionName" /adtargetfolder="C:\Program Files\Cherwell Browser Applications\CherwellAutoDeploy" /adsite="https://YourAutoDeploymentSite/CherwellAutoDeploy/" 
      
                            

Example with installation options:

                                Trebuchet.CommandLineConfigure.exe /autodeploy /adoverwrite=True /admakedefault=True /adnoprompt=True /adminorrelease=False /ReqMinorReleases=False /adtargetfolder="C:\Program Files\Cherwell Browser Applications\CherwellAutoDeploy" /adsite=https://YourAutoDeploymentSite/CherwellAutoDeploy/ /adnouseroptions=False /adinstalloptions=UserChoice /adinstallaccounts=[{\"Domain\":\"cherwell\",\"Username\":\"john\",\"Password\":\"12345},{\"Domain\":\"cherwell\",\"Username\":\"john2\",\"Password\":\"12345\"}]
                            
Sub-command Description

/adconnectionname

The Client connection that is pushed out to all clients during installation. This must be an Application Server connection (3-tier connection).

Accepted values: string

Required: Yes

/adtargetfolder

The directory on the server where the install files are stored. This should be the directory where Auto-Deploy is installed (the physical directory that is pointed to by the Auto-Deploy site). If defaults were selected during the installation, this should be ..\Cherwell Browser Applications\Cherwell Auto-Deploy.

Accepted values: string

Required: Yes

/adsite

The URL of the website housing the Auto-Deploy installation. If the defaults are selected during the installation, the URL is https://YourAutoDeploymentSite/CherwellAutoDeploy.

Accepted values: string

Required: Yes

/admsifilepath

The full path to the CSM installer .msi file. The system will attempt to locate the file, but if it has been moved from its default location (\ProgramData\cherwell service management), you must provide the location.

Accepted values: string

/admakedefault

If true, uses the installation connection as the default Auto-Deploy connection for users.

Accepted values: {true | false}

Default: True

/adnoprompt

If true, automatically connects to the installation connection without prompting users.

Accepted values: {true | false}

Default: False

/adminnorelease

If true, users are required to install minor releases even if the current version is compatible with the CSM server.

Accepted values: {true | false}

Default: False

/addebug

If true, a series of message boxes is shown during deployment to assist with troubleshooting.

Accepted values: {true | false}

Default: False

/adoverwrite

If true, the installer will overwrite existing connections with the same name.

Accepted values: {true | false}

Default: True

/adnouseroptions

If true, users are not prompted with options during installation.

Accepted values: {true | false}

Default: True

/adinstalloptions

Indicates the type of installation created. If /adnouseroptions is true, then either ClientOnly, or Complete must be selected.

Accepted Values: {ClientOnly | Complete | UserChoice}

Default: UserChoice

/adinstallallusers

If true, all users can run the installation. If false, then installation accounts must be defined.

Accepted values: {true | false}

Default: True

/adinstallaccounts

If set, the installer runs as one of the specified administrative users that matches the domain on the target machine (or does not specify domain) rather than as the current user.

Accepted values: JSON string. Example:
[{\"Domain\":\"cherwell\",\"Username\":\"john\",\"Password\":\"12345},{\"Domain\":\"cherwell\",\"Username\":\"john2\",\"Password\":\"12345\"}]

Default: Installation accounts not used.


Was this article useful?