When App-V 5 was initially released there was new method introduced for automatically “sucking” any locally installed application into context of virtual package, RunVirtual client registry key. This method was then improved in App-V 5.0 SP3 to support user published packages in addition to global ones. One thing, however, that is difficult with this method is the fact it has to be written to client’s registry and thus is not easily manageable.

Fortunately, there seems to be workaround that works well: for both logically tying the RunVirtual entry to the CG rather than some specific package, as well as making sure that we can upgrade App-V 5 packages without constantly going back to all clients making modifications to the HKLM branch of the registry.

One of the support cases that we have had, since the release of Application Virtualization Explorer version 3.0 that started supporting App-V 5.0 packages, is how to run AVE itself inside 5.0 package. Sounds simple enough, doesn’t it: just add the files into .APPV file and go, right? Well, not so in this case…

For a long time already, Application Virtualization Explorer (AVE) has had the ability to set and edit virtualized environment variables per application basis (like you could do in the Sequencer by using that cumbersome OSD -tab), but in the recently released 2.4.0 version we decided to add support for editing variables at the package level too.

Recently I was involved with the customer who uses, amongst the traditional App-V Management Server –based RTSP publishing, a HTTP publishing script that was posted in the App-V Team’s blog mid-2010. This script constructs necessary APPLIST information out of manifest XML files detected on a virtual directory, but unfortunately it has some shortcomings which I decided to fix and present an enhanced version here as a replacement.

Back in the last November, Sebastian Gernert who works as a Microsoft’s Support Escalation Engineer wrote an article about fixing Volume Shadow Copy –related issue with the App-V Client in the German App-V blog (browse the site with Chrome and you get handy translation prompt if you don’t read German).

In this new series, we’re going to highlight some of the new features that we introduced in Application Virtualization Explorer (AVE), version 2.3, released in December last year (gosh, sounds like a long time ago when said like that!).

In a recent post over at the Microsoft’s Technet App-V forums, original poster had the issue during Star Office 8 sequencing wherein middle of the process Windows would just pop up a error message that INF file could not be installed correctly. Let’s find out how to track the source for such an error.