Alchemy Compatibility Package Deployment Command-Line Options

Save to PDF

Applies to: Alchemy

12/04/2024 Brian Saladino   ID: 1355578

Cloudhouse Alchemy Compatability Packages are deployed using the Cloudhouse.Container.Deployment.exe executable. The following table outlines which command-line options are supported:

Delete

Note

Command-line options are case insensitive and can be prefixed with either two slashes ("--") or a single backslash ("/").

For example --deploydir and /deploydir are both valid and will achieve the same result.

Argument Short Alias Specifies
AcceptEula a Accepts the End User Licensing Agreement (EULA). This agreement must be accepted in order to use Alchemy and the Compatibility Packages it creates.
You can find the EULA in the root of each Compatibility Package in the eula.html file.
DeployAlias N/A Specifies an alias for the deployment. The deployment executable only supports the Server alias, which sets:
  • RootHive to HKEY_LOCAL_MACHINE.
  • DeployType to Machine.
  • WriteRegistryOnDeploy to true.
Deploydir d Specifies the deployment directory. 

Note: This folder must already exist on the target computer, and if the path contains a space, this argument must be surrounded by quotes. For example:
/deploydir "C:\Program Files (x86)"
DeployType t Specifies the deployment type. Valid deployment types are either "User" or "Machine". If a deployment type is not specified, the Compatibility Package is deployed to the Machine.
Dryrun r Used in combination with update to simulate the update without making any changes to the system.
This saves any changes that will be made to the system in a report called "package-diff.json" in the source packaging. This lets you verify the performance of any updates before fully deploying them. For more information, see more on Performing a simulated update (dry run)‍.
Force f Forces the deployment, even if it fails.
Help h Displays help and this list of options.
Licensing l Used in combination with update to perform the update against the licensing component only. No other components are updated if this argument is used.
This saves any changes that will be made to the system in a report called "package-diff.json" in the source package and updates all run tokens in all the required run token stores.
RootHive h Specifies the hive where registry keys in AppRegistry.xml and ComRegistry.xml will be written. This also specifies where the redirections in Redirections.xml will redirect to.
Supported values are either "User" for the HKEY_CURRENT_USER hive or "Machine" for the HKEY_LOCAL_MACHINE hive.
If this argument is not specified, the default will be “User”.
Shared s A shared deployment.
TokenFileLocation
(DEPRECATED)
k Specifies the name and path of the Usage Token for Usage Reporting.
If the path contains a space, this argument must be surrounded by quotes. For example:
/tokenfilelocation "C:\Program Files (x86)\usage-testcontainer.token"
Uninstall u Uninstalls the Compatibility Package.
Update p Updates the Compatibility Package.
WriteRegistry w Writes the registry entries in AppRegistry.xml and ComRegistryKeys.xml at deployment time instead of at run time.
Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support