I suggest you ...

Allow for package upgrades to force application(s) to be fully downloaded before launching, and/or show the loading progress bar

We package all our apps to load 100% before launching, and deploy them using full infrastructure. We have either configured by design or by default the fact that users load their apps on first use, not at logon.
Every package we have displays a 'loading' type progress bar then on the first use, and gets to 100% before the program launches for the user.

I recently had to upgrade a package, so I did that using the sequencer. I knew what to change very specifically, so I used the 'Edit package' option when modifying the existing package. I made my file and registry change, and saved the package to a 0.0.0.2 version.

The upgrade went well, but I have noticed something since then.
New users who never launched the package before do not get the progress bar. Not only that, but according to Get-AppvClientPackage output (that I run during launch time) it seems it is actually launching before 100% gets cached.

Why is this and why wouldn't the editor let me say to still load 100% before launch? I can understand conceptually why using 'edit' mode is an issue for creating "feature block 1" if I wanted to stream it, (because I am not executing the program). Wouldn't having a "Force application(s) to be fully downloaded before launching.." make more sense to be "default" in this scenario to rather than streaming delivery by default? And regardless can this not be a choice?

So my suggestion is to change the default to load 100% before launch, or at least give us the option and either way show the progress bar regardless of the choice.

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Bruce shared this idea  ·   ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Andrew G commented  · 

        @Roy, sorry for a late comment, but we've had bad performance from SCCM when using fault tolerance. Unfortunately we are full download because of that. We did follow up with MS and was told (basically) its just how SCCM is. Even for relatively small packages.

        As to the topic when you make changes to the package using edit only, it changes your package from download full to fault tolerance. Not sure why. You can see this in action by taking a package that is full download, and inspect the streammap.xml. You will see LoadAll="true". Take that same package, make an edit to the file system, save and that loadall is taken away.

        My opinion, I really see no reason to allow for all 3 options to be inside the package and flipped with a checkbox:
        For example, you always know what 100% is (full download), and you always know what 0% is (fault tolerance), so ask for streaming block and allow any option to be toggled via deployment.XML.

      • Roy Essers commented  · 

        Whats wrong with fault streaming (Fb0 only). Only in rare cases I configr fb1 or 2, depending on the app performance

      • Bruce commented  · 

        Again, this is for package upgrades. It is obviously in our control when creating a net-new package.

      Feedback and Knowledge Base