All Forums
> Network Scanner
> Current topic
Active Directory Import
Started by rmpf2
rmpf2
Active Directory Import 29 October 2016, 06:34 |
Re: Active Directory Import 29 October 2016, 09:53 |
Admin Registered: 18 years ago Posts: 3 518 |
rmpf2
Re: Active Directory Import 30 October 2016, 04:26 |
Thanks... Just a sample???? Can it be exported?
Also, is possible to make the call to the AD with some kind of query? Like trying to do the import of only Window XP machines.
For those that are not discarded to later being resolved is possible to have them with a default comment? (Comment can be the hostname?)
Also, is possible to make the call to the AD with some kind of query? Like trying to do the import of only Window XP machines.
For those that are not discarded to later being resolved is possible to have them with a default comment? (Comment can be the hostname?)
Re: Active Directory Import 30 October 2016, 14:59 |
Admin Registered: 18 years ago Posts: 3 518 |
We have added a way for user to customise LDAP URL used to query AD as shown below in these builds.
A description of how to create custom AD searches can be found here.
A description of how to create custom AD searches can be found here.
rmpf2
Re: Active Directory Import 01 November 2016, 06:29 |
Hi Andrew.
This was my first working AD connection statement before the new query feature: <LDAP://OU=IT,DC=business,DC=local>
Now it didn't work. This is the error: One or more errors occurred during processing of command
Later I tried: <LDAP://OU=IT,DC=business,DC=local>;(&(objectCategory=computer)(operatingSystem=Windows XP*)) , but again appear the error.
Can you tell me what I'm doing wrong or give us an example?
This was my first working AD connection statement before the new query feature: <LDAP://OU=IT,DC=business,DC=local>
Now it didn't work. This is the error: One or more errors occurred during processing of command
Later I tried: <LDAP://OU=IT,DC=business,DC=local>;(&(objectCategory=computer)(operatingSystem=Windows XP*)) , but again appear the error.
Can you tell me what I'm doing wrong or give us an example?
Re: Active Directory Import 01 November 2016, 09:48 |
Admin Registered: 18 years ago Posts: 3 518 |
It's because now the entire connection string is exposed, including the attributes to select and search depth. Try something like this:
<LDAP://OU=IT,DC=business,DC=local>;(&(objectCategory=computer)(operatingSystem=Windows XP*));name;subtreeA similar example launched on a DC works for me:
Rmpf2
Re: Active Directory Import 01 November 2016, 12:01 |
Re: Active Directory Import 01 November 2016, 12:13 |
Admin Registered: 18 years ago Posts: 3 518 |
Those are components of an LDAP search query:
- name is a selection of what attributes to retrieve.
- subtree is a search scope.
Rmpf2
Re: Active Directory Import 01 November 2016, 12:50 |
Re: Active Directory Import 01 November 2016, 14:27 |
Admin Registered: 18 years ago Posts: 3 518 |
New update. Now the search scope and selected attributes are hidden to prevent any confusion and a filter field as added as shown below.
rmpf2
Re: Active Directory Import 02 November 2016, 00:12 |
Hi Andrew, nice job, every new feature, including the examples and the one to save the no ip resolution discarded hostnames, thanks. In the case of the hidden options like the name attribute make sense cause it would always be the one in terms of NS job but i think your first idea to allow the user to choose the search scope was not bad at all. Maybe a combo box or a list box with base, one level and subtree?