Hi Vasaris,
On 26.02.2010 16:51, Vasaris wrote:
> After this, I uploaded settings.xml file to the target workstation, which
> I have preprared and exported from the additional workstation, where WPKG
> client was installed manually. It is as follows:
I hope you also imported the configuration into WPKG client on the second
workstation.
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration><file>\\serveris\KATALOGAS\DOMAIN\DISTRIBUCIJA\WPKG\wpkg.js</file><net-use-machine-account>YES</net-use-machine-account><path-user></path-user><path-password></path-password><exec-user>SYSTEM</exec-user><exec-password></exec-password><parameters>/synchronize
>
> /debug</parameters><silent>YES</silent><pre-action></pre-action><post-action></post-action><show-GUI>YES</show-GUI><logon-delay>3</logon-delay><logon-message-title>WPKG
> Software
> Deployment</logon-message-title><logon-message-logo-picture></logon-message-logo-picture><logon-message-1>WPKG
> is installing applications and applying
> settings...</logon-message-1><logon-message-2>Please wait, don't restart or
> power off your
> computer...</logon-message-2><priority>below-normal</priority><stop-service-after-done>YES</stop-service-after-done><laptop-mode>YES</laptop-mode><server-connecting-method>standard</server-connecting-method><server-connecting-ip>192.168.2.1</server-connecting-ip><server-connecting-timeout>5</
ser
>
> ver-connecting-timeout><server-connecting-script-timeout>3</server-connecting-script-timeout><server-connecting-script-file></server-connecting-script-file><log-file>C:\system\log\wpkg-run.log</log-file><run-on-shutdown>NO</run-on-shutdown><shutdown-delay>10</shutdown-delay><logon-interrupt-password></logon-interrupt-password></configuration>
I see you're not using a path-user setting but instead the machine account. I
personally never tried it but remember that there were some discussions that in
certain cases it does not work properly. Tomasz can comment on this, he knows by
heart I think.
I suggest you to try using a path-user ("DOMAIN\user" notation) and password in
order to use this user to connect to the specified share.
> The log file, created during clien service run, is as follows:
>
> 2010-02-26 17:39:46 -> Starting WPKG on startup
> 2010-02-26 17:39:46 -> Before create shared memory: successfuly done.
> 2010-02-26 17:39:46 -> Create shared memory: successfuly done.
> 2010-02-26 17:39:46 -> Set script security context: successfuly done.
> 2010-02-26 17:39:46 -> Starting script action execution
> 2010-02-26 17:39:48 -> Script action execution done.
> 2010-02-26 17:39:48 -> Script execution: failure. Exit code: 1
> 2010-02-26 17:39:48 -> Working done. Perform cleanup.
> 2010-02-26 17:39:48 -> Cleanup done.
This is a typical scheme shown when WPKG client fails to connect to the network
share hosting wpkg.js.
I see you also added "/debug" to the WPKG parameters. I recommend you to use
"/synchronize" only and control the debug level within config.xml. This will
allow you to change it later without having to re-deploy a configuration update
to your clients.
br,
Rainer
-------------------------------------------------------------------------
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
