[gptalk] Re: Determining Who Has Run a Login Script
- From: "Gray Troutman" <jgraytroutman@xxxxxxxxx>
- To: gptalk@xxxxxxxxxxxxx
- Date: Mon, 22 Oct 2007 13:48:07 -0700
Netlogon is write protected, that was why I suggested a subfolder that you
would give write access to or using a share somewhere else, it really
doesn't make any difference where it goes. As for two users writing at the
same time, this is a matter of milliseconds, and with only about 100 users I
didn't think the chances of that were incredibly high.
On 10/22/07, Jakob H. Heidelberg <jakob@xxxxxxxxxxxxxxx> wrote:
>
> 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> 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.
>
>
>
>
>
>
>
>
>
Other related posts:
