This is our setup almost exactly. We have every user log out when they leave and use a script to reboot our Windows machines nightly. This insures that WPKG runs, among other things.
Urs Rau wrote: > > Some background to my question. My problem with regards to different > ways of running and stopping and restarting wpkg service seems to be > mostly centred around the fact that in my environment, (xp pro > workstations connected to linux samba PDC with active network mappings) > I cannot have more than one user credential active with mappings against > the server. So it's a case of one or the other. So if the user has > logged in to the server and has his or her network drives mapped against > the PDC, as automatically done by the network logon script, then I can't > run a scheduled run of 'wpkg.js /synchronize' using different, 'network > - admin - access - privileged', user credentials against the same samba > pdc server. > > So the 'only' way I have found wpkg service working for me is when set > to startup as a service that has specific privileged > network username and password set for the service. But this means > the wpkg.js is not run often enough to pickup changes, unless I also > start interfering more with how often people restart their workstations. -- - Matt Miller - Solutions for Progress 728 South Broad Street Philadelphia, PA 19146 215-701-6108 (v) 215-972-8109 (f) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wpkg-users mailing list wpkg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wpkg-users
