MSI to execute a file
Ok i'm struggling a bit here...
I'm trying to create a package around Visio 2007. So far i've run the OCT to create the msp file and placed this in the Updates folder. I'm now trying to create an msi which simply executes a batch file i've created which in turn executes the setup.exe with added commands (afaik you can't just add the command you want to run to an msi file!!?) but am not having a lot of luck. I've created a blank msi and added a CustomAction called "SetupExecute", I then added this action to the InstallExecuteSequence table with a condition of NOT Installed AND (REMOVE<>"ALL") and Sequence number 50.
BTW I only have WinINSTALL LE 2003/ORCA and don't want to copy the file over first, just run it from the package directory
When running this msi nothing really happens!! Any ideas?
I'm trying to create a package around Visio 2007. So far i've run the OCT to create the msp file and placed this in the Updates folder. I'm now trying to create an msi which simply executes a batch file i've created which in turn executes the setup.exe with added commands (afaik you can't just add the command you want to run to an msi file!!?) but am not having a lot of luck. I've created a blank msi and added a CustomAction called "SetupExecute", I then added this action to the InstallExecuteSequence table with a condition of NOT Installed AND (REMOVE<>"ALL") and Sequence number 50.
BTW I only have WinINSTALL LE 2003/ORCA and don't want to copy the file over first, just run it from the package directory
When running this msi nothing really happens!! Any ideas?
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
The point with Office 2007 is that you don't execute any of the MSIs directly. You need to use Setup.EXE and pass the appropriate arguments to it.
Posted by:
jcarri06
14 years ago
Also, keep in mind that if you have MSI_1 run, and it calls a batch file, and that batch file calls setup.exe, and that calls MSI_2, it will FAIL since "Another installation is currently running".
Basically, you can't use 1 msi to call another. If you build your MSP correctly, you shouldnt' ahve to wrap it around anything...
Basically, you can't use 1 msi to call another. If you build your MSP correctly, you shouldnt' ahve to wrap it around anything...
Posted by:
reds4eva
14 years ago
ORIGINAL: jcarri06
Also, keep in mind that if you have MSI_1 run, and it calls a batch file, and that batch file calls setup.exe, and that calls MSI_2, it will FAIL since "Another installation is currently running".
Basically, you can't use 1 msi to call another. If you build your MSP correctly, you shouldnt' ahve to wrap it around anything...
Basically everything you have said is wrong.
jshand, you need to search APPDEPLOY, there is a billion pages of info on how to create an MSI wrapper, and how to use that wrapper to deploy Office 2007.
Posted by:
jcarri06
14 years ago
ORIGINAL: reds4eva
Basically everything you have said is wrong.
Wow...really?? I could have sworn I was never able to call another msi from an already running msi...Gonna have to look into this once more. Thx.
Posted by:
anonymous_9363
14 years ago
It depends on where in the sequence you put the CA. If you *must* nest, the best place is in ExecuteImmediate after the InstallFinalize action. MS now states - and most would agree - that nested MSIs are A Bad Thing. The principal issues are that of patching and uninstall. Chaining MSIs is available in WI v4.5, however, just to cloud the issue!
Posted by:
jshand
14 years ago
Cheers for the replies guys. I've managed to deploy this via the setup.exe and command line arguments now so no need for an msi. The information is appreciated though [;)]
Posted by:
nheim
14 years ago
Hi Jamie,
don't know what you are trying to achieve here...
I assume, you want to install it with a GPO.
If this is the case, MS has done it for you (well sort of..)
If you install it standalone, you install it with this MSI:
\VISPRO.WW\VISPROWW.MSI
If its done with O2k7 thogether, use this MSI:
\Enterprise.WW\EnterpriseWW.msi
See: http://technet.microsoft.com/en-us/library/cc179214.aspx
Regards, Nick
don't know what you are trying to achieve here...
I assume, you want to install it with a GPO.
If this is the case, MS has done it for you (well sort of..)
If you install it standalone, you install it with this MSI:
\VISPRO.WW\VISPROWW.MSI
If its done with O2k7 thogether, use this MSI:
\Enterprise.WW\EnterpriseWW.msi
See: http://technet.microsoft.com/en-us/library/cc179214.aspx
Regards, Nick
Posted by:
anonymous_9363
14 years ago
The problem is, though, Nick, that you can't now use transforms. You must use patches and, guess what? When GPO'd, the patches are ignored. MS says to use CONFIG.XML to customise. Great! Except you can't do anything really useful with that, other than choose features.
Posted by:
jshand
14 years ago
I have an RM network here so usually need an msi to distribute any applications out. I initially tried just installing from the VISPROWW.msi file but it wasn't having it and also there was no way to customize Visio to my establishment but as i mentioned i've managed to roll this out now using the correct method of calling on the setup.exe with arguments.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.