I'm sure this is a simple question but I'm having a reall brain fade today (it is St Pat's day [:'(])

I want to create a MSI package (as I want to push out it out via our deployment tools) that runs two command lines.

"\\source01\PACKAGING\Source\PDFFactoryPro2.5\Files\setup32.exe /kernelmode /quiet"
xcopy \\source01\PACKAGING\Source\PDFFactoryPro2.5\Files\FppLicense2.ini %windir%\system32 /C /Y

Now before anyone suggest I should see if there's a MSI in the setup32.exe there's not (that would be too nice and easy) and before anyone suggests snapshotting/install monitoring the setup32.exe that isn't a option as the package installs printers (and creates a service) therefore it doesn't capture correctly (The software is like Adobe Distiller, in that you print to it and it creates a PDF)

Can someone please help
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


Custom Action? Can´t you create a custom action that runs the setup.exe in the msi?
Or in your SoftwareDistribution tool create a separate setup.exe installation package?

Answered 03/17/2006 by: fetgor
Senior Purple Belt

Please log in to comment
"\\source01\PACKAGING\Source\PDFFactoryPro2.5\Files\setup32.exe /kernelmode /quiet"

You need a Custom Action here, maybe a
Action: <name of action>
Type: 2 (msidbCustomActionTypeExe + msidbCustomActionTypeBinaryData), possible 1026 (msidbCustomActionTypeExe + msidbCustomActionTypeBinaryData + msidbCustomActionTypeInScript)
Source: <binary table, name column>
Target: /kernelmode /quiet

As for the ini-file, I would recommend just putting it in the MSI as a normal file.
Answered 03/17/2006 by: sikkert
Orange Senior Belt

Please log in to comment