Hi,

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.

Muttley
0 Comments   [ + ] Show Comments

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.

Answers

0
One thing to point out is some vendor supplied applications may not support advertised installs for whatever reasons.

Though there are some vendors that simply disable the advertised install on purpose, for whatever reasons. [;)]

To troubleshoot your MSI, you need to ensure that the required sequence of actions are still in the MSI package. eg: ensure that the required actions are populated in the AdvtExecuteSequence table, such as CreateShortcuts and Publish_______ etc etc etc.
Answered 05/23/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
And they are:
CostFinalize
CostInitialize
CreateShortcuts
InstallValidate
PublishComponents
PublishFeatures
PublishProduct
RegisterClassInfo
RegisterExtensionInfo
RegisterMIMEInfo
RegisterProgIdInfo
InstallFinalize
InstallInitialize
MsiPublishAssemblies
Answered 05/24/2006 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity