Kirx' Blog -

Use App-V 5 Beta Publishing and Management Server with a Remote Database

April 18, 2012

App-V 5 Beta allows to connect to a Database that is installed on a remote machine. However, it has shown that using a remote SQL Database is not that trivial. This article will highlight how to prepare the remote SQL Database to be used by App-V 5.

Reading through the documentation there is no hint that connecting an App-V 5 Publishing Server to an SQL database that is running on a different machine might be sort of ‘special’. Instead, it states something like “just enter the name of your Database Server’ and that’s it. Well, if you read some forum articles, posts and tweets it appears that this implementation does not exactly provide an ‘out-of-the-box’ experience. Let’s see…


Howto: Increase the Update Speed for Application Changes

April 16, 2012

So, you followed one of the posts orthe Admin Guide that have told you how to publish a new application with the App-V 5 Beta Management/Publishing Server(s) – but your Client doesn’t seem to refresh changes?

The potential reason for this is an interval that is defined on the Publishing Server feature. By default, it only refreshes its information every ten minutes. If this appears to slow for you, there is a simple switch to shorten that period…


HowTo install App-V 4.5 Management Server on Windows Server 8 Beta

April 15, 2012
1 Comment

A colleague of mine, Volker Kleiner (owner of , posted a German article on about how to install the App-V 4.5 Management Server onto Windows Server 8 Beta. Why… well, because it just doesn’t work out-of-the-box. During installation, you’d get an Error 25100 or Error 25122. For Windows 2008, a solution is described at MS KB2212140, but that doesn’t work on Win8: To prepare the machine, you need to “convert” it into a “GUI less” server instance and convert it back afterwards. This is the (loose) English translation of that article…


Posted in App-V, Management, Server
Tags: , , , ,

Bulk-update App-V Packages with a new Sequencer

January 26, 2012

Do you want to update all your old SoftGrid / App-V Packages to the newest Sequencer / Client version? Do you need to create Publishing MSIs for a bunch of packages because in the past you didn’t need them but want to use them now? Here is a simple Powershell Script that converts all existing packages within a folder structure recursively.


European App-V User Group Meeting: Nov 18th, Schiphol (The Netherlands)

September 21, 2011
Leave a Comment

After some German only events, I’m glad to announce the first Euopean App-V User Group Meeting on Nov. 18th in the Netherlands.

There will be about half of all world wide App-V MVPs on site (most of them even presenting), so this is probably a unique oppurtunity to meet with them and other community leader.

While the day is fully packed with awesome presentations, time is planned for questions and answers. And as Community events should be: it’s free!

You can register at

If you’d like to tweet about it: #AppVUG is the tag of choice.


Hope to see you there!





Posted in App-V

New: Free Login Consultant’s Application Virtualization Analyzer Tool

August 25, 2011

Do you want to get a comprehensive overview of all your App-V applications and packages, no matter if you use a Management Server, SCCM, another deployment solution or even manual deplyoments?

Do you want to verify quickly, if Naming Conflicts between virtual packages, 8+3 folders and other items occur?

Then, get Login Consultant’s “App-V Analyzer” to get all the infos usefully presented!


Posted in App-V, Tools
Tags: ,

ProcjectVRC Whitepaper: Impact of Application Virtualization on VDI Performance

June 17, 2011
Leave a Comment

It has been a question “ever since”:

What is the perfomance impact of Application Virtualization?

Now, Project Virtual Reality Check ( has released a Whitepaper that provides an idea of that. ProjectVRC compared Microsoft App-V, VMware ThinApp and Citrix XenApp Streaming running in Virtual Windows 7 machines.

While the impact is significant, there are some things to note…


Posted in App-V, Client
Tags: ,

App-V 4.6 SP1 – the right Sequencing Wizard

June 1, 2011
1 Comment

The new App-V Sequencer 4.6 SP1 introduces – besides new features – a set of new wizards. While in the „old“ Sequencers, basically there were three different
wizards (New; Open; Open for Upgrade), there are 7 wizards available within 4.6 SP1. To increase confusion, most of these wizards contain choices that influence the Sequencing process. Depending on those process choices, some wizard steps will be skipped.

After working with the new Sequencer for a while now I tried to figure out which wizard allows (or prevents) certain activities.


To Q: or not to Q: – that is the question

May 19, 2011

… at least that is one question that often is discussed in an App-V environment.

While monitoring an application setup with the App-V Sequencer, you will have to decide if you install the application to the C: drive (the installer’s default location) or to the Q: drive. Microsoft strongly recommends to always install to the Q: drive (an “MNT install”). However, many
applications proved to work fine after they were installed to C: (a “VFS install”).
This article discusses some of the myths and facts around that “C: vs. Q:” or “VFS vs. MNT” installations.

Note: To limit the size of that post, there is an “Extended Version” availabe as PDF at This PDF contains more detailed information, esp. the details to reason the table’s content.

[Update 2011-05-23: Tim Mangan blogged about an issue when Sequencing to Q: in the App-V 4.6 SP1 Sequencer.]


Posted in App-V, Sequencer
Tags: , ,

Defective component registration with 4.6 SP1 Sequencer

May 13, 2011
1 Comment

This is a loose translation of Sebastian Gernert’s blog articel “4.6 SP1 Sequencer registriert Dateien nicht richtig…” (German).

Sebastian namely thanks Jan Pfisterer and Marius Gawenda, who pointed him to that issue.

Because the new Sequencer does not require a separate hard disk partion for the Q: drive (but uses a Symbolic Link), some components (like OCX controls) may not register correctly. In their registration, they may point to the Symbolic Link’s target (on the C: drive) instead.


« Previous PageNext Page »
%d bloggers like this: