According to http://blogs.msdn.com/b/sgern/archive/2012/10/12/10359028.aspx (a very trustworthy source), Service Pack 2 for Microsoft Application Virtualization 4.6 will be deployed via Microsoft Update “at the end of this month” (which is November). A thing to consider…
Do you want to launch ‘cmd.exe’ within an App-V 5 (Beta) Virtual Environment? ‘OSD Scripting’ can’t help you here… OSDs are gone. Read about a quite neat method that was discussed during the German User Group – and that was streamlined by Volker Kleiner (@vkleinerde)…
All right, you do have your new App-V Beta system installed according to the Beta Documentation – but your Apps just don’t appear on the Client Desktop! Where do you start? Let’s try to figure out some basic steps that can be the foundation of a troubleshooting guideline
“Alles bleibt anders” (Everything remains different) might be a good short description for App-V 5 (Beta). While most of the components keep their names and follow existing general concepts, quite a lot changed under the hood. This post gives you a short overview about Aoo-V 5’s main components and the communication flow between them.
It has been a question “ever since”:
Now, Project Virtual Reality Check (http://www.projectvrc.com) 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…
Microsoft’s Application Virtualization Client 4.5 and 4.6 settings essentially are controlled by Registry values. A while back, Microsoft published an ADM Template to control some of these settings. Login Consultants then published an add-on ADM Template that controls the seetings that Microsoft did not implement.
Now, Login Consultants offers an new, full ADMX Template that uses the more current XML based way of manipulating software settings by Group Policy Objects (GPOs). Furthermore, the new ADMX contains all relevant settings to control App-V Clients, so admins don’t have to deal with two different templates any longer. However, there are som considerations…
During TechEd EMEA 2011 and – a few days later – at the German App-V User Group Meeting, Microsoft showed some features of the upcoming Service Pack 1 for Microsoft App-V 4.6, which is announced for the quarter of 2011.
While Service Pack 1 for App-V 4.6 will significantly affect the Sequencer, there are also some changes to the App-V Client.
#3 Assigning the updated Cache to VDI Virtual Machines (this article)
The asumption of a VDI scenario was the most important driver for Microsoft to develop App-V’s “Read-Only-Cache” functionalities. As Justin Zarb illustrated in one of his articles, storage space may become a significant cost driver in a VDI environment. Given that situation, there are some possibilities how to achieve storage savings. Please be aware that this blog article can not cover all the advantages, disadvantages and a deep technological assessment, so Iam a little bit short here: (more…)
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)
This is the first article of a series discussing Microsoft App-V’s Read Only Cache
#1 Introduction and Key Findings (this article)
With App-V version 4.6, Microsoft introduced the ability to configure its Client’s Virtual Application Cache (= “Cache”) to be accessed in Read Only Mode (also referred to as “ReadOnlyFSD”).
The App-V Cache is a potentially large file (up to 1 TB max) that contains copies of the application packages (“SFTs”) in order to allow fast (local) access to resources that originally are stored centrally on the network. Due to its purpose, it was designed to reside locally on the App-V Client machine (i.e. a Windows Workstation or a Remote Desktop Server/Terminal Server). Storing the App-V Cache locally on the Client allowed the applications to launch with only a minimum impact to the performance. Because of that “local” design and the requirement to fill (load) new application packages into the Cache, full modification and exclusive access rights had to be given to the Cache File for the App-V core services and drivers in the past.
For VDI environments with hundreds or thousands of Clients, this local and exclusive approach represents a significant cost driver, because in VDI environments usually there aren’t cheap, locally attached Hard Disks installed. Instead, SAN storage has to be bought (or rented) to host the Virtual Machines operating system and applications. Because of the exclusive access approach, each VDI Virtual Machine had to have its own, dedicated App-V Cache, often 4-12 GB in size – although all of these individual cache files potentially contain the same or similar applications.
By introducing the ability to access a shared cache in Read Only Mode, Microsoft allows significant savings related to storage costs compared to old versions of SoftGrid/App-V as well as to other Application Virtualization Solutions. Additionally, it allows to store the App-V Cache file outside the VDI Virtual Hard drive, thus unlinking it from the (virtualized) operating system. This results in an increased flexibility, because changes to the Virtual Application set do not require to modify the VM image any longer.
Because of these potential advantages, the announcement of that Shared Cache approach created certain noise in the App-V community, including some hints of how to create a Shared Cache and fill it with a set of applications.