Life After APP-V Server: Exploring Options for Application Streaming and Delivery

The discontinuation of Microsoft’s APP-V Server has left many enterprises seeking new methods to manage application streaming and delivery. As organisations adapt to an ever-evolving technological landscape, the need for efficient, scalable, and secure application delivery solutions is paramount. This article delves into the life after APP-V Server and explores the various alternatives available for application streaming and delivery. 

The End of an Era: APP-V Server 

Microsoft Application Virtualization (APP-V) Server was a popular tool that provided a flexible and efficient way to deliver applications to end-users without installing them on individual machines. By streaming applications on demand, APP-V helped reduce system conflicts and improve application management. However, with Microsoft ending support for APP-V server in April 2026 organisations will , if not already doing so , have to pivot to alternative solutions. 

 

All Is not lost however! There are alternatives to APP-V full Infrastructure available including several from Microsoft. 

Modern Solutions for Application Streaming and Delivery

 

1. Microsoft Endpoint Manager - Microsoft 

Microsoft Endpoint Manager (MEM) is a comprehensive solution that combines Configuration Manager and Intune to deliver and manage applications across devices. MEM enables traditional and modern management approaches, allowing organisations to deploy applications via the cloud seamlessly. It offers robust security features, simplified application updates, and enhanced user experiences. You may wonder how we deliver an APP-V application via Intune. 

You can use PSADT (PSAppDeployToolkit) as a wrapper around App-V sources. In the wrapper run the following the commands: 

 

Install 

Add-AppvClientPackage "$dirFiles\$appPackageName.appv" 

$UserSID = (Get-LoggedOnUser).SID 
Publish-AppvClientPackage -Name $appPackageName -UserSID $UserSID 

Get-AppvClientPackage -Name $appPackageName | Mount-AppvClientPackage 

  

UnInstall 

$ReturnCode = Execute-ProcessAsUser -Path "$PSHOME\powershell.exe" -Parameters "-WindowStyle Hidden -Command & { & `"Get-AppvClientPackage -Name $appPackageName | Stop-AppvClientPackage | UnPublish-AppvClientPackage`"; Exit `$LastExitCode }" -Wait -PassThru 
Get-AppvClientPackage -Name $appPackageName | Remove-AppvClientPackage 

 From that package create a .intunewin file,  upload to Intune and deploy. 

You will need Microsoft-Win32-Content-Prep-Tool

 

2. MECM (Microsoft Endpoint Configuration Manager formerly SCCM) 

When you use SCCM to manage virtual applications, you gain several benefits, such as a single management infrastructure, scalability, deployment, and content distribution features 

To deploy virtual applications to computers, you need to have both the Configuration Manager client and the App-V Client installed on your computers. The Configuration Manager client manages the delivery of virtual application packages to the App-V Client, which then runs the virtual application on the client 

Here are some key points about deploying App-V applications with SCCM: 

• Creating Virtual Applications: You must first create the virtual application using the App-V Application Virtualization Sequencer. The sequencer monitors the installation and setup process for an application and records the information needed for the application to run in a virtual environment 

• Deployment Methods: SCCM supports two methods for delivering virtual applications to clients: streaming delivery and local delivery (download and execute). Streaming delivery is beneficial for applications that require frequent updates or patches, as it reduces disk space requirements on the client. Local delivery ensures that the application is always available, even if the client is offline 

• Configuration: You need to configure the SCCM environment to deploy virtual applications via App-V. This involves setting up the Configuration Manager Console and ensuring that the necessary client agents and settings are in place 

Microsoft Endpoint Configuration Manager (MECM) and Microsoft Intune are both parts of the Microsoft Endpoint Manager suite, but they serve different purposes and have distinct features: 

 MECM (Microsoft Endpoint Configuration Manager) 

• On-Premises Solution: MECM is primarily an on-premises tool used for managing a wide range of devices within an organization’s network. 

• Comprehensive Management: It offers extensive capabilities for managing devices, applications, and security policies. 

• Legacy Systems: MECM is well-suited for managing traditional desktop environments and legacy systems. 

• Complex Deployments: It supports complex deployment scenarios, including operating system deployment, software updates, and configuration management. 

Intune 

• Cloud-Based Solution: Intune is a cloud-based service focused on modern device management. 

• Mobile Device Management (MDM): It excels in managing mobile devices, including smartphones and tablets, across various platforms like iOS and Android. 

• Simplified Management: Intune provides simplified application management, policy deployment, and endpoint security. 

• Integration: It integrates seamlessly with other Microsoft services, such as Azure Active Directory and Microsoft Defender for Endpoint, to enhance security and compliance 

• In summary, MECM is ideal for on-premises, comprehensive management of traditional IT environments, while Intune is designed for modern, cloud-based management of mobile and remote devices. 

• Both tools can be used together for a hybrid approach, leveraging the strengths of each. 

Endpoint management services and solutions at Microsoft | Microsoft Learn 

 

3. App Attach for APP-V 

If you are about to embark into the Cloud or you are already there then why not consider using the App Attach Blade to stage your APP-V applications? Its simple , fast and efficient with no DC or SQL server needed.  

App attach and MSIX app attach - Azure Virtual Desktop | Microsoft Learn 

Watch a demo presentation here: MSIX and app attach made easy - YouTube 

 

4. APP-V Management, Publishing and Reporting server Communal Project  

If you followed our event at MAD day in Hamburg in November 2024, you would have seen a superb demo of a 3rd party APP-V Management , Publishing and reporting Server by one of our Microsoft Partner, Andreas Nick of Nick IT  

In Andreas’ own words: 

Since App-V Publishing Server has been discontinued for 2026, we have started to create a replacement based on DotNet Core and a Maria DB (on each server). The server is functional and compatible in its current form. Kerberos is supported and theoretically it is possible to install it in a Docker container under Linux. We will show a short demo of publishing and App-V reporting. 

For a Demo, please take a look here: https://youtu.be/RfTWy_NMlyY 

 

5. AppVentix - Deployment & Application Lifecycle Management for App-V and MSIX 

AppVentiX is a management and deployment solution for App-V, MSIX (app attach) and FSlogix app masking. It simplifies the process of deploying and updating Microsoft application packages in various environments. AppVentiX also allows users to manage App-V and MSIX simultaneously and facilitates the transition from App-V to MSIX. 

AppVentiX supports the management of App-V and MSIX (app attach) on both virtual machines and physical machines, whether they operate in the cloud or on-premises. It is compatible with Server OS, Multi-session OS, and Single-session OS. 

https://appventix.com/  

Their demo at MAD day : MAD DAY 2024 Deploy applications in real-time with AppVentiX - -Bram Wolfs and Ingmar Verheij 

 

6. CloudFish Deployment Management for App-V and MSIX 

Cloudfish Deploy is a solution providing real-time application lifecycle management for multiple packaging technologies including MSI, MSIX (including App Attach), App-V, ThinApp and even PowerShell scripting. Their simplified and centralised application management interface provides real-time software deployments for physical and virtual desktop environments, both persistent and non-persistent.  

The Cloudfish Deploy solution simply consists of three portable executables – the management console, the agent, and the client. No backend required. 

https://www.cloudfish.co.uk/  

 

When selecting a new application streaming and delivery solution, organisations should consider several factors to ensure they choose the best fit for their needs: 

• Compatibility: Ensure the solution supports the operating systems and applications used within the organization. 

• Scalability: Choose a solution that can grow with the organization and handle increasing workloads. 

• Security: Opt for a solution with robust security features to protect sensitive data and ensure compliance with regulations. 

• User Experience: Consider the ease of use and overall experience for end-users, as this can impact productivity and satisfaction. 

• Cost: Evaluate the total cost of ownership, including initial setup, maintenance, and ongoing support fees. 

Best Practices for a Smooth Transition 

Transitioning from APP-V to a new application delivery solution can be challenging. Here are some best practices to ensure a smooth and successful migration: 

1. Assess Current Infrastructure

Conduct a thorough assessment of the current infrastructure to identify dependencies, compatibility issues, and potential challenges. This assessment will help in planning and executing the migration more effectively. 

2. Plan and Test

Develop a detailed migration plan that outlines the steps, timelines, and resources required. Testing the new solution in a controlled environment before full deployment is crucial to identify and address any issues early on. 

3. Train IT Staff and End-Users

Provide comprehensive training to IT staff and end-users on the new solution to ensure they are familiar with its features and functionalities. This training will help minimize disruptions and ensure a smooth transition. 

4. Monitor and Optimize

After deploying the new solution, continuously monitor its performance and gather feedback from end-users. Use this feedback to optimize the solution and address any issues promptly. 

 

Conclusion 

The discontinuation of APP-V Server has prompted and will continue to prompt organisations to seek modern alternatives for application streaming and delivery. By exploring solutions such as Microsoft Endpoint Manager (either MECM or Intune), App Attach for APP-V or using a 3rd party solution such as  AppVentix, CloudFish  organisations can find the best fit for their needs. Considering factors such as compatibility, scalability, security, user experience, and cost, and following best practices for a smooth transition, organisations can ensure continued efficiency and productivity in application delivery. 

Embracing these modern solutions will not only address the challenges posed by the end of APP-V Server but also pave the way for more advanced, flexible, and secure application management in the future. 

 

Philip McLoughlin

Support Escalation Engineer