/build/static/layout/Breadcrumb_cap_w.png

LDAP import to big errors out

It appears that our LDAP users is now to big to import and errors out. I have to import new hires (don't know their names in adavanced) daily so they are in the kbox. When the import happens it imports all users everytime. Can anyone give me a idea how to shrink this down and import in smaller blocks?

See script below

(&(objectCategory=person)(objectClass=user)(samaccountname=*))

0 Comments   [ + ] Show comments

Answers (9)

Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
Puttying your users into groups would be good.

Or how about an alphabetical breakdown (LDAP doesn't support regex):

(&(objectCategory=person)(objectClass=user)(|(samaccountname=a*)(samaccountname=b*)(samaccountname=c*)(samaccountname=blah*)))
Posted by: WhitzEnd 13 years ago
7th Degree Black Belt
0
I agree with Gerald. Groups would really be the way to go for this. If the new hires are created in a certain group or OU before they are moved to their respective departments then you could create a query that will import just that group.

If you dont mind me asking...how many users are importing and causing it to time out?

Brandon
Posted by: RBakerNoble 13 years ago
Senior Yellow Belt
0
The new users are created in their proper OU containers. I just don't know when new users are added them. Right now we are imported around 2800 users
Posted by: RBakerNoble 13 years ago
Senior Yellow Belt
0
We actually have more OU's then letters in the Alphabet
Posted by: airwolf 13 years ago
Red Belt
0
We have over 3000 users imported and the LDAP import syncs nightly. Do you mean you have 2800 NEW users imported per day? If not, you shouldn't be hitting any kind of 'max'. I haven't seen any issues on my K1000 with over 3000 users in one LDAP import.
Posted by: RBakerNoble 13 years ago
Senior Yellow Belt
0
No we only average a couple of new employees a day. The import though imports everybody even if there is no changes to their accounts.
Posted by: WhitzEnd 13 years ago
7th Degree Black Belt
0
The import shouldnt reimport each user. It will update any existing user with changed information and also import the new users. It shouldnt time out with 3000 users either. The only time i have seen the LDAP import timeout was with 25k+ users. What time is your import set to run?
Posted by: RBakerNoble 13 years ago
Senior Yellow Belt
0
When I run the import it shows me the new users that are being imported (usually aroud 5 or so) and then it says for the other 2700 users that there are changes, which I know can not be true unless it is picking up a time stamp or something. We have never been able to get our scheduler to run. Dell says due to size of import. I try and import manually once in the morning and once late in the afternoon.
Posted by: RBakerNoble 13 years ago
Senior Yellow Belt
0
Just a side note all of this was working fine until a week ago and the only thing that really changed lately was we loaded the SSL cert about three weeks ago. Just curious after we finally got the cert to work properly My Kbox now takes about 20 minutes maybe more to boot up has anyone else seen this?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ