[wpkg-users] Silent installs of MSI or exe files.

[David Christensen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Malte Starostik wrote:
> Am Montag, 10. August 2009 23:28:07 schrieb David Christensen:
>> Malte Starostik wrote:
>>> Am Montag, 10. August 2009 21:40:15 schrieb David Christensen:
>>>> Charles Gargent wrote:
>>>>>> Is anyone familiar with modifying msi files by way of mst to do silent
>>>>>> installs, is this even possible?
>>> [...]
>>>
>>>>> Besides, anything you can run on the command line can be run in WPKG
>>>>> (if there are many command lines to run putting them in a batch file
>>>>> is a good idea.
>>>> I started investigating the mst option, but was unsure if that option
>>>> would work via WPKG.  With the issue at hand I need to include a new ini
>>>> file that contains site specific configuration options.  I downloaded
>>>> orca and created an mst, but wasn't clear on how to include the ini as
>>>> part of the mst or even what needed to be the final output after
>>>> everything  was changed.  This is about the time I started looking at
>>>> autoit, but based on your response it doesn't look like a valid
>>>> solution.
>>>>
>>>> I'd like to try toe msi/mst route but I have limited knowledge of this
>>>> area, any pointers on where to look for howtos etc would be appreciated.
>>> Hi David,
>>>
>>> you might have a look at this one: http://www.instedit.com/ it's IMHO
>>> quite nicer to handle than orca.  Then you just use sth. along the lines
>>> of msiexec /i path\to\setup.msi TRANSFORMS=path\to\transform.mst /qn
>>> /norestart as install command.  Alternatively, if it's only about
>>> dropping an additional file into the target system, you might as well
>>> install the msi without transform and add another command like
>>> %COMSPEC% /c copy /y path\to\config.ini path\to\destination\
>>>
>>> HTH,
>>> Malte
>>> -------------------------------------------------------------------------
>>> wpkg-users mailing list archives >>
>>> http://lists.wpkg.org/pipermail/wpkg-users/
>>> _______________________________________________
>>> wpkg-users mailing list
>>> wpkg-users at lists.wpkg.org
>>> http://lists.wpkg.org/mailman/listinfo/wpkg-users
>> Malte,
>>
>> Thanks for the info, based on my current need I will take your advice
>> and install the msi without the transform and copy the ini file over.
>> Is the %COMSPEC% command you provided intended to be appended to the
>> existing entry in the packages.xml file?
> 
> it goes like:
> <package id='myapp' name='MyApp' revision='20090810'>
>   <check .../>
>   <install cmd='msiexec /i %SOFTWARE%\MyApp.msi /qn /norestart'>
>     <exit code='3010' reboot='postponed'/>
>   </install>
>   <install cmd='%COMSPEC% /c %SOFTWARE%\MyAppini "%ProgramFiles%\MyApp\'/>
> </package>
> 
> where %COMSPEC% expands to the fully qualified name of cmd.exe on NT based 
> Windows versions and command.com on DOS based ones.
> 
> All commands given in <install/> tags are run sequentially as long as they 
> succeed and don't indicate an immediate reboot.  If you need more than a few 
> commands or more complex ones, you can also put them into a separate .cmd file 
> and include a command to call that one from packages.xml.
> 
> Cheers,
> Malte

Based on the syntax it would appear the target file needs to be on the
local host, is it possible to store the target file on a network share
like the same one the msi is stored on and still use %COMSPEC% ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkqAmFEACgkQ5B+8XEnAvqsx3QCgh71+yMyQeD80POczL+N9x4VO
mZsAn1sOu8a0Q//UKhA0VjG4lmILL9YP
=QENF
-----END PGP SIGNATURE-----