The deployment tool, Cloudhouse.Container.Deployment.exe deploys the Container from a file share, or local directory, that the executable resides on 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 and if not specified the Container will run from its current location which can be 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.Container.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.
Containers will default to https usage reporting, and will report an error if there is an invalid, or missing token. Containers may report usage to fileshares, if the /usagelocation option is specified at deployment time. Note The usagelocation must exist at deployment time, the deployment tool will not create the specified path on the UNC share.
The reporting token is encrypted by the machine when the Container is deployed, unless /noprotect is specified. Currently /noprotect is required when you deploy into a Gold Image, or using the deployment type Shared Deployments - Running Containers From File Shares (Deploy without Container Copy).
Full details are available in Licensing & Reporting.
The Container inherits any permission from the parent folder for the folder that is created, C:\ProgramFiles\<ContainerID>.
Refer to appropriate section for details on the different types of deployments, and example usage.