On Tue, May 14, 2013 at 7:27 AM, Klavs Klavsen <[email protected]> wrote:
> I switched to the winxp edition - and sflow now installs perfectly. > > I edited path to NSCP - to be EXACTLY the same as I use for sflow agent > msi - and now it works too - atleast on win2003/x86 machines. Haven't had > time to test on win2008. > > One odd thing - I'musing a path like this - which works: > "\\\\my-software01\\autorepo\$\\NSCP-0.4.0.183-Win32.msi" I've updated #20534 with more information. msiexec is fragile that way, as is cmd.exe. > However, this path works fine NSCP - the exact same - for the sflow agent > ONLY works for windows servers on same Domain as the my-software01 machine. > The machine on this other domain - can easily open > \\my-software01\autorepo$ in a file explorer on the machine - but msieexec > says it can't find the network path.. If you are running msiexec directly from the command line, and it can't connect, but file explorer can, then it sounds like an issue with msiexec. Are you using DFS perhaps? Or perhaps an older version of windows installer? > > > It seems a pretty fragile package distribution mechanism :( > You should check out http://chocolatey.org, it's like apt-get for windows. There's a puppet chocolatey package provider here: https://github.com/chocolatey/puppet-chocolatey Josh -- Josh Cooper Developer, Puppet Labs *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **Register now and take advantage of the Early Bird discount - save 25%!* -- 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.
