All Forums >> [Scripting] >> WSH & Client Side VBScript >> Table Does not Exist on searching user name in AD Do you like VisualBasicScript.com? Link to us and help spread the word about our forum. Thanks!
Is there any difference in searching for user account in AD and computer account?
I am using similar queries in my WinPE environment. The search for computer account query works fine while the search for User query comes up with "Table does not exist message". Why?
Similar Queries except: objectCategory = 'Computer' while searching for Computer Name objectCategory = 'User' while searching for User Name
Set ADConnection = CreateObject("ADODB.Connection") Set ADCommand = CreateObject("ADODB.Command") ADConnection.provider = "ADsDSOOBject" ADConnection.Properties("User ID") = "Domain\username" ADConnection.Properties("Password") = "MyPassword" ADConnection.Open "Active Directory Provider" Set ADCommand.ActiveConnection = ADConnection
Her is what I use and it works. Note the ";subtree" at the end of the ldap statement. This will search from the current context through all of it's sub-ou's. Keep in mind that my LDAP query was wrapped by this forum editor but you will likely parse it up and build it as you did for yours.
Set objADOconnADSI = CreateObject("ADODB.Connection") objADOconnADSI.Open "Provider=ADsDSOObject;" Set objCommandADSI = CreateObject("ADODB.Command") objCommandADSI.ActiveConnection = objADOconnADSI objCommandADSI.Properties("Size Limit")= 10000 objCommandADSI.Properties("Page Size")= 10000 objCommandADSI.Properties("Sort on") = "sAMAccountName" objCommandADSI.CommandText = "<LDAP://searchdomain=com,dc=com>;(objectClass=user);sAMAccountName,distinguishedname;subtree" Set objRSADSI = objCommandADSI.Execute
1. Always use & to concatenate strings instead of using + 2. Make sure your ldap path are correct. To search for users in a specific domain, simply include the ou in the ldap path as you would normally do when using getObject.
My query runs fine from my machine (coz I am already logged in the domain). But does not work in the WinPE environment.
The amazing part is that the same query works fine with the same credentials while searching for a specific computer acccount but comes with a "table does not exist" message while searching for Useraccount.
Could there be any possible credentials restrictions setting in AD where my user account is restricted to search or modify users but I am allowed to search computer accounts?
Is there any policy setting of that sort? Coz if there is, then I can forward my issue to the higer admins and then go from there.
Any other thoughts or ways to search for user account in WinPE mode??
Posts: 1804
Score: 12
Joined: 5/15/2003
From: USA
Status: online
are you authenticated to the DC while in PE? Check out http://www.msfn.org/board/index.php , they have a WinPE forum that could possibly provide info on this.
Is'nt it just funny that as soon as I entered DC=DCName in my query that it worked just fine.
Just changed "LDAP://dc=searchdomain,dc=com" to "LDAP://DC=DCName/dc=searchdomain,dc=com" and it worked fine.
But this brings me to the next question. In this specific test case, I have hardcoded the DCname, but can you get the name of the nearest DC in WinPE environment before logging to any domain.
This is what I had tried, but did not work for me.
Set MyDomain = GetObject("LDAP://RootDSE") MyDC = MyDomain.Get("dnsHostName")
Then I tried to use the MyDC variable in the above LDAP search but this did not work in WinPE (works fine from my machine as I am already logged on the domain).
hmm.. Didn't we have this discussion before regarding selecting domains to authenticate if the local machine isn't of the domain ? I thought you already come up with ideas on that.
I've created a vbscript to rename PCs in a cmd-line supplied OU in a 2k3 AD environment. The script works fine if the OU supplied is under the root of the domain, but not if the OU is a subfolder of an OU on the root of the domain. The error I get is the same "Table does not exist" with error code of 80040E37 as in the topic.
It didn't work because when the LDAP path is incorrect. When you specify the path, it has to be the fully qualified path; starting from the very top of the domain hierarchy to the very bottom. So you would need to specify "ou=level 2,ou=level 1,dc=cargohome,dc=com".
Replace:
objCommand.CommandText = "Select Name from 'LDAP://OU=" & strOUin & ",dc=cargohome,dc=com' " _ & "where objectClass='computer'"
Her is what I use and it works. Note the ";subtree" at the end of the ldap statement. This will search from the current context through all of it's sub-ou's. Keep in mind that my LDAP query was wrapped by this forum editor but you will likely parse it up and build it as you did for yours.
Set objADOconnADSI = CreateObject("ADODB.Connection") objADOconnADSI.Open "Provider=ADsDSOObject;" Set objCommandADSI = CreateObject("ADODB.Command") objCommandADSI.ActiveConnection = objADOconnADSI objCommandADSI.Properties("Size Limit")= 10000 objCommandADSI.Properties("Page Size")= 10000 objCommandADSI.Properties("Sort on") = "sAMAccountName" objCommandADSI.CommandText = "<LDAP://searchdomain=com,dc=com>;(objectClass=user);sAMAccountName,distinguishedname;subtree" Set objRSADSI = objCommandADSI.Execute
you can use the tags (without the spaces) which helps with formatting
All Forums >> [Scripting] >> WSH & Client Side VBScript >> Table Does not Exist on searching user name in AD 
Printable Version
Table Does not Exist on searching user name in AD - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread