locked
AppV 5.1 Standalone MSI bug? RRS feed

  • Question

  • Sequenced several apps using sequencer 5.1.

    Added script into Deployment config.

    Seems that standalone MSI would not use deployment file beside the MSI. SCCM successfully launches scripts.

    Hotfix Package 1 for Microsoft Application Virtualization 5.1 on a cliens is installed. Scripting enabled.

    Wednesday, February 3, 2016 9:23 AM

Answers

  • Confirmed, so I looked at the MSI with Orca at the SetPublishPackage32 Customaction:
    SP3: APPV_OR_MSI_FILE=[APPV_OR_MSI_FILE];APPV_DEPLOYMENTCONFIG=[APPV_DEPLOYMENTCONFIG];APPV_LOCAL=[APPV_LOCAL];MSI_TEMPLATE_REGKEY=Software\Microsoft\AppV\MsiTemplate\[ProductCode]

    5.1: APPV_OR_MSI_FILE=[APPV_OR_MSI_FILE];MSI_TEMPLATE_REGKEY=Software\Microsoft\AppV\MsiTemplate\[ProductCode]

    Clearly missing the APPV_DEPLOYMENTCONFIG property.
    As a workaround you could use the custom transform Dan created. Have a look here


    Roy Essers

    Friday, February 12, 2016 12:24 AM
  • I can confirm this. App-V 5.1 generated MSI no longer uses deployment config file. I have blogged about this with a simple example.

    http://app2pack.blogspot.com/2016/02/app-v-51-bug-or-expected-behaviour.html


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    Wish to add MVP behind my name :)

    app2pack.blogspot.com: app2pack.blogspot.com

    Thursday, February 11, 2016 6:27 AM
  • By Default, AppV do not use the Config Files unless you specify to use one. If you don't want to do that then, you can directly write your scripts inside the AppX Manifest.xml & import it into your package using Export/Import option under Advanced Tab in the Sequencer.

    http://blog.fslogix.com/putting-your-app-v-scripts-directly-into-the-.appv-5.1-file


    Posted AS IS with No Warranties. Mark as Answer if this answers your question, It will help other community members.

    Wednesday, February 3, 2016 9:55 AM

All replies