Updating Deployed Containers

Save to PDF

Applies to: Cloudhouse Compatibility Containers

29/11/2019 Cliff Hobbs   ID: 266745

To update the contents of a deployed application Container with a new version of the Container, run the Cloudhouse.Container.Deployment.exe command with the /update switch. The Container may include changes to:

  • Files
  • Registry settings
  • Shortcuts
  • Container configuration files
  • File type associations


Using the /deploytype switch without specifying a type will default to machine


Attempting to use the /deploydir switch when a Container has already been deployed will result in 'Failed to deploy' exit code -1. The /update switch must be used to update Containers to the latest version, or the /uninstall switch must be used first to remove the Container.


Cloudhouse.Container.Deployment.exe /update /deploytype [ machine / user ] 


With the release of Container version 4.5.1807.555, the /noprotect switch been removed from Cloudhouse.Container.Usage.exe as the token's file path location can now be specified on the command line. This allows the token to be stored on a secure file share for shared deployments. Contact Cloudhouse for more details.

Updating Containers

Application files, file associations, shortcuts, and registry can all be updated using the latest versions in a new source Container. The following describes how each component is updated.

File Associations

If the file type associations source file (FileAssociations.xml) in the new Container is the same as in the currently deployed Container, /update will recreate any missing file type associations and restore values or types to the original values and types specified during the initial deployment.


The /update switch will preserve any values that appear in the registry that are not specified in the source file.

If the file type associations source file (FileAssociations.xml) in the new Container is different from that in the currently deployed Container, /update will delete any registry values that do not appear in the FileAssociations.xml and will update any values and types that have changed. 


Any new shortcuts specified in Shortcuts.xml will be created. Any shortcuts that do not exist in the XML file will be removed. Any fields that differ between the currently deployed and the new version to be deployed will be updated to the latest version.


A registry update will be performed the next time the user runs the application, it does not happen as part of the update process. Updates are performed if the value of LastModified Date of Registry Added stored under HKCU\software\cloudhouse\appaccelerator\{appid} differs from the last modified date of the new application registry XML file (AppRegistry.xml).

The registry update will remove all keys under {appid} (but not the values of the key itself), and create all the entries specified in the AppRegistry.xml file. It will then set the last modified time to the time of the new AppRegistry.xml file.

Subsequent application start events will not trigger registry updates because the modified time of the file will match the value stored in the registry. If the last modified time cannot be found in the registry, the registry will be created using the latest AppRegistry.xml file. If the AppRegistry.xml file is invalid, /update will report an error and will not remove any app registry.

Updating Reporting Configuration

Update the Container to use HTTPS Reporting

The /update switch can be used to reconfigure a Container from reporting via a file share to using HTTPS, provided the Container's components have been upgraded to version 4.5.1807.555 or later. The token location will default to inside the Container i.e. the current location the deployment is being run from. The path to the reporting token needs only be specified if the token resides outside of the Container i.e. on a remote file share.


c:\<path_to_container>\Cloudhouse.Container.Deployment.exe /update /tokenlocation

Update the Container to use Fileshare Reporting

The /update switch can be used to reconfigure a Container from reporting via HTTPS to a file share, provided the Container's components have been upgraded to 4.5.1807.555 or later. 


c:\<path_to_container>\Cloudhouse.Container.Deployment.exe /update /usagelocation \\<path_to_unc_fileshare>
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support