Hi CraigDK
Thanks for sharing your insights on the challenges with app delivery using ConfigMgr, especially in light of App-V’s EOL and the limitations with MSIX. I completely understand the pain points for both persistent and non-persistent VDI environments in on-prem setups.
This is exactly where App Volumes can provide significant value. Using App Volumes with App Attach, you can:
- Leverage ConfigMgr for Triggering Delivery: App Volumes supports App Attach by delivering VHDs directly to endpoints. While ConfigMgr handles the distribution of these VHDs, the App Volumes agent virtualizes the application instantly on the endpoint, bypassing the need for a lengthy download and installation process. This is particularly useful for persistent VDI, where the applications need to stay agile and easily managed.
- Streamlined App Management: App Volumes eliminates the need for traditional installation, enabling fast app delivery that exceeds App-V’s performance. It’s well-suited for both persistent and non-persistent environments, ensuring users have their apps available immediately without unnecessary overhead.
- Integration and Flexibility: While ConfigMgr doesn’t natively support App Attach today, you can use ConfigMgr to manage and deploy VHDs, with our App Volumes and App Attach integration handling the last-mile for quick delivery and virtualization. This bridges the gap between ConfigMgr’s capabilities and the agility of modern attach methods.
If you’re interested in exploring this approach further or need help with specific configurations, feel free to reach out to me directly. I’d be happy to provide more details or even schedule a deeper discussion to show how this can fit into your environment.