Kirx' Blog -

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: , , , ,

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: , ,

About the App-V Client Cache size not being (fully) controlled by the Registry Value FileSize

April 17, 2010


The App-V Client comes with the Registry Value “FileSize” in the “AppFS” key that indicates to control the App-V client’s cache size. This is not the case.

Instead, there might be a difference between the FileSize Registry value on the one hand and the actual maximum value and the value shown in the App-V Client Management Console on the other hand.

To adjust the maximum cache size using centrally controlled methods you have to initialize/flush the App-V cache or to use Microsoft’s App-V Cache Resizer Resource Kit tool.


Posted in App-V, Tools
Tags: , , , , ,

How to upgrade to Microsoft Application Virtualization 4.6

February 23, 2010
Leave a Comment

Now that MS App-V 4.6 has been released, one of the tasks is to define an upgrade path for your SoftGrid 4.2/4.2/App-V 4.5 infrastructure to the new App-V 4.6 release.

If you already run App-V within your organsation, probably the new key feature – 64 bit Client support – is not that relevant for you. Howerver, you may plan to roll out Office 2010, you may plan to build an VDI envoronment or maybe you just waited for that release because you just want to upgrade you “old” SoftGrid deployment.

Upgrading to a new version always is a good time to consider and re-think your current installation:

  • How did the amount of users scale?
  • Do Subsidaries play a role in your infrastructure?
  • Do you want to use one of the new Deployment Solutions that are available with App-V 4.5/4.6?
  • Do you plan to migrate your base Operating System on Desktop computers, Terminal Servers (now RDS server) or hosted VDI environments?
  • How startegic will Application Virtualization be for your application deployment?


Posted in App-V, Management
Tags: , , , ,
« Previous Page
%d bloggers like this: