In the Cool Solutions article “Workarounds for ConsoleOne Templates (, Peter suggests using ConsoleOne over NWAdmin in order to avoid LDAP issues. I have a few things to add to his comments.

The problem that TID 10075451 talks about is the need for a UniqueID attribute on each user, which ConsoleOne by default populates with the value of CN. For example, you could create a user BobSmith, CN=BobSmith and UniqueID=BobSmith, but NWAdmin does not populate this attribute.


If you’re using LDAP utilities that require UniqueID, here’s a workaround:

  1. Go to the LDAP Group object for the LDAP server.
  2. In the Attribute Mappings page, change the LDAP UID to NDS UniqueID mapping, to point at the NDS CN.

Note: Be sure that this mapping is what you want, as it will affect all servers associated with the LDAP group.

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: geoffc
Aug 17, 2005
2: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