My earlier how-to article about doing App-V package branching operation using AVE was otherwise correct, but if you are intending to use your branched packages in App-V’s traditional Management Server infrastructure, there’s couple of additional details you must attend to in order to be able to import your branched packages in.

So, in the last week there was a first (European) App-V User Group day, that was held in Microsoft NL’s offices at Schiphol / Amsterdam. Like almost a 100 others, I was there to attend the event and even though I did not have my own presentation, I got my share of publicity as well.

ExitVe, the utility for starting processes outside App-V virtual environment, from within that environment, is now available for downloading. You can find it from our community tools page at http://www.gridmetric.com/community/free.html.

Every now and then there might be a need to start processes outside the virtual “bubble”, from within the bubble; to effect changes to the real system or examine it without Virtual Environment (VE) being in a way. Since App-V does not natively offer such a capacity, I decided to write our own tool for doing just that: escaping the VE through a hatch!

We opened up a beta testing opportunity for upcoming Application Virtualization Explorer, version 2.3 a few weeks ago. At that post we also announced new features that were going to be in the product and that were already available in the beta as well.
While the new features mentioned will be getting a more detailed coverage in the upcoming weeks, I just wanted to write to tell about few new features which the beta does not support but will be in the actual 2.3 release.

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..

A new free tool to use instead of OSD file’s ABORTRESULT and SUCCESSRESULT attributes for controlling launch process. For 4.6 RTM an newer App-V Clients.

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.

In this final part of the series we take a look at something that we call application configuration scripts, which can be utilized for common tasks needed with virtual applications.