Amazon Web Services (AWS) have launched the End-of-Support Migration Program for Windows server (EMP) to give AWS customers a migration path to AWS EC2 for applications dependent on Windows Server 2008 and 2008 R2 that have reached End-of-Support.
Cloudhouse has been selected as the EMP Preferred Partner, working with partners and customers to help drive server migration to AWS.
What is EMP?
From January 14, 2020, Microsoft Windows Server 2008 and Windows Server 2008 R2 have reached End-of-support.
So that AWS enterprise customers have a migration path to EC2 for applications dependent on End-of-Support platforms, AWS have launched the End-of-Support Migration Program for Windows Servers, or EMP.
EMP leverages specialist application compatibility packaging technology which isolates the application from the underlying Operating System, enabling the migration of applications to a newer, supported version of Windows Server on AWS.
EMP will help partners attract End-of-Life Windows Server migrations to AWS.
While any licensing associated with EMP is included in EC2 subscriptions, partners delivering AWS migration projects will need to incorporate application compatibility packaging into their delivery programmes and services.
How does AWS EMP work?
Cloudhouse brings a decade of experience migrating incompatible applications, a deep knowledge of the application compatibility solution underpinning AWS EMP, and an application compatibility packaging service that can scale up to deliver rapid packaging services to AWS customers and partners.
What is Application Compatibility Packaging?
To make an incompatible application function on the modern AWS EC2 platform, it needs to be taken through a process called Application Compatibility Packaging.
The process itself is very similar to the traditional application packaging process most often used to support desktop transformations but the output is an EMP Application Compatibility Package, configured to enable the application to deploy into AWS EC2 without the need to refactor, recode or upgrade the application.
The resulting Application Compatibility Package includes the resources necessary for the application to run on the newer version of Windows Server as well as all the application files, runtimes, components, and deployment tools, and has an engine that redirects the API calls from your application to files within the package.
This resolves any dependencies, and decouples the application from the underlying OS. The packaged application can now run on future versions of Windows Server, which means it’s not necessary to upgrade them when the next end of support event for Windows Server arrives.
How do I take advantage of EMP?
Contact us here or direct to email@example.com to find out more.
FREQUENTLY ASKED QUESTIONS
Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.
Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.
Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.
Contact us here with your requirements and we will provide you with a quote.
Packaging and Maintaining Applications
Cloudhouse provide the Professional Services to package applications.
Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.
Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.
Cloudhouse recommends the same team who manage the operations of native apps.
Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.
The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.
Full documentation is made available to Cloudhouse partners and customers as required.
Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.