- From: "Julian C. Dunn" <
>
- To: "
" <
>
- Subject: [chef] Re: RE: Re: Silent installations via Chef in Windows
- Date: Wed, 18 Jun 2014 12:08:44 -0700
On Wed, Jun 18, 2014 at 6:40 AM, Kapil Shardha
<
>
wrote:
>
As per the documentation
>
http://docs.opscode.com/resource_windows_package.html , the new
>
windows_package
>
(built-in) resource seems to lack some attributes, like "options", that we
>
used to have before from windows cookbook.
>
This attribute was used to pass in command-line arguments, such as "/qn"
>
for silent installs for MSIs that allow it. Any
>
idea on how to pass such arguments using this new built-in resource? I did
>
not have much success with using "package"
>
resource either, though I mentioned the windows provider in "provider"
>
attribute. Also, is there a way to still use this
>
resource from windows cookbook? (something like "include_recipe 'windows'"
>
in recipe perhaps?)
There is still an 'options' parameter that you can set to whatever
extra flags you want msiexec to use. Looks like it is missing from the
documentation; I'll have that corrected.
And yes, you can still use the old windows_package provider from the
cookbook. Depending on it in metadata in your cookbook will override
the provider in core and allow you to install packages the old way,
plus supports Inno, Installshield, etc. that we haven't gotten around
to adding to core yet.
BTW, I have had lots of problems with msiexec generally (outside of
Chef) and UAC. If you try to install an MSI using msiexec from a
package that resides in a UAC-protected directory (example:
C:\Users\jdunn\Downloads), it will silently fail and even /l* doesn't
log anything. :-(
- Julian
--
[ Julian C. Dunn
<
>
* Sorry, I'm ]
[ WWW:
http://www.aquezada.com/staff/julian * only Web 1.0 ]
[
gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
Archive powered by MHonArc 2.6.16.