/build/static/layout/Breadcrumb_cap_w.png

What is the difference in launching the shortcut in configure software phase and installation phase in App-V?

In App-V 4.6 or 5.0 or 5.1, when we are sequencing an application.
First phase is to install our application during sequencing and during this time we can launch the shortcuts also and all these changes will be recorded.

But they have given a separate option for us to launch shortcuts.
4D0O8m.png
.To do  these configurations in the “Configure Software” phase, after checking the “I am finished installing” box and clicking “next” in the Sequenceri24EgA.png

Can anyone please explain what is the difference in launching the shortcut in the above two phases.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: dunnpy 6 years ago
Red Belt
0
In App-V 4.x all config was done in the install phase and the launch dialogue was there to configure Feature Block1, if you didn't launch anything then the whole application would be in FB1.

In App-V 5.x the launch is there to manage first use tasks, it's a step added that wasn't in 4.x.to clarify the need to configure licensing and other items on first launch. The FB stuff is now in the customize phase, in the streaming options.

Dunnpy
Posted by: Badger 6 years ago
Red Belt
0

yep, not much really.

There is no real difference as dunnpy mentioned, but it is handy to have a distinction between the install, then the config. I normally run the app from the Startmenu shortcuts during the 'install phase' and do all the config I want rather than in the App-v dialogue 'run each program...' mainly because the App-V GUI stress's me out.

One of the best things Microsoft did was add that tick box in your first image..
'I am finished installing...'

Posted by: apptopack 6 years ago
Posted by: ur00361883 6 years ago
Black Belt
0
@Dunnpy

I think you are talking about the below screen which comes in streaming section in 4.6 also.


Comments:
  • This screen comes from 4.6 SP1 only and not in 4.6. - apptopack 6 years ago
    • Let's take latest versions only, can you explain why exatly this shotcut launch screen for as the explanation given by Dunny for streaming is for the second screen. - ur00361883 6 years ago
      • That's the way Microsoft has developed :) If you skip this streaming part, then the entire package would be downloaded upon launch of the shortcut. This will consume more time and delay the launch process. - apptopack 6 years ago
    • The streaming screen is for launching the shortcut for populating feature blocks.But can you tell what is the use of the shortcut launch which comes after finishing installation phase and clicked next.Because we can launch the shortcuts in installation phase itself.What is the difference to do here seperately. - ur00361883 6 years ago
      • You can perform changes to the application by launching the shortcut in both installation phase and in configure software phase(sequencer will be monitoring even in configure phase.It is also possible to manage the tasks for programs that are not listed on this page by launching them outside of the Sequencer using Windows Explorer.).Say if you have missed out to customize in install phase, you can then use the configure phase to perform changes. Hope its clear. - apptopack 6 years ago
      • Microsoft recommends to use the configure phase to perform additional configurations.Though you can do it in install phase. - apptopack 6 years ago
    • Is there any functionality difference if any do it in installation phase or this shortcut launch phase.?Because microsoft is still retaining this screen in 5.1 version also.

      There should be some difference because of which they kept this screen seperately. - ur00361883 6 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ