Hmm, does still not work, made an extra share for this, In example the UNC-Path is showed like this <param name='log_file_path' value='\\\\server\\share\\dir' /> Would it be correct using \\server\share\dir ? I made a user wpkg for deployment and logging, does authentication work for logs as well? Thanks in advance, greets mike > -----Ursprüngliche Nachricht----- > Von: Rainer Meier [mailto:r.meier at wpkg.org] > Gesendet: Mittwoch, 28. Januar 2009 20:20 > An: Mike Burgener > Cc: wpkg-users at lists.wpkg.org > Betreff: Re: [wpkg-users] Wpkg-client logging issue > > Hi Mike, > > Mike Burgener wrote: > > <param name='logLevel' value='0xFF' /> > > This is correct. It enables full debug logging within the log file. > > > > <param name='log_file_path' > > > value='\\whale\netlogon\wpkg\logswpkg-[YYYY]-[MM]-[DD]-[HOSTNA ME].log' > > /> > > Seems to be correct too. But you have to make sure that even > an unprivileged user has full write access (guest write > access) to the \\whale\netlogon share and in particular the > wpkg sub-directory. Usually users do not have write-access to > the "netlogon" share. So I propose either to use a dedicated > share where you allow writing for everybody or to log to the > same server where you sore wpkg.js. The second option is nice > because Windows would use the same credentials to write the > log which it is using to load wpkg.js (credentials > configurable within wpkg client). > > For example: > WPKG JS path: > \\server\wpkg\wpkg-server\wpkg.js > > log_file_path > \\server\wpkg\wpkg-log > > So make sure the share is giving full write access to the > "wpkg" share and the user you configured within WPKG client. > Then you might limit the same user to read-only access on > filesystem level in order to make sure users cannot write to > the "wpkg-server" > directory. > > Note: It is absoulutely crucial that you give full write > access to the \\server\wpkg\ share because if you give just > "read" access it's useless to give even full permissions on > filesystem level. > > > > But this seems not to work, no logfile seems to be created, > seems not > > to be a permission issue. > > Right, see above. > > br, > Rainer > > |