Deploying a Cloudhouse Compatibility Container

04/02/2020 Cliff Hobbs   ID: 267076

Deploying a Cloudhouse Compatibility Container

Cloudhouse.Container.Deployment.exe (also known as the Cloudhouse Deployment Tool) is used to deploy a Cloudhouse Compatibility Container from the file share/local folder containing the executable, to the specified server or desktop.

Use the following command to deploy a Cloudhouse Compatibility Container:

<path_to_container>\Cloudhouse.Container.Deployment.exe /acceptEULA /deploydir "<target_path>\" /deploytype [machine | user] /usagelocation \\<path_to_reporting_token>

where:

  • <path_to_container> is the path to the folder containing the Cloudhouse.Container.Deployment.exe executable. If no path is specified, it is assumed the Deployment Tool is in the current folder.
  • /acceptEULA indicates your acceptance of the Cloudhouse EULA (only required the first time you deploy a Compatibility Container).
  • /deploydir "<target_path>\" is the path to the folder the Compatibility Container is to be deployed to. If this is not specified, the Container will be deployed to its current location, which can be on a file share.

Note

Either the /deploydir or /shared (for a shared deployment) need to be specified.

  • /deploytype is the type of deployment which will either be machine or user.

Note

The /deploytype switch is optional for machine-based deployments but required for user-based deployments. Omitting this switch will result in the Compatibility Container being deployed to the machine.

  • /usagelocation \\<path_to_reporting_token> specifies the location of the Reporting Token, which can be a file share.

Note

The Deployment Tool can also be run using deployment tools such as Microsoft Endpoint Configuration Manager/SCCM.

Usage Reporting

Cloudhouse Compatibility Containers default to https usage reporting and will report an error if there is an invalid or missing Reporting Token. The Reporting Token is encrypted by the machine when the Compatibility Container is deployed. Compatibility Containers may report usage to file shares if the /usagelocation option is specified at deployment time.

Warning

If the /usagelocation switch is used, the location specified for this switch must already exist before the Compatibility Container is deployed. If the location specified does not already exist, the Deployment Tool will not create it.

Full details are available in Licensing and Reporting‍. 

Container Permissions

The Compatibility Container inherits any permission from the parent folder for the folder that is created. For example C:\ProgramFiles\<Container_ID>.

Deployment Options

Refer to the appropriate section for details on the different types of deployments and example usage.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support