On 02.03.2010 16:12, Vasaris wrote:
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?
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.
Or deploy a remote system, but leave remote access off. And so on.
In other words: do not make tests on real systems and make sure
everything works before you deploy it.
(...)
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.
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?
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.
--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
