First, update to the latest SVN version. Next ensure that the audit.vbs script you are running is the version from the SVN.
Run the script from a location where the users CAN change the log file (call the script from a batch file, but call it on a share where the script can write its logs when run as the user logging in and you should have no trouble).
Finally if you are still struggling, you can modify the script .
Change this section, particularly, fix the path rather then using the variables. The downside of this method is that you must re-modify the script every time a new version is released.
[code]
' Find out the name of this script, usually audit.vbs but it depends where we were called form.
full_script_name = WScript.ScriptFullName
' Strip off the .vbs and the path, so we can create files with the same suffix.
' No point in creating or overwriting audit.config if we aren't called audit.vbs
script_prefix = Left(full_script_name,(InStrRev(full_script_name,".vbs")-1))
script_prefix = Right(script_prefix,(len(script_prefix) - (InStrRev(WScript.ScriptFullName,"\"))))
' We also need the Path
sScriptPath=Left(WScript.ScriptFullName, InStrRev(WScript.ScriptFullName,"\"))
this_config = sScriptPath & script_prefix & ".config"
'this_config = "audit.config"
this_audit_log = sScriptPath & script_prefix & "_log.csv"
' keep_audit_log = "y"
'
' This takes no account of the command line switches added to a forked version, but in principal
' The logic should be...
' look for audit.config and use that, if it doesn't exist, grab it from
' the web server, if we cant do that, then use the internal defaults.
' Finally modify the defaults depending on any command line switches
'
'
' First check to see if we have no config file, if so lets see if we can grab one from the server
'
[/code]
What you change it to depends on where you want the log files and config to live.
BTW Was your post translated by Google by any chance?