I am new to packages and have never done it before.

I want to push out an application that is already in .MSI format. But -
When you double click the .MSI format it says that

" 1: This installation cannot be run by directly launching the .MSI
package. You must run setup.exe."

If you run the setup.exe it works fine. I think its something to do with
something called InstallScript, im not sure, the software manufacturer
has created the MSI. Its an industry specific product you wont have
heard of it.

We have recreated the package by snap shot and then have an additional
problem. The install folder needs to have modify permissions for all
users, I have been told that I need to create a custom action. I don't
know how to add the custom action to the end of the .MSI.

Initially we had a consultant company in to package the original version
of the software - they seem to have created an .MST and it works fine.
The .MSI seems to be untouched as when you double click it you get the
same error message as above, but with the .MST it works fine. They seem
to have a custom action using a secedit.exe command, but how ever many
times I try to duplicate it, it doesn't work.

Please can you advise what is the best direction for me to take, either
some help or a training course.
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
Well there are a couple options here. First off read this:

http://itninja.com/blog/view/7.8-gigabyte-size-limit-in-nt''s-ntfs4

Now there are a couple options for not going this route and maybe doing a snapshot like you have done.

1. During the snapshot, install into a folder other than Program files (c:\prg for example) this way the newly created program folder will have full control permissions for the everyone group. This saves having to get into a custom Action.

2. It appears that the consultant has done this already and put the custom action in calling secedit or some other utility (I would have used an ACL utility). You can assign this via group policy and in the modifications tab specify the MST (transform file). Or you can also use the command line and specify to use the MST file in it.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/command_line_options.asp

Good luck.
Answered 10/29/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
Try the following command from a command line in dos or from Start/Run command line:

D:\SETUP.EXE /A INSTALL.MSI


Key:
D:\ (being the source CD)

I hope is not too late.
Answered 11/12/2004 by: mikepackager
Yellow Belt

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