Opens in a new tab
WEBINAR
Streamlining Citrix Application Management
Request a Demo
post
Legacy Apps

Migrating Legacy Applications to Windows Server 2016

Rory Monaghan
Senior Technologist
In 2020 Microsoft will end support for Windows 7 and has already ended support for Windows XP and Server 2003. Many corporations have started work to migrate their work environments to Windows 10. As part of this effort, they are finding it is difficult to migrate many legacy applications required for business needs. This legacy software can vary from being too expensive to replace and/or deemed mission critical for the business. While some of the software may actually function on Windows 10 or Server 2016 systems, there is not a decent and proven method to move the software off from previous Windows environments.
An example of legacy software that cannot move was a customer that had a legacy version of SAP 4.7 requiringMicrosoft SQL Server 2000 with patches, which cannot be installed on Windows Server 2016. Additionally, SAP 4.7 uses a Windows MMC (Microsoft management console) plugin to control the server and this plugin is also not supported with the latest version of MMC available on Windows Server 2016. In order to retire Windows Server 2003, the customer would have no choice but to upgrade the SAP software to the latest version at a very high licensing cost; unless another solution could be found.

Solution

Cloudpaging contains advanced features that can templatize and abstract information from the Windows environment and provision an application using a file system driver that normalize the file content between Windows operating systems. This technology allowed Microsoft SQL Server 2000 to be packaged on Windows Server 2003 and delivered to Windows Server 2016. The legacy SAP 4.7 application was also packaged with MMC plugin on Windows Server 2003 and was set to run in the isolated virtual layer with SAP configured to run in the integrated virtual layer. By running isolated the MMC plugin, this layered disposition Cloudpaging container was able to load SAP’s MMC plugin without conflicts on Server 2016. This allowed the legacy SAP software to run on Windows Server 2016 without issues. Using Cloudpaging, customers can isolate conflicts between the legacy components and newer versions, and can successfully package legacy applications and deploy them to either Windows 10 or Windows Server 2016 without issues.
On this page
Share
Stay in the loop
Get the next Numecent post in your inbox — no more than twice a month.
Rory Monaghan
Senior Technologist
Rory has spent his career at the intersection of end-user computing, application delivery, and the Microsoft ecosystem — from packaging shops in Dublin to enterprise architecture in Silicon Valley. He writes about what actually breaks in the wild, and what to do about it.

Related reading

All posts
post
Jun 04, 2026

Why Application Packaging is Still a Challenge for IT

Application packaging has been part of enterprise IT for decades. Yet it remains one of…

Learn more
post
May 28, 2026

Deploy Legacy Apps to the Latest Citrix Desktops

For many years, Citrix customers have used Citrix Session Hosts as a solution for legacy…

Learn more
post
May 07, 2026

Stop Repackaging, Start Moving: Maximize Application Portability with Containerization

The dream of “write once, run anywhere” has been a long-standing goal in the world…

Learn more