[wpkg-users] A few issue

[Vasaris]

> > You mean, to test out? I would gladly help, because I am interested in support of AD/GP way of the WPKG service-client deployment.
> 
> Sponsor, like in $$$.

Depends how much? ;-)

> Or donate your time and write a fix yourself.

as .msi file is built every time, I have to know, what tools are used for its building. Or maybe only the first .msi file was build by some tools, and all later additions are done by modifying it by hand with tool like ORCA.

> > Yes, I have found that already with Registry Monitor. But I beg my pardon, how may I change these settings on clients, to which they there already deployed, for example if they fail to satisfy my deplyment config?
> 
> http://wpkg.org/WPKG#Changing_WPKG_Client_settings

OK, I understand that. But what happens, if for example, I make config error on the first depplyment, and incorrect settings go into registry secure lockers. Then, for example, when WPKG service is run, it does not find wpkg.js, because I 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?

> You can do it manually, too.
> 
> But if you have more than one PC, you can do it using command line.
> 
> http://wpkg.org/WPKG#Changing_WPKG_Client_settings

It is the decision in any case, but I do not see any value of such decision.

> > I have only added on property - SETTINGSFILE, pointing to the local location with settings.xml. I did not even think, that settings.xml is not read every time, when service runs.
> 
> So, deployment should succeed if the file was there _before_ installing WPKG Client.

And if not? Beause I had scenario in the beginning, when I put wrong path to the wpkg.js.


> You can do it as a WPKG package (execute="once").

And if I change that to ="always"? Will it update every time?

But this does not solve first-bad-settings-deployment scenario in any case, would it?

Regards,

Andrew.