Good point. You can have file locking and dropped writes to the log file. In the past I've had each instance of an executed script create a log file (dynamically named after the computer the instance ran on) in a directory. So for example you have Directory A, and in Directory A you have log files for Computer1, Computer2, and Computer2. Then I ran a second script from my workstation. This script parsed the text files in the directory and consolidated the results into a text file or excel spreadsheet. It was an extra step, but it guaranteed no loss of data from file locking. From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Jakob H. Heidelberg Sent: Monday, October 22, 2007 3:40 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Determining Who Has Run a Login Script SYSTEM wouldn't be able to access the network I guess - NETLOGON can be "opened" with NTFS rights, but I wouldn't recommend this of course. Use another share somewhere! The ECHO method is OK (and other writes to flat files), but exactly WHAT happens when 2 users try to write to the file at once - write failure for one of them is my guess. Best regards /Jakob From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of EIS Lists Sent: 22. oktober 2007 22:32 To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Determining Who Has Run a Login Script This is what I was thinking. However, I believe NETLOGON is write protected, no? If it runs as a Startup (rather than a login) script, it runs under the System account, right? That should be able to write to netlogon. From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Gray Troutman Sent: Monday, October 22, 2007 1:19 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Determining Who Has Run a Login Script oops...forgot a space...that should be: echo %username% >> \\YourDC\NETLOGON\ScriptLogs\WhoHasRunTheScript.log On 10/22/07, Gray Troutman <jgraytroutman@xxxxxxxxx> wrote: Just curious, but wouldn't it be easiest to add this line to the start of the login script: echo%username% >> \\YourDC\NETLOGON\ScriptLogs\WhoHasRunTheScript.log (it doesn't have to be a subfolder of netlogon, just a folder which you give everyone write capabilities to) On 10/22/07, Martin Hugo < Martin_Hugo@xxxxxxxx <mailto:Martin_Hugo@xxxxxxxx> > wrote: You could fire the script with a simple batchfile. The first line of the batchfile could check for the existence of a text file on the client, if the file is present, just exit the batchfile doing nothing, if not, run the script and create the textfile that the first line checks for. You could further have it append the <computername> to another text file on a server somewhere which would then list all the machines that it fires the script on. Martin T. Hugo Network Administrator Hilliard City Schools Tel: 614-921-7102 Martin_Hugo@xxxxxxxx gptalk@xxxxxxxxxxxxx writes: Hi - We want to run a little logon script (or maybe startup script) to install fonts and make a reg change. Is there an easy way to "log" who has run this script? I thought about writing a line to a shared text file but have not had much luck with that. This would affect about 100 computers. Thanks. --------------------------------------------------------------------------------------------------------- This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. ---------------------------------------------------------------------------------------------------------