After looking at the basics of Virtual File System (VFS) and how the data behaves in the client for VFS virtualized directories in the previous articles in the series, let’s finish up the discussion of VFS folders by looking at one specific – rather interesting – bug (because that’s what it must be) when it comes to fully virtualized folders and the whole concept of isolation.

In the previous article in the series, we discussed the different modes of Virtual File System (VFS) entries in a general level and exactly how application sees the files (and directories) stored in VFS –virtualized folders. This time over we are taking a little bit closer look at the client’s behavior when it comes creating new files or directories on these VFS-virtualized directories, as opposed to just reading in files that were carried over from the Sequencer.

I recently got the inquiry about the way AVE displays certain App-V variable, %SFT_ALLUSERS_DIR%. Since there’s more than meets the eye behind this variable, I thought to write up about it..

In this new “mini-series” I will take a close look into a Virtual Filesystem (VFS) feature found in App-V, and some of the things that I feel should be understood by everyone doing VFS sequences and especially when trying to troubleshoot them.