{"id":1232,"date":"2008-10-13T17:43:58","date_gmt":"2008-10-13T17:43:58","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/2008\/10\/microsoft-virtualization-part-4-application-virtualisation.htm"},"modified":"2008-10-14T07:52:07","modified_gmt":"2008-10-14T07:52:07","slug":"microsoft-virtualization-part-4-application-virtualisation","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2008\/10\/microsoft-virtualization-part-4-application-virtualisation.htm","title":{"rendered":"Microsoft Virtualization: part 4 (application virtualisation)"},"content":{"rendered":"

I’m getting behind on my blogging (my day job keeps getting in the way) but this post continues the series I started on Microsoft’s virtualisation technologies. So far, I’ve set the scene<\/a>, looked at host\/server virtualisation<\/a> and desktop virtualisation<\/a> and this time it’s Microsoft Application Virtualization<\/a> – formerly known as SoftGrid<\/a> and also known as App-V.<\/p>\n

Microsoft provides a technical overview of App-V<\/a> but the basic premise is that applications are isolated from one another whilst running on the same operating system. In fact, with App-V, the applications are not even installed but are sequenced into a virtual environment by monitoring file and registry changes made by the application and wrapping these up as a single file which is streamed to users on demand (or loaded from a local cache) to execute in its own “bubble” (technically known as a SystemGuard environment). Whilst not all applications are suitable for virtualisation (e.g. those that run at system level, or require specialist hardware such as a “dongle”) many are and one significant advantage is that the virtualised applications can also be run in a terminal services environment (without needing separate packages for desktop and server-based computing). It’s worth considering though, that virtualising an application doesn’t change the license – so, whilst it may be possible to run two versions of an application side by side, it may not be allowed under the terms of the end user license agreement (e.g. Internet Explorer).<\/p>\n

I wrote a post about application virtualisation using Softricity SoftGrid<\/a> a couple of years ago but, with App-V v4.5, Microsoft has made a number of significant changes. The main investment areas have related to allowing virtualised applications to communicate (through a new feature called dynamic suite composition), extending scalability, globalisation\/localisation and security.<\/p>\n

Of the many improvements in App-V v4.5, arguably the main feature is the new dynamic suite composition<\/a> functionality. Using dynamic suite composition, the administrator can group applications so that shared components are re-used, reducing the package size and allowing plugins and middleware to be sequenced separately from the applications that will use them. This is controlled through definition of dependencies (mandatory or optional) so that two SystemGuard environments (App-V “bubbles”) can share the same virtual environment.<\/p>\n

On the scalability front, App-V 4.5 also takes a step forward, as it provides three delivery options to strike a balance between enterprise deployment in a distributed environment and retaining the benefits of application isolation and on-demand delivery. The three delivery options<\/a> are:<\/p>\n