Just after a clarification (new to this all)

With Appp-V sequencer building SFT files needs to be done on the platform for which the Virtualized package is to be deployed eg: Win 7 sequencer for Win 7 Package deployment

If you use AdminStudio to create SFT files and Virtualized packages, are they still platform specific, or will they run on any platform?

Hope that makes sense

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Same rules apply to both products. When you sequence you use the lowest common denominator which in turn may provide the greatest portability. Ideally you build the sequence on the same operating system as the target but it is possible to get into scenarios such as sequence on XP then deliver to XP, W2K3, Vista, W2K8, Win7, W2K8R2. Now I'm not saying this is always going to work because depending on the platform you are delivering to and the requirements of the application but that is generally a rule of thumb when sequencing for portability.

With App-V 4.6 SP1 Package Accelerators things are different because the package is essentially re-hydrated and not monitored so the state of the sequencing station does not really matter. However the target operating system you are delivering to may be an issue depending on what operating system the package accelerator was generated on.
Answered 03/29/2011 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
@ KKaminsk

Excellent, thanks for the reply, I thought it may be something like that. We have a project for repackaging on Win 7, but i know at some point there will be a requirement to use those Apps on XP where a machine has not yet been upgraded. Jut gauging what additional work may be required eg: redoing the package for XP.

Again thanks for your help.
Answered 03/29/2011 by: skylizard
Senior Yellow Belt

Please log in to comment