Does anyone have any good ideas on troubleshooting vendor supplied .msi files that won't advertise?

I was trying to deploy a package through Group Policy, but it doesn't work. It was visible in Add Remove Programs, but no files or shortcuts were installed.

I checked the installation and saw that the shortcuts weren't advertised, so I created a transform file and made a new advertised shortcut, but this also didn't install.

I then tried to simulate the GP deployment using the commandline msiexec.exe /ju myinstall.msi TRANSFORMS="myinstall.mst" (to save time) but still couldn't get it to install.

What things in the installation should I look for that I could fix?

My other option is to extract all the files and registry settings and make a new installation, but this is a last resort.

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


Some vendor supplied MSI's simply do not support Group Policy user-based advertised installations, for whatever reason. Though, targeting a computer (rather than users) will result in the whole MSI being installed.

To determine if a MSI can support user-based installation via Group Policy, you need to ensure that the shortcuts are advertised shortcuts. You won't be able to simply delete the non-advertised shortcuts and replace them because the feature set needs to be configured accordingly.

In addition to the above, you need to ensure that the Advertised Tables have been configured by the vendor as well.
Answered 06/12/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment