[wpkg-users] A few issue

[Tomasz Chmielewski]

On 02.03.2010 16:47, Vasaris wrote:
> 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?

So how do you join a workstation to a domain (say, it's computer 
password expired as it was off really long, you accidentally removed it 
from AD, and so on), without either logging into it or starting a script 
on it remotely?

This is the same situation here.


(...)


> 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!).

Yep, could be useful indeed.


-- 
Tomasz Chmielewski
http://wpkg.org