[wpkg-users] A few issue

[Vasaris]

put the wrong path. Does that means, that the client is left in the unsupported state, until is logged on by admin and fixed bad config by hand? Or special script has to be made, to re-deploy on-top?
> 
> More or less (or use psexec, or winexe).
> Same if i.e. you deploy a workstation, but it wasn't joined to a domain - you can't manage it with AD.

Not in this case. That is what has made such confusion for me.

> In other words: do not make tests on real systems and make sure 
> everything works before you deploy it.

Perhaps there was a threshold of experience problem. And not knowing the infrastructure so well.

> > And if not? Beause I had scenario in the beginning, when I put wrong path to the wpkg.js.
> 
> Then you have a chicken and egg problem.
> Even if WPKG Client would read the settings file each time - how would 
> it access a password protected share if you made a typo in a password?

Not in this case, if the settings.xml file is dropped in local file system, as in my case, by external script, which works OK, as it is very simple, compared to WPKG system. That was my mistake.

Perhaps it would be wise to make a change, if wpkginst.exe finds settings.xml in its local directory, it updates registry lockers with this info every time it finds this file. It then can leave or delete it. It would be very simple to "push" changes to the service in case of usual or emergency reconfiguration, and would escape "unsupported" state once and for all. I think, that to "push" such file is much more simple, thant to execute remotelly with psexec (which is known to have version incompatibilieties by itself also!).

If I remembver correctly, some change will be programmed in future releases, that settings.xml will be tried to read on 1st deployment from the directory, where .msi file is located. This is good upgrade, but I think, not sufficient. This is only my 2 cents on the issue.

> >> You can do it as a WPKG package (execute="once").
> >
> > And if I change that to ="always"? Will it update every time?
> 
> Yep. Shouldn't do much harm.
> But You would rather want "once", and upgrade package revision if you made an upgrade.

That is possible also.

Regards,

Andrew.