I am confused. I am trying to figure out how this is better than using NTNAME. I have been using this for several years to find a logged on user's computer. If the user is logged on more than once, it will only find one computer. I think the solution you are working on has the same problem. If it can find all the computers, then this may be worth it. NTNAME just appears to much easier than using winscl.exe.

At the company I work at we have probably about 140,000 computers, not counting any kind of servers. We probably have about 100 domains. I don't have admin rights to all those domains. I do not have any admin rights to the wins servers. Will this cause any problems using winscl.exe? I also could not find this as a download from Microsoft's site, so I assume that you will have to buy the reskit. Not a problem for me, but something to remember.

I have not been able to test what this thread is currently working on. I am at home recovering from a hernia operation. So I may have missed a point along the way. If this was using some sort of COM method, I probably would have jumped on it. As I said at the begining, I am just trying to understand.

Well, here is some sample code. You could probably wrap this inside wshPipe udf.
code:
$ScriptDir = @CurDir
$UserID = 'Name'
$Who = fnFindUser($UserID)
? 'Error: ' + @Error
? 'Who:   ' + $Who

QUIT 1

FUNCTION fnFindUser($User)
;--- This function will find what computer a person is on.
  DIM $Temp, $Reply, $FindUserError
  $Temp = '%temp%\' + $User + '.tmp'
  DEL $Temp
  SHELL '%Comspec% /C ' + $ScriptDir + '\ntname.exe ' + $User + ' > ' + $Temp
  $Nul = Open (10, $Temp, 2)
  $FindUserError = @Error
  IF $FindUserError = 0
    $fnFindUser = ReadLine (10)
  ENDIF
  $Nul = Close (10)
  DEL $Temp
  EXIT $FindUserError
ENDFUNCTION
_________________________
Kelly