LDAP import missing values

[bennyphipps]

Hi,

we've got a LDAP data source setup (using a MID Server) which is only pulling in 6000 out of 7000 records.   I can see AD groups that are virtually identical in name and all other attributes (except the obvious ones like ObjectSID, ObjectGUID samAccountname etc) some which are included and others which are not there's no fields with massive values in either etc.

This is not a problem with Transform map as the data is missing from the import itself.   I've tried clearing down the Filter in the OU Definition and that made no difference either.

I can view the AD Groups from the instance when I use the LDAP Browse functionality ok though.

Can anyone help or suggest anything?   My import table field sizes are all pretty large to account for truncation etc but some of the groups.

Cheers,

Ben

[poyntzj]

What happens if you try to import just this object ?

I have an option for singleUser and singleGroup for this kind of thing

[bennyphipps]

Hi Julian,

Sorry I've not tried that... how exactly would I set that up?   With a FIlter in the OU definition of samaccountname = XYZ I guess...?

Cheers,

Ben

[bennyphipps]

Hi,

Well blow me down... that worked ok... It's pulled in the record individually and I can see that would indeed be a unique record as the objectSID.

I've compared that one groups attributes and they are pretty much identical except for the key values like SamAccountName, ObjectSID source, DN etc...   i.e. none of the fields are particularly large, there's only 2 members in each group no funny characters etc...

I wonder why the main OU Definition does not pull it in... any ideas?

Cheers,

Ben

[poyntzj]

Sorry, been working on a couple of things

All our standard groups have ITSM in their name as either the suffix or part of the Suffix (we also have ApprGrp for approvals NotGrp for Notification)

Our transform removes the ITSM from the display name and changes ApprGrp or NotGroup to Approval or Notification

We also import some groups with a specific mail address.   If our network monitoring raises a ticket, the relevant local team gets the notification via these groups - not all of them are process users, but at least they are notified.

Our single user import is as follows

Name: Single Group

RDN: OU=Static,OU=Distribution Lists,OU=INFR

Query Field: sAMAccountName

server: AD server      

Table: Group

filter: (&(objectClass=group)(cn=Import Group ITSM))

Our standard import for groups is

Name: Groups - Universal

RDN: OU=Static,OU=Distribution Lists,OU=INFR

Query Field: sAMAccountName

server: AD server      

Table: Group

filter: (&(objectClass=group)(|(cn=*ITSM*)(mail=*.itops@groupm.com)))

And the group that you can import manually is appearing in the import set for your larger import ?

and if so, when you transform, are you getting errors ?