Kirx' Blog -

Microsoft Application Virtualization 4.6 Read Only Cache for VDI environments #2

August 20, 2010

Setting up the Staging Client and Loading Applications into the Staging Cache

Article Series Content

#1 Introduction and Key Findings

#2 Setting up the Staging Client and Loading Applications into the Staging Cache (this article)

#3 Assigning the updated Cache to VDI Virtual Machines


This article will focus on preparing the “Staging Client”

In App-V’s “VDI Mode”, the shared cache file potentially will be accessed permanently by different VDI machines. Therefor, any update to that Read Only Cache, including its first filling, has to be applied to a different cache file. This special instance of an App-V Cache file will be called “Staging Cache File” hereby. Because that file uses a proprietary format, the only way to apply any updates is by using a “normal” App-V Client machine. This (virtual) client machine is usually called “Staging Client”.

It is supposed that you already have a “full” App-V Infrastructure including the App-V Management Server. Also it is supposed that this infrastructure has been validated to work propperly (i.e. applications already have been deployed to Test Clients)


Posted in App-V, Client
Tags: ,

Should the App-V Sequencer be installed into the Snapshot Image?

August 14, 2010


In order to create a persistent state of the Sequencer Workstation for App-V Sequencing, it is recommended to either use Virtual Machine Snapshots or some Hard Disk Imaging Technologies. The reason for creating such a persistent state is that Sequencing always should be performed from a “clean” workstation and imaging or using snapshots are two very fast ways to accomplish this.

The Common Sense about that persistent image is that it should reflect the “Core (Client) Image” to certain extends and also it should not have any background services active that negatively influence the sequencing process. Microsoft’s Sequencing Guide whitepaper describes that more detailed.

But what about the Sequencer Software itself: should it be installed before the image gets created – or should it be installed each time after the image has been reverted?

In the past, there was an easy answer to that question. It was caused by a special behaviour (you may call it a bug) of the Sequencer Software – and this answer was: Do not install the Sequencer before creating the image. Essentially, the reason for this advice was that the Sequencer sometimes generated equal Package GUIDs (instead of random GUIDs) – it did not do that always, but explaining that would be out-of-scope here. Therefore, the Sequencer software usually was not installed before creating the image…


%d bloggers like this: