Move all your applications and workloads to the cloud

Cloudhouse powers cloud migration, resolving compatibility problems that can stall the migration of applications and workloads reliant on legacy systems such as Windows Server 2003, 2008, 2008 R2 and Windows XP and 7.

It doesn’t matter what the application is – front office, back office, middle tier, legacy, COTS, in-house coded. We even handle applications that have no source media.

And it doesn’t matter whether you have a single cloud provider, deploying from a private cloud, or have a hybrid strategy, Cloudhouse Application Compatibility Packages will work on any, and all, of them. Package once and deploy anywhere.

Cloudhouse Application Compatibility Packages can also be deployed to AWS Workspaces and AppStream 2.0, as well as Microsoft’s Windows Virtual Desktop.

DAAS compatible

Run Application Compatibility Packages on both AWS Workspaces and AppStream 2.0, and Microsoft's Windows Virtual Desktop

Move with no code changes

Migrate legacy applications without needing to refactor, recode or upgrade

Fully cloud agnostic

Package once and deploy to any cloud provider. Future proof your applications for future moves.

How does Cloudhouse work?

Cloudhouse application compatibility packaging relies on three key principles:

1. Packaging on the operating system on which the application is supported

2. Runtime analysis to detect additional resources the application requires after install

3. The Redirection and Compatibility Engines (AAV) included in the resulting compatibility package.

The resulting container include all the application files, required runtimes, components, deployment tools, and the embedded redirection and compatibility engine the application requires to run on the target Operating System.

The Cloudhouse Auto Packager creates the compatibility package by packaging the application on the Operating System that is currently supported by the application, eg Windows 7. The redirection and compatibility engine, included in the Container, will run in user mode. As the Container is deployed to the target machine, the file type associations are registered, and short cuts created to enable the user to run the application.

The Auto Packager captures the resources the application’s installer/MSI reads from, and writes to, when it is installed on the operating system it is compatible with. At the end of the install capture process, the Auto Packager performs runtime analysis to capture additional application resources that are unknown at install time, for example changes to configuration files or components that are created at run time.

The Redirection and Compatibility Engine intercepts the Windows API calls as the application interacts with the local operating system. The redirected calls abstract the application’s files and registry, stored in the Container, from the local resources and the operating system.

NOTE: the Container does not include the legacy operating system, which means you are not running all, or part of Windows 7 on Windows 10.

This means that, regardless of what modern Windows returns from a system call, the application always gets the resources it expected on the Windows version it was packaged on (e.g. Windows XP). This lightweight approach means that the target application can “see” a combination of the redirected and local file system and registry with negligible performance impact on the application.

One service, one solution
> End-to-end, rapid scalable packaging service
> The complete solution for enterprises moving applications and workloads into the cloud
> Cloud-agnostic : package once for all major cloud providers
> Simple packaging process supported by auto-packaging toolset

Industry-leading technology
> Zero impact on end-user experience, applications work exactly as they did pre-migration
> Unique redirection and isolation engine makes the application behave as it did on its legacy platform
> No recoding or refactoring required
> Avoid expensive upgrades and associated change management

Easy to manage
> Applications are abstracted from Operating System, removing risk from Operating Systems updates
> Compatible with all third party management and reporting tools
> No remnant of the legacy Operating System is included, eradicating technical debt
 

AWS EMP

 

 

Cloudhouse is the Preferred Partner for the AWS End-of-Support Migration Programme (EMP) for Windows Server. Click here to find out more.

Some of our Customers

Latest News from Cloudhouse

Cloudhouse Technologies named as Preferred Partner powering AWS EMP

Cloudhouse has been selected as the EMP Preferred Partner, working with partners and customers to help drive server migration to AWS.

Migrate everything to Windows 10 on Microsoft Windows Virtual Desktop

Windows Virtual Desktop is a comprehensive desktop and app virtualisation service running in the cloud.

Cloudhouse featured on latest AWS Podcast

Cloudhouse has been picked out as the ideal solution for enterprise customers stuck with Windows 7, Server 2008 applications that they can’t migrate to AWS on the latest AWS podcast.

Contact Us

Platform