One of the first choices to make when delivery App-V applications via Configuration Manager is whether what mode you want to use for delivery, this post takes a look at both options: Download and Execute The mode we choose to use is decided via a dropdown on the deployment type:
Before you use this calculator to understand how you should size your App-V 5.0 Management Server, remember this calculator uses averages from my “typical environment”, please read this post which explains the numbers, assumptions and logic behind it before proceeding. To use this calculator you will need to calculate/estimate what your
Truth be told the 5.0 App-V Management server is pretty lightweight however it will grow over time and more than likely at some point the question about adequately sizing your database will arise. In the 4.x generation of Management server database growth was primarily influenced by the amount of users
UE-V continues to spark the interest of customers I speak to around the world and a common theme in the feedback is the lightweight and efficient way it roams user state is a breath of fresh air in the face of roaming profiles and other larger user profile management (UPM)
This is a question that burns on the lips of many of the customers that I visit, especially those who are just starting out with this whole App-V thing. To make my life easier I have drawn up a feature comparison to make clear the fundamental differences from an application
TechEd North America was absolutely off the hook! It was great being out there and meeting so many of you face to face. For those who were unable to attend or just want to recap on some of the sessions, fortunately everything was recorded and uploaded onto Channel 9. Check out my
For those who are familiar with App-V 4.x they will be smiling now with the return of a familiar feature of the sequencer. For those who aren’t familiar with previous versions of the sequencer let me explain… Security Descriptors – Full VFS Write Mode In 4.x Security Descriptors copied the
Whoa okay so this Hotfix (also being dubbed the Spring Update) has a lot of offer beyond the standard customer fixes you might be used to. This hotfix brings about significant changes to product itself which include: Publishing Refresh performance improvements User Profile Management support for published app state Package
Performance Guidance for Application Virtualization 5.0 – Now on TechNet
Last update: 18th August 2015 Right it’s that time where I right click and export all my Internet Explorer favourites on App-V 5 and pull together a ramp up guide for all you people interested in learning what all the fuss is about! This a living blog post and will be
That’s right people! We now have a UE-V 2.0 Template which can be used to roam user publish state. This can be leveraged in stateless environments to ensure that our application published state is roamed between machines. This will roam items and locations such as the catalog, shortcuts, FTAs and registry
It would be an understatement to say I am absolutely buzzing to be speaking at TechEd North America next month. For all those attending, I look forward to seeing you there and be sure to pencil in my session: WIN-B355 The Circle of Life for an App-V 5.0 Package: From
App-V integration with Configuration Manager 2012 SP1 and R2 is better than it has ever been. With App-V applications now a fully respected member of the application model, with features such as virtual environments and supersedence it makes for an altogether more polished solution. One thing I often get asked
It has recently been announced that Configuration Manager now supports App-V 5.0 SP2 with either of the following: Cumulative Update 4 for System Center 2012 Configuration Manager SP1 http://support.microsoft.com/kb/2922875/en-us Or Cumulative Update 1 for System Center 2012 Configuration Manager R2 http://support.microsoft.com/kb/2938441 Not only do the new releases bring in full
**Update** The CoW exclusions list in App-V 5.1 has been reduced to just .exe, .dll, .ocx and .com | Click here for more details CoW stands for Copy on Write and it’s a concept discussed in depth in our App-V 5 SP2 Application Publishing and Client Interaction guide. I’ve also
As we all know App-V 5.0 is all about PowerShell and if you’re anything like me you’re always running your import-module appvclient command on the machines you work with. Well today I want to share with you a handy tip that will allow you to save that time by editing
As announced last week, we recently published a great article on TechNet covering App-V 5.0 Capacity Planning. There is a lot of really valuable information in the article which will be essential when sizing out your App-V environment so head over and check it out. I thought I would call
Info around how to plan out and size App-V 5.0 Server Infrastructure has been a hot ask, we recently published an article on TechNet which gives some brilliant guidelines around capacity planning and it can be found here.
At the moment I am chilling in sunny Bangladesh but thought I would set this post to publish today before I left for annual leave last week, nobody can ever say I leave you VirtualVibes readers hanging huh! Today I thought I would share some info around upgrades. During my
We have come a long way from the good ol’ .pkg files we had back in days on 4.x. I have discussed at length both App-V 5.0 – OS Integration – State Changes and Global File State Changes in App-V 5.0, but what about when we make changes to global
Have you ever come across this error before? Investigating further into the event logs we find the following explanation of what went wrong: Registry staging! Now that’s something I have discussed in more detail here but essentially the cause of this error is due to the fact the App-V client
Hope you all had a great holiday season with friends and family! Time to kick off the New Year with some more App-V! With the release of SP2 for App-V the questions around supportability and backwards compatibility have arisen once again. This is the same as it has always been
Everyone who has being anticipating the release of SP2 for App-V 5.0 will understand that one of the core new features it has brought is the support for shell extensions, when you throw RunVirtual and browser helper objects into the mix too, what we end up with are very blurred
Happy days! That’s right people, the wait is over! After having the beta in our hands for a while now, the official release of App-V 5.0 SP2 is now available for both sequencer and client as part of MDOP 2013 R2. Some of the key features of this release are:
I have talked lots about how App-V 5.0 packages integrate so tightly with our client machines and how it stores assets on the platform. In this post I want to clarify where App-V puts stuff, by stuff I mean package related file system and registry assets. The diagram below explains
In App-V 4.x we had something called autoload targets and triggers which could be used in combination to make App-V applications automatically get cached depending on certain factors, in App-V 5.0 we have a similar more simple equivalent setting called AutoLoad. This setting like most App-V Client configurations can be
With App-V we have something called “Full Infrastructure”, this is used to refer to an App-V Management Server based method of delivery for App-V packages. App-V 4.x In App-V 4.x we had the App-V Management Server role which was responsible for not only managing the packages but also servicing client
It not unusual that in the mix of all your weird and wonderful applications you will have a handful that will leverage a .bat file shortcut to kick off your application. Let’s deep dive into the mechanics of sequencing and delivering these type of applications. Take this example where I
Anyone would be forgiven for thinking that App-V 5.0 and CM 2012 SP1 integration is just a simple managed way of using standalone mode. By that I mean that Configuration Manager simply sends out PowerShell commands to add and publish packages leaving App-V to handle the rest. The truth is