[gptalk] Re: Determining Who Has Run a Login Script

Whichever share you use, there's no point doing it in the startup script
- you haven't got a user logged on then so at best, you'll get something
saying that "computer1" is logged on to "computer1" which is probably
not what you need :-)

We've used something similar to Ronald's method in the past - you can
always be sure that there aren't two users logging on simultaneously to
any one machine so it all works nicely.

Steve

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Nelson, Jamie R Contr 72 CS/SCBAF
Sent: 22 October 2007 21:45
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining Who Has Run a Login Script

SYSTEM can access the network as long as you grant permissions to the
builtin "Domain Computers" group or the individual computer object.

However, like Jakob said, don't use NETLOGON. Use a different share
somewhere else.

Regards,
Jamie Nelson

-----Original Message-----
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.

 

 

 

 

***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
by logging into the freelists.org Web interface. Archives for the list
are available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************

Other related posts: