5 replies
by chris hirst
Without thinking too deep a WINS server would collect IP,s Usernames and NETBIOS names. You may need to do a bit of manipulation with the exported file to get everything together.
Chris
by donalda-m
by joseph moore
I do this very thing on my network for auditing purposes. It is very easy.
In the user logon scripts, you can collect the %USERNAME% and %COMPUTERNAME% variables and direct them to a text file. So, you could simply put this in the scripts:
ECHO %username% -- %computername% >>\\SERVER1\SHARE1\Userlogins.txt
And that will make a text file that looks like this:
JOE -- MYPC1
JO2 -- MYPC2
JO3 -- MYPC3
etc.
Now, in my login scripts, I am adding the date and time the users log in, using the NOW.EXE app from the Resource Kit. I wanted to add some kind of date history, so I would know if someone logged in from a machine they should not have logged in. NOW is a nice app to do this with, since it exports date and time, and acts like the ECHO command. You can download NOW from Microsoft here:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/now-o.asp
(please remove any spaces)
Copy NOW.EXE into the Netlogon share on your PDC and BDCs. So, this is what mylogon scripts all have:
now.exe %username% -- %computername% >>\\SERVER1\SHARE1\Domainuserslogin.txt
And the log file looks like this:
Wed Jan 23 22:58:48 2002 -- JOE -- MYPC1
Wed Jan 23 22:58:48 2002 -- JO2 -- MYPC2
Wed Jan 23 22:58:48 2002 -- JO3 -- MYPC3
etc.
I think the last thing to add is the path to the text file. Make it a path that all users can write a file into, like a public Share directory.
Hope this helps.
by donalda-m
by donalda-m
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending