What's new in Cloudhouse release 1702
Applies to: Auto Packager and Cloudhouse Containers
25/05/2019 Cliff Hobbs ID: 266758
Release 1702 is now available from Cloudhouse.
Cloudhouse Compatibility Containers™ are now available for Windows and Internet Explorer (IE) applications. These new Containers can be stored on-premise, deployed and run on servers and desktops using a customer’s existing management and deployment tools (such as SCCM, LANDESK, build scripts), without using Cloudhouse’s Applications Anywhere service in Azure.
The new Container format is created using the Auto Packager tool and same virtualisation and redirection engine you are familiar with. At the end of the packaging process, a link is provided to the Container’s folder on the local computer. The Auto Packager will update automatically the next time it is run, and the following features will be available.
Auto Packager 184.108.40.20632 (released 3rd Feb 2017)
- Auto Packager creates new Containers for Windows and IE applications.
Auto Packager 220.127.116.1108 (released 15th Feb 2017)
- Enable/disable diagnostic telemetry reporting from the Container improves the support and troubleshooting experience of Containers
- The “Done” page includes a link to the Container.
Auto Packager 18.104.22.16835 (released 24th Feb 2017)
- Product survey "Feedback" button for customers to rate the product, and provide feedback.
Containers 22.214.171.124 (released 28th Feb 2017)
- Individual unencrypted XML files for registry and file redirections, shortcuts, file type associations, programs and environment variables make it far easier to edit and maintain Containers.
- Command-line support for Machine (default) and User-based deployments.
- Added feature hints in the configuration files AppAcceleratorV.clc and Redirections.xml, simply uncommenting a feature enables it in the Container.
- Container uninstall for Machine and User deployments.
- Diagnostics telemetry reporting can be enabled/disabled in a Container, improving the support and troubleshooting experience of Containers.
- User deployments currently require Administrator privileges to complete the uninstall, SCCM or similar must run the uninstall action as Administrator. The following article explains How to manually uninstall a Container in the event of a failed uninstall.
- Cloudhouse recommends using the Auto Packager on x86 operating systems only. Re-directions will not be created correctly for applications that contain a mix of x64 and x86 components. Containers will be created successfully for applications that contain only x64 components, but successful packaging on this platform requires detailed knowledge of the application prior to packaging.
Features in Upcoming Releases
See Planned features for future Cloudhouse releases for details of the features we have planned for feature releases of our products.