Recently I was working on a XenApp project where I noticed an issue with the server builds when trying to deliver App-V packages. The issue was that 8dot3 naming (a requirement for App-V package delivery) had been disabled. This setting is easily changed with a simple fsutil command or change
In previous blog posts I have talked about various models for RunVirtual detailing how we can deliver and manage the feature in conjunction with connection groups. In this post I would like to share with you a simple script which you can include in your package delivery to provision the
Over my design and implementation projects with VMware User Environment Manager (UEM) I couldn’t help but pay particular interest into how it works with App-V. In this blog I intend to lift the hood on how UEM captures and collects user settings for App-V and the mechanisms it uses to
I have recently been working a lot with VMware User Environment Manager (UEM), formally known as Immidio Flex+. If Ivanti’s Desktop Now powered by AppSense is too complex and Microsoft’s UE-V is too simple then UEM surely sits squarely in-between the two! It has a very light weight infrastructure and still
While working with a large financial organisation in London last week, someone brought my attention to how RunVirtual is giving them some interesting side effects they didn’t quite expect when running other local tasks or applications. I wasn’t too surprised by what they were seeing but thought it would be a good
I was recently working with a client who were getting extremely frustrated by the understanding that they could only really limit delivery of App-V packages by target operating system. They noticed the option as part of the sequencing process as shown here: They wanted a much more granular way to control whether
Hi All, It’s been a while since I last posted as I have been really busy working with clients over the last few months. I just wanted to take this opportunity to share with you a real world example of how I have recently used RunVirtual and APPVVE to enable
I recently had a the chance to sit down for a few days with a financial firm in London with the aim of driving down publishing times in their stateless non-persistent VDI environment. Over the engagement we implemented a range of techniques to drive down publishing times and consequently drive
App-V in Windows 10 So I’m sure you have all heard by now that App-V has made its way into Windows 10! This is a major milestone for the product and should pave the way for a much larger scope of adoption across the enterprise. As somebody who has worked
When introducing App-V concepts to people who are new to the product one some of the more interesting conversations arise as soon as the word streaming is mentioned. Streaming means many things to different people, everyone tends to have pre-conceptions about what it entails and often the term is misused. The
We have had a fairly constant flow of updates to App-V 5 ever since the release in November 2012. From service packs to hotfixes, we have seen the product grow and mature. However even I sometimes get confused or forget exactly what features or fixes came with which release. Of
Great news, App-V 5.1 has finally been released! It has been a little while since the announcements at Ignite but now it is here at last. Overall this release goes a long way to consolidate all the work that has been put into App-V 5.0 since its original release and sends
A few weeks ago I was informed that I have been selected to join an exclusive group of Microsoft community leaders and industry experts known as Microsoft Most Valuable Professionals (MVPs). The programme looks to highlight and recognise people outside of Microsoft who have made significant contributions to their software
In this brief post I am going to explain the purpose of the PublishingSource registry value in App-V 5.0 and how it works. PublishingSource can be found in either of the following locations depending on whether the package has been published to the user or published globally: HKEY_CURRENT_– USER\Software\Microsoft\AppV\Client\Packages\{PACKAGE GUID}\Versions\{VERSION
When I first took a look at how SCCM manages App-V connection groups I have to say I was really impressed with the flexibility of the rule based approach of Virtual Environments. Since then App-V connection groups have developed and moved forward, most notably with the recent SP3 release. I
**App-V 5.1 has now been released | For the App-V 5.1 Feature Run Down – Click here** Wow, what an amazing trip to Chicago that was! Ignite was buzzing with people, technology and some really great sessions. Despite the fact that there was only two App-V focused sessions in the
I am frequently asked about the various options available when updating a package using App-V 5.0. In this post I will clarify some of the key decision points and how they will impact the way you deliver your updated package. Control Updates within the Sequencing Process A commonly asked question
App-V 5.1 Sequencing Advanced Techniques and Troubleshooting, Infrastructure and MSIX 7th – 9th – London – East Central
Since the release of App-V 5.0, connection groups have been a highly rated feature of the release, it is something that brought about a whole new level of flexibility and manageability compared to dynamic suite composition in 4.x. However connection groups have evolved overtime and there are many nuances to
SP3 for App-V 5.0 introduced a new feature called RequirePublishAsAdmin which allows Administrators to restrict non-admins publishing packages to themselves if they are already added to the machine. For a full run down of this feature read here, it was on this post a commenter brought up the question of
Since the introduction of App-V 5.0 and the PowerShell commands which we have come to know and love there has always been the question around ways we can execute these commands remotely. As more and more organisations start to look at how they go about supporting their App-V environments and
App-V 5.0 SP3 is now available on MSDN as part of MDOP 2014 R2, there are some great features that you need to check out! Here are detailed posts detailing the key features of this release: – Connection Groups 2.0 – More Manageable & More Flexible – User RunVirtual Key – Merged Roots
Right so pre SP3 for App-V 5.0, aslong as a package was added into the client cache, any user (admin or non admin) could go ahead and publish the application to themselves with a quick and easy line or PowerShell. There weren’t really many ways to negate this apart from
Before I say too much lets play a game of spot the difference! Below are two screenshots of me sequencing Paint.NET in both pre-SP3 and SP3 for App-V 5.0: Pre-SP3 SP3 Spotted it?! Of course you have. You will notice that the SP3 sequencer no longer requires the entering of
Connection groups have been given a lot of attention in the latest SP3 release of App-V 5.0 in what is now a more flexible and more dynamic overall picture of how we can manage these groups. There are two main improvements that have been brought into the fold: Optional Packages
That’s right people! The RunVirtual feature that was limited to machine targeted packages affecting all users has now been enhanced to allow user specific deliveries. If your not familiar with RunVirtual then read here first for a quick run down. Machine RunVirtual First of all its worth mentioning nothing has changed
Lately I have had a lot of people ask me about securing the App-V 5.0 infrastructure by utilising the HTTPS protocol so I thought I would share a step by step guide on how you can go about implementing it. There are three main areas you can utilise HTTPS in an App-V
UE-V is such a simple yet elegant solution for user state management, it is something anyone can easily get up and running with minimal effort and planning required. In this blog post I am going to share everything you need to get going by explaining the simple mechanics that form