Deploying Containers

Deploying Containers

The command, Cloudhouse.Container.Deployment.exe deploys the Container from a file share, or local directory, that the executable resides in to the server or desktop the command is executed from. The deployment tool can be used from electronic deployment  systems, like SCCM.  The Container will be deployed to the folder specified on the command  line, this is optional because the Container can be run for its current location on a file share. If the specified deployment folder already exists, and a Container is present then the contents of the Container will be overwritten.


c:\> %path to container%\Cloudhouse.Containers.Deployment.Exe /acceptEULA /deploydir "c:\path name\"  /deploytype [machine | user ] [/usagelocation \\path\to\reporting]

If the deploytype is not specified, then the deployment tool will default to machine deployment.

Container Permissions

The Container inherits any permission from the parent folder for the folder that is created, C:\ProgramFiles\<ContainerID>.


Usage  reporting is recorded in the location specified by /usagelocation, and this should be a file share for machine based deployments. For user based deployments, it is recommended that a local file path within the user's profile is used so that roaming profile solutions can collect the data.  File shares can be used for user based deployments, however the path may  not always be available for laptop users who are working remotely.

The usage location must exist at deployment time, the deployment tool will not create the specified path on the UNC share.

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

Deployment Options

Was this article helpful?

Can't find what you're looking for?

Contact Support