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

[bennyphipps]

Hi,

So I don't believe the transform is relevant as I'm just trying to import the data at the moment...   I don't get any errors though just that XXXX inserts have been made into the import table.

[poyntzj]

what does your filter look like ?

and is the record there when you look at Loaded data ?

[bennyphipps]

Filter is:

(objectclass=group) and I also tried (samaccountname=*) - no joy

And no the record is NOT in the import when I look at loaded data... that's the crux of the issue... why isn't it there...?   I created a new copy of the OU Definition and changed the filter to specify (samaccountname=XYZ) I get it through fine...

weird

[poyntzj]

what is your RDN set to in both the mass and single import ?

i wonder if the mass import is looking in one area and the single import is looking at the whole of your AD structure

[bennyphipps]

This is the OU Defintions...   The bottom one is where I specified the group by Samaccoutnname the top one is the main group import OU definition.   There's a weird slight pattern whereby when I did a comparison of AD grops in the OU and group in the import and sort a->z it there only seems to be ad groups missing earlier on... i.e. AD groups with certain prefixes are never missing but some ARE missing with other prefixes.

Specifically

a samAccountName prefix of "GG" or "GL" will never be missing howeevr

a samAccountName prefix of "Data" may be missing (46% of them are missing from ServiceNow).

Ben