Now I wanted to give the QAD Cmdlets a try and I really failed in the beginning!
I can't connect to the LDAP server, because I don't know if and how I can persuade "connect-QADService" ( or whatever I should have used ) to connect to the server providing an IP address and a naming context. Additionally I might heve to use simple bind later on to provide a username like "uid=user, ou=org" and a password "pwd" to connect.
Is this possible with the QAD Cmdlets? ... and if ... how?
First, is your LDAP server a Windows Domain Controller, ADAM/ADLDS host, or a generic LDAP host? I'm not sure if Quest cmdlets or System.DirectoryServices support connections to anything other than Microsoft based Directory Services hosts.
If your LDAP server is a Microsoft DC or ADLDS host then the following should do the trick to specify the host, naming context and supplying username and password in one command.
I got the idea ... but still can't connect :-) I can connect with Softerra's LDAP Browser e.g. even as anonymous user, if I just want to read some attributes, but even this seems to be impossible with get-QADObject ( or I don't do it right )