Submitted by: Jack Shreve


In a recent Cool Solutions article, fellow Novell afficionado Geoff Carman gave a good explanation of why searches in ConsoleOne sometimes don’t work. Specifically, the article discussed the symptom where, when typing the first few letters or even all of the object name, the search doesn’t go to the object, but instead will end up on the first object in the container.


One thing not mentioned was that C1 container searching is limited to containers with less than 1000 (one thousand) objects. Any container with more than that will require the use of the EMA (Eyeball Match Algorithm). I don’t know why this should be, but there it is.

Note: I have tested this behavior only in ConsoleOne v1.3.6d-h.

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: ConsoleOne

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: cnejack
Sep 19, 2007
1:21 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