I have a dropbox sync for all packages, so the wpkg root with all xml-files are shared as \\127.0.0.1\wpkg$ (software files are downloaded from a web share)
I'll try to add a delay script and see if that works. XP Home is also lacks taskkill, so I had to copy that from another computer to make sure my packages work as they should. Thank you all! David Petterson <da...@ifm.liu.se> Phone: +46(0)13-28 2617 Systems Administrator Department of Physics, Chemistry and Biology at Linköping University Office: F F202 SE 581 83 Linköping, Sweden On 2011-03-28 13:30, Malte Starostik wrote: > Am Montag, 28. März 2011, 12:53:20 schrieb David Petterson: >>> Did you configure the user/password for the service to use. Can this >>> account access the server? >>> You can try to run cmd via psexec as the same user (SYSTEM?) that WPKG >>> Client runs as and see if you can access the server from that shell. >> >> It uses the same (SYSTEM) user account as on my other computers running >> XP Pro and Windows 7. When I start the service manually it works fine. > > Not sure if this applies to XP Home and if this fix works. In the registry, > under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows > NT\CurrentVersion\Winlogon\ try setting the value of SyncForegroundPolicy to > 1 > (or add it as a REG_DWORD if it doesn't exist). > If that fails, you could maybe delay the WPKG execution by some other means - > a local script to execute before the action wpkg run, a local wrapper script > or just a connect script with a long delay. Anything that runs locally to > waste some time for the network to come up. > > HTH, > Malte ------------------------------------------------------------------------- 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
