Hello, We have just released update to Application Virtualization Explorer, version 2.4.5. This update adds explicit support for three new (OSD) policy elements that were introduced in hotfix 8 for 4.6 SP1 and in 4.6 SP2. These policy elements are mainly meant to fix issue with Adobe Reader protected mode and now you can set them directly from AVE’s […]

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.

One common mistake people tend to do when trying out the whole application package “side-by-side” functionality of App-V – i.e. running separate packages of the same application suite on a same machine – is to not be careful enough about how to name each individual application.

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.

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

There is a Compatiblity -tab in the Windows Explorer when you take the properties from a executable, which can then be used to set certain pre-defined compatibility mode settings for a program. It might not be so intuitive, however, to set those same settings for virtual applications as you probably have discovered when trying to set compatibility for applications running in App-V “bubble”. In this post, I will demonstrate how to utilize OSD scripting to do what you would normally do through Windows Explorer UI.

In the previous article of AVE’s scripting capabilities, we discovered how AVE implements the basic App-V scripting capabilities – but in much smarter manner and easiness lacking in any other App-V –related tool there is. In this installment, we will see how to take scripting a bit further, by adding additional execution capabilities for our […]

In this article, I want to give a brief lesson on something called OSD scripting. OSD scripting is a way to add dynamic or added functional behavior into App-V packages outside what the App-V itself as a virtualization technology provides.