[wpkg-users] MSI install issues

[Andrew Rae]

Hi

I use 'Orca' - details here http://support.microsoft.com/kb/255905  

If my memory serves me correct, it is the 'property' table that contains parameters accepted on the command line when installing an MSI.

With Orca, you can make an MST to change anything inside the tables within the MSI.

This has been useful in the past to change (for example) start menu shortcut locations etc - just takes a little figuring out which entry to edit!

Hope that helps
Andrew

-----Original Message-----
From: Shier, Jon [mailto:JonS at mtrx.com] 
Sent: 09 September 2011 19:12
To: Andrew Rae
Subject: RE: [wpkg-users] MSI install issues

Is it Superorca or just orca? And what Table are you looking at to see the MSI Options?

Thanks
~Jon 

-----Original Message-----
From: Andrew Rae [mailto:A.M.Rae at leeds.ac.uk] 
Sent: Thursday, September 08, 2011 9:30 AM
To: Shier, Jon
Cc: wpkg-users-bounces at lists.wpkg.org
Subject: Re: [wpkg-users] MSI install issues

Hi Jon,

Sorry for waffling, a bit of a brain dump, hope some of it helps.

It depends on how the MSI is actually made & configured by the manufacturer of the software.

I find  that a good thing to do is to actually open the MSI I want to install in a software package called Orca (which is free) to see what options there are for that particular MSI (and then potentially create an MST to use at the same time as the MSI).

If there were more than one or two parameters you want to pass through the MSI installer, in this case, you could put the "ALLUSERS=1" into an MST and then install the MSI with something like: 'msiexec.exe /I installer.MSI TRANSFORMS=installermstfile.MST'


Bit of background - i'm guessing you've probably got WPKG installing the software as 'SYSTEM' user account on the client machines, any 'per user' settings disappear into the SYSTEM user's profile - which you never log in as.

Andrew

From: "Shier, Jon" <JonS at mtrx.com<mailto:JonS at mtrx.com>>
Date: Thu, 8 Sep 2011 16:48:45 +0100
To: "heiko.helmle at horiba.com<mailto:heiko.helmle at horiba.com>" <heiko.helmle at horiba.com<mailto:heiko.helmle at horiba.com>>
Cc: "'wpkg-users at lists.wpkg.org<mailto:'wpkg-users at lists.wpkg.org>'" <wpkg-users at lists.wpkg.org<mailto:wpkg-users at lists.wpkg.org>>
Subject: Re: [wpkg-users] MSI install issues

That seems to work, why would I need not need to supply that on all of the msi files?

~Jon



From: heiko.helmle at horiba.com<mailto:heiko.helmle at horiba.com> [mailto:heiko.helmle at horiba.com]
Sent: Wednesday, September 07, 2011 8:17 PM
To: Shier, Jon
Cc: 'wpkg-users at lists.wpkg.org<mailto:'wpkg-users at lists.wpkg.org>'
Subject: Re: [wpkg-users] MSI install issues

wpkg-users-bounces at lists.wpkg.org<mailto:wpkg-users-bounces at lists.wpkg.org> wrote on 08.09.2011 03:41:01:

> I have one msi install that I am having issues with using wpkg, it 
> will not create the program files shortcuts or desktop shortcuts. I 
> have moved this msi from a standard windows domain GPO, which installs 
> just fine. I just wanted to try to keep all my installs in one spot. 
> From what I can tell in the logs it installs fine with no errors. Has 
> anyone run into this before?

Did you set any properties? Try ALLUSERS=1 - this helps most MSI install the Shortcuts into %ALLUSERSPROFILE% instead of %USERPROFILE%.

Best Regards
        Heiko