What's new in Cloudhouse release 1901

Applies to: AppAcceleratorV, Auto Packager, Cloudhouse Containers, Discovery Tool

27/03/2019 Cliff Hobbs

Overview

Release 1901 is now available from Cloudhouse.

This topic details the new features and fixes for the Cloudhouse Auto Packager, Editor, and Containers they create that have been released throughout January 2019.

Any components that have changed this month are version 4.5.1901.nnnn

AppAcceleratorV 

Fixes

AppAcceleratorV 4.5.1812.23048 (released 11th January 2019):

  • Issue resolved where a virtualised process could not create a child process when the path contains spaces and the entire path is not enclosed with quotes.

Auto Packager

New Features

Auto Packager 4.5.1901.23656 (released 11th January 2019):

  • Auto Packager can now capture:
    • Run commands configured for services.
    • The running state of a service.

Auto Packager 4.5.1901.23698 (released 31st January 2019):

  • Auto packager detects service users.

Fixes

Auto Packager 4.5.1901.23656 (released 11th January 2019):

  • Issue resolved where the recovery options for services for a Windows XP application were not captured during packaging.
  • Issue resolved when editing a package at the end of the packaging process results in duplicate entries in some files.

Cloudhouse Containers

New Features

4.5.1901.946 (released 11th January 2019):

  • Configurable service start on deployment.
  • Deploy services under unique virtual service accounts.

4.5.1901.992 (released 31st January 2019):

  • Cloudhouse.Container.Run.exe interprets the rest of the command line after the /FileArgs flag as the FileArgs value (it ignores any / or -- characters).
  • Can now deploy extra privileges for a virtual service account.

Fixes

4.5.1901.946  (released 11th January 2019):

  • Issue resolved where uninstalling a Container would fail with the error The system cannot move the file to a different disk drive. Only seen when uninstalling a container from a drive other than the C: drive.

4.5.1901.992 (released 31st January 2019):

  • Issue resolved where ComDeployment.xml validation fails saying File is not in the container despite the file existing in the Container.
  • Issue resolved where a user deployment was permitted on a computer that already had a machine deployment.
  • Issue resolved where an extra WOW6432Node key was inserted when deploying a 32-bit COM server on a 64-bit machine.

Discovery Tool

1.0.1901.51 (released 31st January 2019):

  • A new tool that discovers drivers

Advisories

Advisory 1

The Container Editor should only be used to update applications, file, and registry redirections on the same architecture the original Container was created on. For example, if the Container was created on an x86 machine, then the Container Editor must be run on an x86 machine to update the Container.

Anti-Virus Advisory

Remove any Runx.exe files (where “x” is a number), from the Container before deploying it. These files are only required if you need to create Universal Windows Platform (UWP)/MSIX packages of the Container. Anti-virus and malware scanners may flag these files as malware as they are unsigned and designed to run other executables.

Features in Upcoming Releases

See the Features in Upcoming Releases page for details of the features we have planned for feature releases of our products.

Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support