With the App-V 5.0 Sequencer we have three options for optimising how our packages stream to our clients:
Click NextIn previous versions of App-V this would lump everything into one feature block so the whole package had to be download before launch. Now this does something completely different called Fault Streaming. Fault Streaming downloads the bits the application needs as its requests it, in other words the minimum amount will be streamed depending what files the application calls upon. This still keeps a FB0 however.
Run Selected or Right Click LaunchThis allows you to launch and interact with your application(s) and simulate usage in order to define a Feature Block map. Click here to read more about how this is different in App-V 5.0 with a new Publishing Feature Block/FB0.
Tick the box!Ticking the box that says “Force application(s) to be fully download before launching” does exactly what it says! No FB1 or FB2, the whole package will get downloaded at first launch. This approach still defines a FB0 too.
The Pros and Cons Here are the theoretical pros and cons of each approach:
Quick first launch time
Potential hang while application requests new bits during use
Feature Block Definition
Less hanging during use as commonly called files should already been downloaded in FB1
Slower first launch time compared to fault streaming
No fault stream associated hanging and offline use available for first launch
Slowest first launch time out of all options
To read more about Feature Block 0 with App-V 5.0 click here
Hello, any idea to modify "Force application(s) to be fully downloaded " after to do create the package ? (xml ?)
Hi you can change the optimisation by upgrading your package and re-monitoring.
Is there any option to change in configuration files manually instead of upgrading the package.
What is best practice for XenApp 65 environment in terms of optimisation?
@ K - It depends on the way you configured your client.