A Forum reader recently asked:

“I installed IDM 3.5 and noticed that searching the AD driver set is very, very slow. Sometimes I even get the error “Service not found …”

I looked at TID 3268470 but it did not mention the steps to fix this. Any step-by-step procedure to create index for IDM 3.5 ‘slow’ issue?”

And here is the response from David Gersic …


1. Use ldapsearch to export the DN of each “NCP Server” object in your tree. For each server DN, do this:

dn: cn=ServerName,ou=Context,ou=Whatever,o=OrgName
changetype: modify
add: indexDefinition
indexDefinition: 0$objectClass$3$0$0$1$Object Class

2. Put this in to an LDIF file, then import it in to your tree.

3. If the object classes are not already there, you’ll need to add them to each of the NetWare servers.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: dgersic
Feb 20, 2008
9:43 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow