On windows server 2008 - it works perfectly.

Den torsdag den 2. maj 2013 15.41.35 UTC+2 skrev Klavs Klavsen:
>
> Hi guys,
>
> I'm trying to make puppet install packages on windows.
>
> It will install exe files just fine - but msi files won't be installed. 
> They fail consistently :(
>
> I've tried both having the files on a central directory - and give an UNC 
> path to it, and with a file resource, putting the file in c:\temp\ - they 
> both give the same result upon install:
>
>                         package { "sflow":
>                                 source => $architecture ? {
>                                         'x86' => 
> 'C:\\temp\\hsflowd-win-1.22.2-x86.msi',
>                                         'x64' => 
> '\\\\software01\\autorepo$\\hsflowd-win-1.22.2-x64.msi',
>                                         default => 'unsupported 
> architecture'
>                                 },
>                                 name => $architecture ? {
>                                         'x86' => 'sflow',
>                                         'x64' => 'sflow',
>                                 }
>                         }
>
> If I use urls like:
> 'c:\\temp\\hsflowd-win-1.22.2-x86.msi' - I get Failed to install: The 
> network name cannot be found - after puppet runs: 
> msiexec.exe /qn /norestart /i c:\\temp\hsflowd-win-1.22.2-x86.msi
>
> If I use urls like:
> 'c\:\\temp\\hsflowd-win-1.22.2-x86.msi'
>
> it fails with: Failed to install: Fail on INT 24
>
> Using Puppet-3.1.1 client on Windows Server 2003.
>
> How do you guys install msi's on windows? :(
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to