Citrix: Debunking 5 Myths about Application Layering
As a Citrix SE and former Unidesk solution architect, I often worked conference booths giving demos and answering questions, so I got to talk to a lot of the IT people at a lot of IT shows. It is always interesting to hear what they’re being told by other layering vendors now that this idea of delivering apps as virtual disk containers is going mainstream, and others are offering their own layering solutions.
Some of the perceptions about layering were accurate. Many weren’t. Here are some of the things that the vendors are saying about layering in general that don’t apply to Citrix App Layering:
1. Layering technology can’t deal with apps that have early Windows dependencies like Dragon, Imprivata OneSign, antivirus, and agents like the Citrix VDA
Most layering solutions are based on architectures that run above the Windows OS and only do in-guest layering. Whether they attach apps at user logon or machine start, these solutions run too late to be compatible with apps that have deep Windows dependencies, boot-time drivers, system services, and pre-logon requirements. These vendors tell people, “layering technology cannot handle these types of apps. You have to put these apps in your base image.” Read VMware’s response in their App Volumes forum when one customer asked about layering Imprivata OneSign to see what I mean.
That is not the case with Citrix App Layering. We have the only “full-stack” layering technology that can manage and deliver the entire Windows workspace as modular virtual disks, including the Windows operating system itself. This unique architectural approach enables us to offer 2 kinds of layering that are compatible with all apps.
Read the entire article here, Debunking 5 Myths about Application Layering
via the fine folks at Citrix Systems, Inc.