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.

Well, that didn’t take long. Only few days after Quest acquired Changebase, today Citrix has announced the same for App-DNA.

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.

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.

It so happened a while ago that I was on consulting day for a customer and we needed to make smallish update to an existing App-V package I originally did with Sequencer (because AVE does not currently have a monitoring functionality nor package creation from scratch). This update was only about adding a bunch of files to the sequence (some additional data/definition files for the application within) and as I did not had AVE installed on their packaging machine, I went with the usual Sequencer route. I soon discovered that I shouldn’t have done 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.

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 the earlier blog post, we have saw how App-V supports scripting for added package functionality and how it is configured by using the built-in tools (i.e. Sequencer) or manual methods; let’s now look at how our Application Virtualization Explorer (AVE) can make the process much easier for you regardless of the scenario.

Having been inspired by a recent blog posting by Tim Mangan about currently known issues in package branching (and my own previous experiences of the same), both in 4.6 and 4.6 SP1 versions of the App-V Sequencer, I thought about to write a quick and short howto for doing branching operating with our Application Virtualization Explorer (AVE).