Citrix: The Magic of App Layering: Understanding File System Layering & Layer Priority
Often, when first introduced to the Citrix App Layering technology, admins will call it “magic”. This response is both flattering and somewhat undeserved! Magic has often been used to describe events or processes that the viewer could not explain. But App Layering is not magic; it’s some creative, innovative thinking that is easy to understand once you break it down.
In this post, we will look at the basics of file system layering, conflict resolution/file system merger along with the concept of layer priority and what happens when Layered Images and Elastic Layers (hot add) are combined.
Let’s start with a couple of basic statements, so we are all on the same page.
C: is really a virtual thing. Whether you are running a physical laptop, server or virtual machine, C: is just a logical assignment to whatever “drive” Windows can see. It contains a hierarchy of folders and files (in specific locations) to enable Windows to boot, services and applications to run, and users to interact with them.
To layer a C: drive is really to create a logical C: drive from a series of Layers each with their own file system and set of file system objects.
A Layer is simply a container for the file system objects and registry entries unique to that layer. In an Application Layer, this is just the files and registry entries that have been added, changed or even removed during the application install.
Read the entire article here, The Magic of App Layering: Understanding File System Layering & Layer Priority
Via the fine folks at Citrix Systems, Inc.