Hi again, My problems seems to be resolved. For Rainer, its not a bug... My permission denied messages were due to simultaneous file access... When the I was doing wrong deployment packages, sometimes wpkg was idling in background waiting for user interaction wich never happends. In this state, when the scheduled task was run again, it tried to access again the log file and was getting a permission denied error message.
I had another problem : for my testing purposes, my scheduled task was running every 2 minutes on 200 computers. I encountered authentication problems from the fileserver (2043 error id in the security event log) After increasing the scheduled task interval (15 minutes) it has been fixed. Now all is working well. I only need another thing : add a random waiting time before the script tries to install packages. I will post my modifications of the script if someone ask for. Thanks for your help. This wpkg tool is really great. BTW I now also use the wpkg create report tool which is great too. Cheers, Laplaud François ________________________________________ De : wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] De la part de Troy Hamilton Envoyé : jeudi 6 janvier 2011 18:35 À : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account 2011/1/6 LAPLAUD François <lapl...@sdis72.fr> ... All is going well except that I get this error message : [...] Initialized temporary local log file: C:\Windows\TEMP\wpkg-logInit.log Initializing new log file: \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log Failed to open log file: ACCESS DENIED; falling back to local logging: null WPKG 1.1.2 starting... Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. [...] I have checked shares and NTFS rights and they seems correct. I then types the following command : psexec \\pc1007-057 -s cmd /c echo test > \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log And this last command works perfectly (the log file is created... with the text "test" in it) Your echo test does seem to indicate that your rights on the server share are correct, which is kind of puzzling. You might try actually logging into a workstation and running your command: cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug from within a SYSTEM user command prompt (http://wpkg.org/SYSTEM_user_Command_Prompt). I use the same method that you are attempting using beyondexec (http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I don't remember encountering this error. Cheers, Troy ------------------------------------------------------------------------- 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
