App-V 5.0 SP3 Sequencer issue

There is a bug with the App-V 5.0 SP3 Sequencer that has just been release some days ago. When you try to install the MSI of a created App-V package created by the SP3 Sequencer, the installation only works when you run the MSI installation in an elevated cmd (start cmd.exe with “Run as Administrator”). If you deploy your apps with SCCM, you’re usually not affected when you run the installation by the system account.

The following error messages are shown when you install the msi without elevated cmd:

error1 error2

I created an mst that fixes the issue. Do the following steps to apply the fix :

  1. Download the mst that fixes the issue: http://www.notmyfault.ch/downloads/AppV5_SP3Fix.zip
  2. Extract the mst file and copy it into the same folder as your msi file
  3. Run the following command:
    msiexec /i YourAppvPackage.msi TRANSFORMS=AppV5_SP3Fix.mst

If you want to run it unattended, add /qb as parameter. Make sure your current directory is the one that contains the msi/mst or just add the full path to your msi and mst. Don’t rename your msi, use the original name that has been created by the sequencer.

You can also permanently apply the transform (mst) to the msi with Orca.

The root cause of the issue is a changed setting in the MSI. The custom actions responsible to publish and remove the App-V package won’t run under the local system account with full privileges (no impersonation)

AppV_SP3_sequencer_issue

The mst I created changes that configuration back so that these custom actions run under the local system account with full privileges (no impersonation) as it was prior to SP3. This change is done by changing the above marked type values from 1025 to 3073.

 

2 thoughts on “App-V 5.0 SP3 Sequencer issue

  1. There is a template in the sequencer install used to create that MSI. In years past I used to mod that for better MSIs. Not sure if you can fix it there, but have a look and fix it just once.

    Tim

  2. Hi Tim – Thanks for that note. I have already seen these templates (PackageMsiTemplate.msi). They still exist. It’s just not so “sexy” that there exists one template for every language. So if you want to customize it, you need to customize the one according to your language you’re running the sequencer in. But of course that would eliminate the need to modify the msi after it has been created.

    Regards, Michael

Leave a Reply

Your email address will not be published. Required fields are marked *