Shared Content Store is proving a very popular feature with App-V 5.0 and with my recent post on The Microsoft App-V Team Blog going deeper into the subject I thought I’d take the opportunity to pull together some useful SCS links: Introducing Shared Content Store in App-V 5.0   Shared

This is now done within the package editor rather during the sequencing workflow itself, however the functionality is identical. We talked about this technique in 4.x here, all these same concepts apply in 5.0 so if you are interested in the concepts jump over to the post. What I want

That’s right, Hotfix 1 for App-V 5.0 SP1 Management Server is now available. The purpose of this hotfix is to fix the issue with priority setting within the management server as discussed here around connection group conflicts. Read all about this hotfix and download it from here.

5th December 2014 | PLEASE NOTE: This feature has been deprecated and is not supported. Please use RequirePublishAsAdmin feature. 8th November 2014 | PLEASE NOTE: This feature is being deprecated and is not supported. 8th April 2014 | PLEASE NOTE: Enabling PackageStoreAccessControl client configuration setting on a computer that is running Remote Desktop Services (RDS) or

Hello VirtualVibes readers, In this post I am going to share with you the App-V 5.0 SP1 client footprint while idle. Please bear in mind this information will naturally vary between environments and serves only as a guideline. First lets understand what processes actually run on our App-V client machines

Anyone who has downloaded and installed the App-V 5.0 SP2 Beta may have noticed that the client doesn’t seem to have the usual client GUI which we have become familiar with: Well this isn’t an issue or bug, it is actually intentional. The client graphical user interface has been left

So it’s no secret that one of the major improvements to come along with the App-V 5.0 SP2 Beta is the way we now handle and support shell extensions and runtime dependencies. Let’s take a closer look… Shell Extensions They are finally here! Probably the most requested feature when we

That’s right App-V 5.0 SP2 Beta is here, along with updates for App-V 4.6 and UE-V. Highlights ·        App-V 5.0 SP2 Beta o   Shell Extension Support o   Run Time Dependencies Detection o   GUI Improvements ·        UE-V 2.0 Beta o   Windows 8 App Support o   Company Settings Centre o   Improved Synchronisation

In a previous post we talked about state changes with App-V packages and how these changes were stored, that post revolved around user profile based changes that we would typically like to roam. How about changes that are made to non-user profile locations such as the package root itself? These

Ever since my blog on Adding and Publishing a Package in Standalone Mode I have noticed an increased number of people hitting this issue when trying to add/publish their App-V packages. Having grappled with what the cause of this could be for the last few weeks, bouncing ideas around with

5 Years 6 Months 2 Weeks and 1 Day ago my mate Justin Zarb wrote a brilliant blog post on Specifying a Working Directory in App-V 4.x and how we can use the .OSD to achieve this. Well here I am a good while later, posting about how we do

Following on from my post called Understanding the PVAD where we talked about how things work in the absence of the Q: mount drive we had in previous versions of App-V, I want to share with you some insights into how permissions work on both the PVAD and VFS for

The Primary Virtual Application Directory, more efficiently called the PVAD has been a topic of much discussion ever since the advent of App-V 5.0. I guess although we complained about the Q: mount drive we had in App-V 4.6 it did make things really easy to understand. The PVAD is

There have been some great posts flying around talking about the RunVirtual feature in App-V 5.0 over the last few weeks and months, both from some of the guys here at Microsoft and our MVPs. So I thought I’d break it down in true VirtualVibes fashion as an end-to-end step

Sequencing a shortcut is a commonly used method in App-V 4.x to get virtual packages to interact with something local. Especially when the local element is the parent in the relationship. For example local Internet Explorer and virtualised Adobe Flash Player or local Microsoft Office and virtualised plugins. The first

In previous parts of this series we looked at the App-V 5.0 package format, how it sits on our client OS in the file system cache and how the registry works. So that’s all well and good but what about when about when users make customisations to packages, how do

Not a huge raft of changes in terms of SP1 for App-V 5.0 apart from much better language support and also the foundations for support of Office 2010, more details below! Download MDOP 2013 to get this latest release. About App-V 5.0 SP1   How to sequence Microsoft Office 2010 in

Now we understand the package format and client file system for App-V 5.0, let’s take a look out how the registry looks in terms of OS integration. As mentioned in Part 1 of this blog series, within the .appv package we can see a registry.dat file which contains the entire

Following on from my post App-V 5.0 OS Integration – Part 1 – Package Format  where we talked about how a App-V 5.0 package is made up, now we can move on to look at how this package is reflected on your client operating system after the package has been

Yep that’s right HF1 for App-V 5.0 is officially released and publicly available, you can find it here. It fixes two identified issues, I have come across issue 2 recently and it is potentially an issue that anyone using App-V full infrastructure could have hit so it’s great to see

In this series of posts I am going to take you behind the scenes of how our packages integrate with our operating system in App-V 5.0. The most logical place to start is with the package itself and understanding what is output by our Sequencer. Let’s take this Paint.NET package

Deploying a package in standalone mode in App-V 5.0 is really really simple! I recommend having a standalone client somewhere to everyone I talk to regardless of infrastructure choices because it is the easiest way to quickly test a package before deploying to an environment. There are two main steps to

Following on from my post around “App-V Package Streaming Optimisation” let’s talk more about the Publishing Feature Block. In App-V 4.x if we chose to optimise our package we would end up with a FB1 (Primary Feature Block) and FB2 (Secondary Feature Block). FB1 would contain the assets we need

Connection Groups are proving a really popular feature in App-V 5.0, however how do we handle the situation whereby one application is the member of more than one connection group and both are published to the same AD group? Let’s take this following theoretical scenario with 3 apps (NotePad++, Winrar

App-V 5.0 Connection Groups build on the success of Dynamic Suite Composition (DSC) in App-V 4.x and presents a much more manageable experience. Let’s take an example, below I have published NetBeans, it’s an IDE application which relies on the Java Development Kit (JDK) being present. I have also packaged

In App-V 5.0 we have the great ability to have user specific configurations applied to different AD groups for the delivery of an application. Essentially meaning one set of users can receive an application in a certain way and others users will get the same application in a different way.

The workflow for package upgrades is pretty similar in App-V 5.0 as it was in 4.5, however there are now a few added benefits around phased targeted rollout of App-V upgrades…. I have a version one of Paint.NET deployed here: This version of the package is without a additional plugin