However, it does appear to have limitations. You have to hit the server where the user logs in at to get results. You cannot run this from a workstation.

Pinging Alex.. Pinging Shawn.. It should be doable in ADSI, but we are running in mixed-mode until all of our servers/systems are converted over to 2000.

I have created in our Kix script the ability to log the users, but the log gets pretty unwieldy and you have to search in reverse order.

I did find the following.. http://cwashington.netreach.net/depo/view.asp?Index=198&ScriptType=vbscript

DISCLAIMER - This batch script has been around a while, it is not my original work.

code:

---

@echo off
setlocal
if NOT "%1"=="" goto begin
:syntax
@echo Syntax: WhereUAt UserName1 [UserName2 ... UserNameN]
endlocal
goto end
:begin
if "%1"=="" endlocal & goto end
set user=%1
set user=%user:"=%
shift
for /f "Skip=4 Tokens=*" %%i in ('net session') do call   arse "%%i"
goto begin
  arse
set str=%1
set str=%str:"=%
if "%str%"=="The command completed successfully." goto end
for /f "Tokens=*" %%i in ('@echo %%str:~23^,20%%') do set substr=%%i?
if "%substr%"=="ECHO is on.?" goto end
set substr=%substr:  =%
set substr=%substr: ?=%
set substr=%substr:?=%
if /i not "%user%"=="%substr%" goto end
@echo %str%
:end

---

I was able to munge some this together from some code from http://cwashington.netreach.net

code:

---

$DCString = "DOMAIN"
$User = "kdyer"
$DomainObj = GetObject("WinNT://" + $DCString)
$DomainObj.filter = array($User)
For Each $UserObj In $DomainObj
$Name = $UserObj.Name
$Description = $UserObj.Description
$FullName = $UserObj.FullName
$LastLogin = $UserObj.LastLogin
$AuthServer = $DCString
next

---

It would be pretty cool to not only have the workstation ID(s) where the user has logged in at, but time(s) they logged in too.

Thanks for any insight.

- Kent

[ 07 February 2002: Message edited by: kdyer ]

Like Emerial Agasse (sp?) always says,

"I want to take this up another notch!"

I want to know what machine they are logging into without having to trawl through some database or log file. Or not knowing which BDC they are logging into.

Thanks!

- Kent

I have two methods of figuring out where someone is logged in. The first is to look in the WINS db. Fine if the user is only logged on to one PC. The other is to NET SEND a message to the user to call me. Yeah, I know, low tech.

Perhaps you could streamline your log format so that you don't need to reverse search it. If you set it up in an ini format with the username as the key and WriteProfileString("file name", "section", "@UserID", "@WkSta") the log details, it would be a one-liner retrieve.

I know it isn't what you are looking for, but you could setup a ini file in a common location using
writeprofilestring("\\pdc\share\user.log","ByUser","@userid","@Wksta, @date @time")

writeprofilestring("\\pdc\share\user.log","ByComputer","@Wksta","@userid, @date @time")

not elegant, but quick and easy

The filename was something to the effect of:
path\User on computername at time.txt

the script looked something like this:

--------------
$file = @userid + " on " + @wksta + " at " + @time + ".txt"

del $file ; this keeps it current
$fo = open(1,$file,5)
$wl = writeline(1,@logonserver)
$fc = close(1)
-------------

It created a 1k file and it could be sorted on filename or date in explorer. It wouldn't tell whether they were logged in currently, but it would tell from what last computer they were logged on from.

hope this helps?

The PSLoggedOn util is OK until you hit a Linux box and then it really dogs.

I am already writing to a log. We have introduced a secondary domain. It would be cool to not only query the DC you login to, but capture the machine you login at..

It seems like I am asking the impossible. I am able to get the Last Logged in time, etc. However, I want to get the machine name. Even if I setup to start looping though our 30+ DCs, it would take a long time to do this.

Sorry...

- Kent

I keep a hidden "login.log" in the root of each users home share which records their workstation (@WKSTA), login server (@LSERVER), Citrix client name, thick/thin client type, date and times as well as all the debug information from all the bits of the login scripts that are executed.

As an administrator I just check the log file in the users' home directory for a history of their logins.

The other suggestions are based on your comment RE: parsing a flat log file.

Sorry we're no closer to your goal, but at least there's some good ideas floating around and at least this thread gets bumped back to the top.

krabourn

[ 08 February 2002: Message edited by: krabourn ]

You da man..

Thanks!

- Kent

Now all we need is someone to go through the source code and make a COM object out of it. At least I wish I had something like that.

krabourn

It may not be elegant or a good way to do this, but with the C code included, we maybe able to parse the information into a logical script.

- Kent

For the moment, as i've just drop a look into this, here are what i'm thinking about :
ADsearch UDF in UDF section to start.
ADsearchpanel sample provided with KiXGUI. get a look to this link (it's completely stand alone)
and the user and workstation ADs properties from MSDN (seems the User.LoginWorkstations property will do the job)

Also, never forget Dynamic object (we have the session object using WinNT:// which look promising)

I'll see this more closer this WE if i can. Let me know if you found something