Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
ADSI
 |
- !!!NEWSFLASH!!!
- !Reading List
- 1063 Object Doesnt Exist
- 1068 Error trying to duplicate user groups
- 1073 Cannot Contact the LDAP Server
- 234 Unable to Parse ADSI Path on WinPE
- 275 Search Return Too Many Object Paths
- Active Directory - Force Replication
- ACTIVEDS.dll could not be Found in the Specified Path
- AD Account Creation Date
- AD Event Monitoring Issues
- AD Locked Account Problem
- AD MachineRole Property
- AD OU Membership
- AD Password Expires Date
- Add a user to a OU
- Add more then one Othermailbox to Account
- Add New Mail Account to users that do not have one
- Adding a Machine to an AD Domain
- Adding a workstation (NT4 and W2k) to the domain
- Adding a Workstation to AD in Correct OU
- Adding NT4 Global Group to a Windows 2000 Domain Local Group
- ADSI and COM
- ADSI Function Equivalent to wntMemberSet
- ADSI IIS related bug in Win2k3 sp1
- ADSI Scriptomatic
- ADSI Special Characters
- ADSI Support on Windows PE
- Attributes - Property Names - of an AD Account
- Bad Path Error on NT4
- Binding to the Global Catalog
- BitLocker Recovery Key
- Check for Admin Access
- Check if a Computer Belongs to a Certain OU
- Check if User Account Object Exists
- Check to see if Print Services are Running
- COM - Active Directory Published Certificates Info
- Convert Qword
- Converting Properties to a Human Readable Form
- Copy User or Computer account in AD
- Create a Mailbox and NT-Security-Descriptor property
- Create an OU in ADSI
- Create Virtual Directory
- Creating Computer Accounts
- Creating IIS 5 FTP Users
- Date AD account was modified last
- Delete Mailbox in Exchange
- Detect Disabled Accounts
- Disable Computer Accounts
- Display list of OUs
- Distribution List and Members
- Dont Expire Password
- dsAddtoGrp 1063 Object Does Not Exist
- dsAddToGrp and What is TESTECH
- dsDeleteObj Issue
- dsFindPath Limitation
- dsFindPath Search Request Slow
- dsfindpath Syntax Error
- dsFindPath with NULL Criteria
- dsGetMemGrp Sample
- dsGetProperty Error 1001 Using Slash in Path
- dsGetUsersGrps Error 1001
- dsGetUsersGrps Problem
- dsMoveObj error 1068
- dssetcredentx Error - The Requested Object does not Exist
- dsSetPassword and Blank Passwords
- dsSetProperty Error 246 Custom Attribute
- dsSetProperty userAccountControl
- dsSetSecProp Set Security Permission
- Editing IIS Properties in 2003 SP1
- Enumerating computers in a Win2k AD domain
- Error 1026 - the specified domain either does not exist or could not be contacted
- Error 1045 Operation is not Allowed on RDN
- Error 1047 Creating Exchange 5.5 Mailbox
- Error 1047 Operations Error Occured
- Error 1047 with dsCreateObj on Exchange 2K
- Error 1062 Constraint Violation Setting pwdLastSet Property
- Error 1063 using dsObjCreate
- Error 1068 The server is unwilling to Perform
- Error 1068 with dsSetObj on New User Account
- Error 212
- Error 222 with dsGetChildPath
- Error 234 Unable to parse ADSI path on NT4
- Error 239 Attempting to Rename an Account
- Error 241 when trying to remove a user from group
- Error 243 - Not a property of the object.
- Error 246 - Propertys syntax not supported
- Errors 1001 and 1026
- Examples for ADSI not working
- Exchange with ADSI
- Extract SMTP address in Exch 5 5
- Find DHCP
- Find Exchange Servers
- Finding a Users Exchange Server
- Force Password Change for ADSI User
- ForeignSecurityPrincipals Issue
- Get Computer Names
- Get Current User Path
- Get Effective Permissions
- Get Exchange Server a Users Mailbox is On
- Get List of all Exchange Aliases from Active Directory
- Get Logged In User
- Get User Properties
- Get Users Full Mame from their Logon ID
- Getting LastLoginTimestamp Value in ADSI
- Group Membership Checking
- How do I set the Password and Other Properties
- How to Get at Virtual Dirs
- How to Interpret UserFlags
- How to Pull all ObjectClass Items
- How to Rename an Account
- How to Specify ADSI Paths
- Instantiating Application Objects with ADSI
- LDAP Path with Comma
- LDAP Query Syntax
- List and Retrieve Groups in an OU
- List Computer Objects
- List Disabled User Accounts on the Domain
- List Groups a User is a Direct Member Of
- List Groups Computer is Member Of
- List Groups in OU
- List OU Objects
- List Users that Belong to an OU W2k AD
- List Users with Multiple Attributes
- Lookup Hidden Mailboxes in Exchange 5.5
- Member of Nested Group
- Modify UserAccountControl Attribute
- Move computer between containers
- MsExchMailboxSecurityDescriptor
- Name display --lastname, firstname
- Problem doing CreateMailbox on Exchange 5
- Problem Getting and Settind the AccountExpires Active Directory Property
- Proper AD Query
- Proper Syntax for an LDAP Path
- Query User to Identify which OU it Belongs
- Recursive Searching and dsGetChildPath vs dsFindPath
- Removing User Must Change Password At Next Logon
- Rename Computer in AD
- Renaming a Group in Active Directory
- Reset passwords in Active Directory
- Return Closest Domain Controller using ADSI
- RootDSE Explanation
- Search All Users in AD for a Property
- Set AccountExpires attribute
- Set Logon Name - ADSI
- Setting Expiry Date on AD Account
- Synchronize Domain and Local Password Issue
- Terminal Server Properties
- Test if Object is a Group
- Three Ways a User is Part of a Group in AD
- User Permissions on an AD Object
- Users Last Logon Time
- Verifying User Credentials Against AD
- Virtual directories on IIS via ADSI
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Bad Path Error in NT 4
Keywords: Bad Path Error in NT 4
Question:
When I run the following code on the domain controller, it will move a specified computer from "CN=Computers" to "OU=Desktops,OU=Workstations" or "OU=Laptops,OU=Workstations", but when I run it from a NT workstation in the domain, I get a bad path error.(w2kroot is a domain admin, dsIsObject commands show that Adsi_Desktops is a valid object, and Adsi_MyComputer_Computers shows that the computer is in the CN=Computers container.)
Any suggestions?
;---------------------------------------------
; Add Extenders
;---------------------------------------------
AddExtender("wwctl34I.dll") ;Used for Dialogs
AddExtender("WWWNT34I.DLL") ;Used for Accounts
AddExtender("wwads34I.DLL") ;Used for ADSI
Title_Bar_Text = "O/S Tuning"
COMPUTERNAME = "CRAZY8"
Domain_Name = "w2ktest"
;---------------------------------------------
; ADSI User Info
;---------------------------------------------
adsi_act = "w2kroot@%Domain_Name%"
adsi_pwd = "xxxx"
dsSetCredent(adsi_act, adsi_pwd)
Adsi_Desktops =
"LDAP://w2ktest/OU=Desktops,OU=Workstations,DC=Test,DC=spawar,DC=navy,DC=mil"
Adsi_Laptops =
"LDAP://w2ktest/OU=Laptops,OU=Workstations,DC=Test,DC=spawar,DC=navy,DC=mil"
Adsi_MyComputer_Computers =
"LDAP://w2ktest/CN=%COMPUTERNAME%,CN=Computers,DC=Test,DC=spawar,DC=navy,DC=mil"
Adsi_MyComputer_Desktops =
"LDAP://w2ktest/CN=%COMPUTERNAME%,OU=Desktops,OU=Workstations,DC=Test,DC=spawar,DC=navy,DC=mil"
Adsi_MyComputer_Laptops =
"LDAP://w2ktest/CN=%COMPUTERNAME%,OU=Laptops,OU=Workstations,DC=Test,DC=spawar,DC=navy,DC=mil"
CompTypeFormat=`WWWDLGED,5.0`
CompTypeCaption=Title_Bar_Text
CompTypeX=-1
CompTypeY=-1
CompTypeWidth=110
CompTypeHeight=61
CompTypeNumControls=4
CompType01=`20,40,70,DEFAULT,PUSHBUTTON,DEFAULT,"OK",1`
CompType02=`5,2,76,DEFAULT,STATICTEXT,DEFAULT,"Select the type of computer:"`
CompType03=`10,15,900,DEFAULT,RADIOBUTTON,Computer_Type,"Desktop",1`
CompType04=`10,25,90,DEFAULT,RADIOBUTTON,Computer_Type,"Laptop",2`
ButtonPushed=Dialog("CompType")
if Computer_Type == 1
Adsi_Target = Adsi_Desktops
Adsi_MyComputer_Target = Adsi_MyComputer_Desktops
Target = "Desktops"
else
Adsi_Target = Adsi_Laptops
Adsi_MyComputer_Target = Adsi_MyComputer_Laptops
Target = "Laptops"
EndIf
if dsIsObject(Adsi_Desktops) then Message("Desktop container valid",Adsi_Desktops)
if dsIsObject(Adsi_Laptops) then Message("Laptop container valid",Adsi_Laptops)
if dsIsObject(Adsi_MyComputer_Computers) then Message("%COMPUTERNAME% exists in
Computers",Adsi_MyComputer_Computers)
if dsIsObject(Adsi_MyComputer_Desktops) then Message("%COMPUTERNAME% exists in
Desktops",Adsi_MyComputer_Desktops)
if dsIsObject(Adsi_MyComputer_Laptops) then Message("%COMPUTERNAME% exists in
Laptops",Adsi_MyComputer_Laptops)
if dsIsObject(Adsi_MyComputer_Target)
Message(Title_Bar_Text,"%COMPUTERNAME% is already in the %Target% container.")
else
if dsIsObject(Adsi_MyComputer_Computers)
dsMoveObj(Adsi_MyComputer_Computers, Adsi_Target,"")
Message(Title_Bar_Text,"%COMPUTERNAME% has been moved to the %Target% container.")
else
Message(Title_Bar_Text,"%COMPUTERNAME% is NOT in the Computers container.")
EndIf ;Adsi_MyComputer_Computers
EndIf ;Adsi_MyComputer_Target
Answer:
Assuming you meant an NT 4.0 workstation and not a Win2k workstation, there are a couple of problems. (Your script worked just fine from one of our Win2k workstation.)- For reasons that are not completely clear the NT 4.0 Dsclient providers sometimes have a hard time
finding LDAP servers by domain name. You can get around this problem by substituting the name of the
domain controller computer for the domain name. For example, if your domain name is "grey" and the
domain controller's name is "birch", change the path from "LDAP://GREY/" to "LDAP://BIRCH/".
- Active directory will not always accept alternate credentials when offered by our extender running on a
NT 4.0 machine. The work around is to create a domain user on the domain controller with the same name
and password as the user on the NT 4.0 machine. Do this instead of using the dsCredent function provided
by the extender. Also, the created domain user account must have sufficient privileges to preform the
desired operation.
At this time it is not clear whether or not the dsCredent behavior is a problem with our extender or a problem with the client software. When I have more information, I will post it here.
- Finally, it appears that in order for dsCredent to work properly on an NT 4.0 workstation, the user name parameter must be changed to conform to NT 4.0 semantics. For example, assuming the "Grey" domain, the user name from a Win2k workstation might be "Admin@grey.windowware.com" and "grey\Admin" on an NT 4.0 workstation. If you want to make a script portable, you can use the WIL WinVersion(2) function to determine the Windows version and therefore user name semantics at run time.
Article ID: W14508
Filename: Bad Path Error on NT4.txt
File Created: 2001:03:02:14:39:48
Last Updated: 2001:03:02:14:39:48