Unsolved
This post is more than 5 years old
1 Rookie
•
122 Posts
0
796
November 24th, 2009 08:00
Software Distribution, anybody working with this, experience?
Hello,
since NetWorker 7.4 I tried several times to use this feature.
I was able to create a depot, add packages, under good circumstances I was successful inventorying some clients.
But it was never stable (I did not achiev reproducible behavior, sometime it worked, sometime it stuck, often was very slow)
With 7.5 no difference
With 7.6 even bad results: Could not add x86 Windows package (missing file inst_connectemc expected due to meta-file)
Could not inventory clients (seems to be bad usage of UDP, some clients sometime working, sometime not)
Trying to update two different Windows NetWorker (one XP, one W2K3, both with 7.5.1) to 7.6 did only uninstall old version, but did not install new version.
I monitored these clients with taskmanager, saw the started installer process, starting two childs, but at the end one process remain, NetWorker was uninstalled and no client installed anymore.
Because of so many different bad experience (slow, not stable, not working) I would now give up on this if nobody is here with good results on using this feature, no matter if NMC wizzard or nsrpush command line.
BTW: the command reference of 7.6 loaded yesterday from powerlink has the beta mark on the page for nsrpush, may be it is not a official feature?


psoni1
41 Posts
1
November 24th, 2009 08:00
I had the same experience while upgrading NW to 7.5.1.x.
FYI,
http://nsrd.wordpress.com/2009/08/05/using-the-networker-software-distribution-functionality/
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 24th, 2009 10:00
Funny enough, GUI upgrade (didn't try CLI) where Windows client gets uninstalled, but new one does not get installed is something I have seen too (not sure was it with 7.4.x or 7.5.x, but I believe it was 7.4.3 or 7.4.4 client). It's a nice idea, but still needs some work I guess (and it is official).
We use HPSA to install packages across our landscape thus no need for application based update procedures.