With the introduction of RunVirtual as an official feature in App-V 5 SP3, the ability to use it for user targeted packages, and the ability of SP3 to set connection group members as optional, I started wondering whether it would be possible to create a connection group for all your IE (or Office) plugins and automatically launch IE (or any Office Application) inside the connectiongroup by using the RunVirtual Registry key, and still start IE (or any Office application) in a specific Virtual Environment by using the /AppVVE: command line hook switch. What I’m thinking of is a default connection group to start IE in for all standard (non conflicting) IE-plugins and separate packages for a specific Java versions. Similar with Office, one connection group for all standard (non conflicting) Office-plugins and separate packages for special plugins (plugins with conflicting versions, conflicting settings, etc.).
Will this work? What happens when an application is started and set to launch in two different Virtual Environments by a conflict between RunVirtual and the AppVVE parameter? Read More…
Hotfix 4 is actually more than just a hotfix. It is quite a major update. Most importantly it fixes the following:
- Hotfix 4 finally solved the issue with having to grant the local system access to a network share from which you wanted to launch an executable inside an App-V 5 environment. The workarounds described in my earlier post(s) are no longer required.
- It also finally allows us to write inside the Virtual Environment again, although with some limitations tot the types of files that can be written.
- We can now again save packages as new packages, like we were used to in App-V 4.6. This makes it much easier to create a (slight) variation of the same package.
- Performance issues have been addressed.
More Information and the rest of the fixes in HF4 can be found here.
Hotfix 5 adds the ability to create user based connection groups that contain both user published applications as well as globally published applications. This allows you to for instance publish Office globally and Office Add-ins on a per user basis.
This feature is however not supported in a full infrastructure scenario as there is no fix for the server available (yet) to enable this feature. But it should work with SCCM managed connection groups, although I haven’t been able to test it yet.
More Information and the rest of the fixes in HF5 can be found here.
Recently I had to sequence Autodesk TrueView 2014 using App-V 5 Sp1. At first this seemed pretty straightforward as I found some recipies on the Internet. But these all turned out to be incomplete or for App-V 4.6. I found that for the best result I had to move (at least the client) to SP2. So here’s my recipe for sequecing Autodesk TrueView 2014.
I’ve been using vbScript for a long time to write (simple) tools to make life a little easier. Because I’m so at home with vbScript I’ve put off using Powershell for al long time, but since App-V 5.0 uses Powershell extensively there’s no escaping it any more. I have to learn Powershell.
Lately I’ve been busy with running external executables inside an App-V 5 virtual environment (see my previous posts). Doing this requires you to find the packageID en VersionID of an App-V package and type a very long command line. So to set myself al least a bit of a challenge I decided to create my first Powershell script tool to make this a little easier. Read More…
We know that it is possible to launch a external (non virtualized) executable inside a App-V 5 virtual environment by using the /appvve parameter and supplying the PackageID and VersionID of the sequence that you want to launch the executable into.
So what happens if the sequence that you want to launch the executable into is part of a Connection Group? Will the launched executable have access to the complete virtual environment of the connection group? Well the answer is a simple “Yes”.
So I started to wonder if is it possible to connect directly to the Connection Group instead of to a sequence that is part of the Connection Group. Read More…
Microsoft has just released App-V 5.0 SP1.
This service pack contains the following changes:
- The App-V 5.0 sequencer and App-V 5.0 client now support twenty-four languages. You can download the additional language packs using the Volume Licensing Service Center.
- The App-V 5.0 server now supports eleven languages. You can download the additional language packs using the Volume Licensing Service Center.
- Support has been added for the App-V 5.0 Volume Shadow Copy Service (VSS) Writer feature.
Also support for sequencing Microsoft Office 2010 has now been added. The Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0 and the Microsoft Office 2010 Deployment Kit for App-V are required for this.
More information can be found here:
Consider these scenario’s
1. You have an application that has its main executable located on a network share but it also requires files installed on the local computer. You want to use App-V 5 to create a virtual package/sequence of the locally installed files and launch the network executable while making use of the created sequence.
2. You already have an App-V 5 sequence of an application and want to run another executable located on a network share while making use of this sequence.
This post has been revised. Please See Launching a network executable inside an App-V 5 virtual environment (Revised)