Find OU from username 3

[L0stInSpace]

How can I find a users OU based on username?

 

[onpnt]

OU ??

can you please get a bit more detailed. with the thousands of abbreviations M$ comes up with daily I can't keep up in my age.

_____________________________________________________________________

_{Hakuna matata!!}

 

[mark01]

OU = Organizational Unit

 

[quicksaab]

I hope one would know what an OU is....anyway, each OU fires a different login script, so - if you reference on the file name of the login script. Not sure what you are trying to do.....

q

 

[onpnt]

I hope one would know what an OU is
Ya, I hope one would know what a Organizational Unit is to!

OU could mean about fifty different things. I guess after replying to thousands of threads and running around in circles trying to figure out with the lack of details in a question are by readin gminds I like to ask first to clarify. be it nicely or not!

_____________________________________________________________________

_{Hakuna matata!!}

 

[L0stInSpace]

OU = Organizational Unit in Active Directory.

I'm trying to write a VBscript login script that will make decisions based on a users OU. I understand that I could run different scripts for differnt OU's, but that is not what I am trying to do.

Sorry about the confussion. This is my first posting here

 

[cmwoodman]

It looks like you are getting the run around. Here is a thread where someone has a script that is returing the OU.

thread329-727405

It might help you out some.

 

[zmann]

L0stInSpace,

You could also implement a chained If--Then--ElseIf statement in your script. ie,

If OU=Marketing Then
LoginScript=Marketlogin.vbs
ElseIf OU=Sales Then
LoginScript=Saleslogin.vbs
End If

Don't know if it is what your after but it might help.

Z

 

[woodhead]

In a Nutshell, it is easier to use the WinNT to locate the user then get the LDAP info.
The script below uses the Login Name (i.e. kbwood to get the information - Namely ASD path. This script will ask for the name. If you do not give a name, it will write ALL ids to a file inthe C:\temp directory.
You must be an admin for it to work.

'gets AD users, checks e-mail Firstname and Last Name, OU location Puts results in a file
'requires Domain admin priviledges to run
' Check to see if there is a command-line argument
Set objArguments = WScript.Arguments
dim strSn
dim strGivenName
dim strNewEmail
dim strCurrentEMail
dim strAsk
dim strWhere
dim strToGet
dim oUser
dim fso
dim file1
Const ForReading = 1, ForWriting = 2, ForAppending = 8
set fso = CreateObject("Scripting.FileSystemObject&quot
set file1 = fspenTextFile("C:\Temp\usersandOU.txt", ForAppending, True)
If (objArguments.Count = 1) Then

' Treat the command-line argument as the name to filter on
strPerson = objArguments(0)

Else
' Check to see if script is running in console
strExecutable = LCase(WScript.Fullname)

If InStr(strExecutable, "cscript&quot > 0 Then

' Prompt user for name
WScript.StdOut.Write "Logon Name to lookup (enter * for all):"

' Use Standard in to get name
strPerson = WScript.StdIn.ReadLine
Else
' GUI mode, use InputBox to prompt user
strPerson = InputBox("Enter the logon name of the person to lookup" & vbCrLf & "(Use * to search for all people)", "Lookup Location in Active Directory&quot
End If

End If

If strPerson <> &quot;&quot; Then
' Input box is not empty and Cancel button was not clicked

' Build the query string
' Active Directory OLEDB Provider format has four parts separated by semi-colons:
' Root: which is the starting point for the search
' Filter: conditions to search on, using RFC 2254 format
' Attributes: attributes to return
' Scope: base, onelevel or subtree for entire directory partition

' Specify the search base.
' We'll use the global catalog for performance reasons since the
' Name and Telephone number attributes are available from the GC

' First, need to discover the local global catalog server
Set objADsRootDSE = GetObject(&quot;GC://RootDSE&quot

' Form an ADsPath string to the DN of the root of the Active Directory forest
strADsPath = &quot;GC://&quot; & objADsRootDSE.Get(&quot;rootDomainNamingContext&quot

' Wrap the ADsPath with angle brackets to form the base string
strBase = &quot;<&quot; & strADsPath & &quot;>&quot;

' Release the ADSI object, no longer needed
Set objADsRootDSE = Nothing

' Specify the LDAP filter
' First, indicate the category of objects to be searched (all people, not just users)
strObjects = &quot;(objectCategory=person)&quot;

' If user enters &quot;*&quot;, then filter on all people
If (strPerson = &quot;*&quot Then
strName = &quot;(sAMAccountName=*)&quot;
Else
strName = &quot;(sAMAccountName=&quot; & strPerson & &quot;*)&quot;
End If

' Add the two filters together
strFilter = &quot;(&&quot; & strObjects & strName & &quot&quot;




' Set the attributes we want the recordset to contain
' We're interested in the common name and telephone number
'strAttributes = &quot;cn,Mail,sn,givenName&quot;
strAttributes = &quot;sAMAccountName,Mail,sn,givenName,ADsPath&quot;
strWhere=&quot;ADsPath&quot;
strSn = &quot;sn&quot;
strGivenName = &quot;givenName&quot;
' Specify the scope (base, onelevel, subtree)
strScope = &quot;subtree&quot;

' Create ADO connection using the ADSI OLE DB provider
Set objADOConnection = CreateObject(&quot;ADODB.Connection&quot
objADOConnection.Open &quot;Provider=ADsDSOObject;&quot;

' Create ADO commmand object and associate it with the connection
Set objADOCommand = CreateObject(&quot;ADODB.Command&quot
objADOCommand.ActiveConnection = objADOConnection

' Create the command string using the four parts
objADOCommand.CommandText = strBase & &quot;;&quot; & strFilter & &quot;;&quot; & strAttributes & &quot;;&quot; & strScope

' Set the number of records in the recordset logical page
'objADOCommand.Properties(&quot;Page Size&quot = 20

' Set the maximum result size
objADOCommand.Properties(&quot;Size Limit&quot = 2000

' Sort the results based on the cn attribute
objADOCommand.Properties(&quot;Sort On&quot = &quot;sAMAccountName&quot;

' Execute the query for the user in the directory
Set objADORecordset = objADOCommand.Execute

If objADORecordset.EOF Then
WScript.Echo &quot;No records were found.&quot;
Else
' Loop through all the returned records
While Not objADORecordset.EOF

' Display the row using the selected fields
strDisplayLine = objADORecordset.Fields(&quot;sAMAccountName&quot & vbTab & vbTab
strWho = objADORecordset.Fields(&quot;sAMAccountName&quot
strWhere = objADORecordset.Fields(&quot;ADsPath&quot
' Check to see if EMail field is null
If IsNull(objADORecordset.Fields(&quot;Mail&quot) Then
strDisplayLine = strDisplayLine & &quot;(No E-Mail Address Listed)&quot;
strCurrentEMail = &quot;(No E-Mail Address Listed)&quot;
Else
' Retrieve EMail address and add to line
strDisplayLine = strDisplayLine & objADORecordset.Fields(&quot;Mail&quot
strCurrentEMail = objADORecordset.Fields(&quot;Mail&quot
End If

'end if

' Display the line

WScript.Echo strDisplayLine
'file1.writeline(strDisplayLine & &quot; &quot; & strWhere)
' Advance to the next record
objADORecordset.MoveNext

Wend
End If
file1.close
' Close the ADO connection
msgbox &quot;The results are in C:\Temp\usersandOU.txt&quot;
objADOConnection.Close
End If

 

[MisterNiceGuy]

I use Ldap binding for virtually everything. Assuming you are binding to the user object, then the immediate parent of the user can be determined fairly easily. i.e.

'Bind to Active Directory System Info
Set AdsSysteminfo = CreateObject(&quot;adsysteminfo&quot
'Bind to the currently logged on user.
Set UserObj= Getobject(&quot;LDAP://&quot; & adsSysteminfo.UserName)

'display the Ldap Path of the OU the user is in. (it's parent)
Msgbox UserObj.Parent

'bind to the OU.
Set OUobj=GetObject(UserObj.Parent)

'display the name of the OU. after removing the &quot;OU=&quot;
msgbox replace(OUobj.name,&quot;OU=&quot;,&quot;&quot

 

[cmwoodman]

Woodhead,

I really like this script you posted. I had some questions about it though, i am only able to return the first 2000 users in my domain. i changed the 'size limit' variable from 2000 to 5000 (even 50000) and i still only returned the first 2000, i also changed the 'page size' in relation to what i change the first and i got the same results. is this some sort of limitation to what the global catalog can return or am i just missing something obvious?

oh, here is a star for you, thanks.

 

[woodhead]

I remembr running into the 2000 record limit - for most of my clients this was not an issue. Off hand I do not remember my solution.

Try commenting out both the line:

objADOCommand.Properties(&quot;Size Limit&quot = 2000

so it looks like: (notice the single quote)
'objADOCommand.Properties(&quot;Size Limit&quot = 2000

You may notice the Page size already was commented out.
I 'think' this is what I did. I pulled this script out of my script library when I read your question. I remembered 'Hey - I had to do this once