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…

As some of you may remember, we used to have a product called Virtualization Encoder available a few years back. The idea of that product was running scripted – or template-based – automated operations against App-V packages, without user intervention. Now, that feature is sort of back in AVE!

We have just released a new version of Application Virtualization Explorer (AVE) which adds couple of oft-requested features, as well as improves the experience overall!

Yes, it’s finally here.

We have been busy in work updating our AVE product to be App-V 5.0 compatible, and as you can probably guess, this has not been a trivial task. In anticipation of launching “next generation” version of AVE that supports App-V 5 packages, I would like to open up a call for those interested in beta-testing the upcoming product.

After looking around MSDN subscriber downloads for App-V downloads, I noticed that something new had been posted there just yesterday… and it looks like App-V 5.0 RTM is out now (as part of MDOP 2012 package)!

Windows Team blog has just announced, for the first time publicly, development and the details of App-V 5.0. Along with the new App-V version. Along with the next App-V version, the blog post also announced Microsoft’s User Environment Virtualization (UE-V) product (which was previously known with codename “Park City”).