Enterprises are modernizing Windows, shifting to Intune, and expanding VDI and Cloud PCs-but application delivery hasn’t kept up. Multiple control planes (ConfigMgr, Intune, Citrix/AVD, macOS) create duplicated packaging, inconsistent versions, and slow time-to-software. A Fortune 50 financial services company set out to simplify this with an overlay approach that unified delivery and self-service without a risky rip-and-replace.
In this VMblog Q&A, Ben Ward, Field CTO of Recast Software shares anonymized lessons from that adoption: what triggered the evaluation, the pain points they prioritized, how they piloted and handled change management and security reviews, and the outcomes that made the effort worthwhile. The takeaways apply to any large organization wrestling with hybrid estates, VDI, and user-centric app delivery.
++
VMblog: What kicked off the evaluation?
Ben Ward: A Fortune 50 financial institution had a home-grown app portal and fragmented delivery paths (SCCM/Intune/VDI). Their engineers wanted one modern front end for every app and delivery method, with automation underneath. Executive leadership later aligned on a vision to “modernize how apps are delivered company-wide,” which created the momentum to move forward.
VMblog: What were the biggest pain points before Application Workspace?
Ward: Slow/uneven delivery with native tools, high manual effort to package and patch third-party applications, tool sprawl across SCCM/Intune/third parties, weak reporting, and a clunky user experience that drove tickets instead of self-service. Hybrid/VDI added more complexity.
VMblog: What outcomes were they actually targeting?
Ward: A single cross-platform catalog, persona restore after Autopilot (so users are productive in 30 minutes), DTAP/ringed rollouts, a curated evergreen catalog that honors their customizations, multi-tenant readiness for M&A, and better reporting/license insights.
VMblog: Why Application Workspace instead of “just Intune/SCCM/Workspace ONE/Jamf”?
Ward: They needed faster, more reliable, context-aware delivery and packaging automation without inheriting native limitations. Application Workspace’s agent, unified packaging model, and self-service UX gave them control and speed, while still integrating with what they own.
VMblog: How does Application Workspace fit with what they already had?
Ward: Application Workspace extends Intune by Connecting with Windows Autopilot and Entra and bridging with ConfigMgr, Citrix/AVD, Microsoft Store, etc. It presents a single catalog and workflow to users and admins that lets them modernize without forcing a big-bang swap-out.
VMblog: What proved value during the pilot/POC?
Ward: They saw quick packaging (GUI vs. wrapper scripts), faster/more predictable installs via the Application Workspace agent, and a better end-user experience (rich catalog, approvals, reviews). Teams also saw that Smart Icons eliminated �wrong launch path’ errors-like off-VPN users hitting the wrong installer-by dynamically routing each user to the correct app delivery method at the right time.
VMblog: How did they approach scale (thousands of apps, multiple platforms)?
Ward: They leaned on Application Workspace’s curated Setup Store (thousands of Windows/macOS titles) plus their own packages for custom one-offs. Automatic updates preserved their customizations and eliminated repetitive rebuilds. DTAP pipelines/rings made large-scale promotion routine.
VMblog: What about VDI, published apps, and off-network users?
Ward: Smart Icons presented a single shortcut that evaluated context (device, network, identity) and launched the right path-local install, web, or virtual app (Citrix/AVD). That cut help desk loops and user error.
VMblog: What metrics moved the needle for leadership?
Ward: They saw reduced time-to-software and fewer “please install X” tickets via self-service, higher patch velocity/consistency, and time back for engineering by eliminating repetitive packaging.
VMblog: Did they change their imaging/provisioning approach?
Ward: Yes. “Shrink the image, move the logic.” Application Workspace enabled an agent-only image so the platform handled just-in-time apps/settings post-boot. One tested package promoted everywhere (laptops, Cloud PCs, and Citrix) without re-packaging.
VMblog: What friction points should others expect-and how can they de-risk them?
Ward:
- “Do we really need a new tool?” Arm champions with ROI/time-savings data and show side-by-side speed/reliability gains.
- Security/pen-test: engage security early, share architecture/data-flows, and plan buffer time for artifacts/reviews.
- Agent sprawl: show the small footprint and what it replaces (wrappers/scripts/portals), not just what it adds.
- Transition from SCCM/Intune: use parallel “stubs,” DTAP/rings, and embed where users already are.
VMblog: Was it worth the effort?
Ward: Yes. With one pane for Windows/macOS/VDI apps, context-aware launch, curated evergreen content, and automated DTAP, they simplified operations and improved user experience, while protecting prior investments. That combination (overlay + automation + UX) is hard to recreate natively.
VMblog: How would you summarize the value in one line?
Ward: “Deliver applications around your users-not your infrastructure.” One unified workspace, one experience, any device.
____________________________
Download the Executive Brief: Deliver Applications to Your Users, Not Your Infrastructure.
A concise guide for IT leaders on modern, user-centric app delivery-what to measure, how to de-risk change, and where an overlay model accelerates Intune/VDI projects.
Additionally, read more on our website.
