ADSI com objects ... ?

[snaileater]

I've read that ADSI (Active Directory Service Interfaces...) can be used by any programming language that can call automation/COM objects.

Is it the case of AutoIt or is it only possible with tools like VB apps and WSH ?

all the tries i made in order to create ADSI object like :

$object = ObjCreate("WinNT://" & "MyDomain")

failed.

How come ?

Thanks for ur help !

[DaleHohm]

First, by intent and design you should be able to exercise any of the COM interfaces from AutoIt as you would from another language -- COM support is still beta however.

Next, all of the examples I've seen for the WinNT namespace in ADSI use Get instead of Create, so you might check out ObjGet instead of ObjCreate.

Third, please provide more information in posts like this and others that you have made recently. You'll find that if you take a moment longer to tell us what version of AutoIt you are running, give specific error messages and a stand-alone example of your code (although in this case it is enough) you'll get much better answers.

Also, since the COM code is in beta, if you could test something like this in a language such as VBScript first it would help isolate whether the trouble is correct usage of the COM object or whether it is an issue specific to AutoIt.

Thanks,

Dale

[SvenP]

I've read that ADSI (Active Directory Service Interfaces...) can be used by any programming language that can call automation/COM objects.

Is it the case of AutoIt or is it only possible with tools like VB apps and WSH ?

all the tries i made in order to create ADSI object like :

$object = ObjCreate("WinNT://" & "MyDomain")

failed.

How come ?

Thanks for ur help !

<{POST_SNAPBACK}>

Using ADSI is no problem when you use the latest beta version of AutoIt3. DaleHohm is right: you have to use ObjGet(), because the object is already present in the system and does not have to be 'created'.

Some WINNT examples are available in the tests\com directory of the beta AutoIt3 ZIP file. When accessing ADS you have to use an LDAP moniker like:

$objGroup = ObjGet("LDAP://CN=SampleGroup,OU=Groups,OU=TM,DC=department,DC=company,DC=country" )    

$objGroup.GetInfo

$MemberOf = $objGroup.Members    ;Get the members of this group

$UserArray[0]="user"
$MemberOf.Filter = $UserArray       ;We need only User objects

..etc..

Regards,

-Sven