Menu Close

GIM Contacts List via LDIF

Senario #1: Copying UserA list to everyone.

You must Export / Import contact attributes via ConsoleOne NDS Import / Export (ICE)
First set up ONE user with all the contacts you want the other users to have by adding or deleting contacts from the GWIM client.
We will then export an LDIF file for the users so that we can copy the contacts from it when we create our Import file.
1) Run ConsoleOne from the server sys:\PUBLIC\mgmt\ConsoleOne\1.2\bin to have a Wizard option on the tool bar.
NOTE: the Wizard seems to be missing form later versions of ConsoleOne, V 1.3.7 +
2) Highlight an NDS Organization and then select the Wizard | Import / Export option from the top tool bar in ConsoleOne
3) Select to Export LDIF file and choose Next
4) Fill in the Ldap server IP and port 389 or 636
NOTE: I had some trouble getting it to connect on the non secured port 389. Gave me a confidentialy error. I used 636
5) Click the authenticated login arial button and Fill in the cn=admin,o=XX
6) On the next page fill in the container where userA resides IE: O=msgusers and choose the arial button for “one level”
7) Click the tab for filter and add the word user to replace the astric IE: objectclass=User
8) Leave the attribute tab at default IE: “All user-level attributes” and click to the next page
9) Enter C:\export.txt to create the exported file we will use to copy our needed contacts from

10) Open the c:\export.txt and find userA IE: dn: cn=msguserA,o=msgusers
11) Note userA attributes regarding the contacts he has IE: nnmContactList: 1;0;0;2;;CN=mess1,O=messenger ;mess1;
These are the attributes we will need to copy to our new Import.txt file we will use for importing the contact list to the other users.

12) create a new text file c:\import.txt and add the following entries by manually typing them in:

dn: cn=msguserB,o=msgusers
changetype: modify
add: nnmContactList
13) Now copy from the export file all the Contacts under userA
nnmContactList: 1;0;0;2;;CN=mess1,O=messenger ;mess1;
nnmContactList: 2;0;1;2;;CN=mess2,O=messenger ;mess2;
Stop after the last nmContactList. There will me more messenger stuff, but it is not part of the contact list.
14)The file will appear something like this:
dn: cn=msguserb,o=msgusers
changetype: modify
add: nnmContactList
nnmContactList: 1;0;0;2;;CN=mess1,O=messenger ;mess1;
nnmContactList: 2;0;1;2;;CN=mess2,O=messenger ;mess2;

15) Save the import.txt

16) use the NDS Import / Export utility to Import the attributes to userB changing setting as needed regarding Import LDIF file and the other users base DN where userB resides.
The end result userB will now have all the contacts that you copied from userA entries in the export file as well as userB orginals.
17) change the cn= for user B to user C and repeat. You can also make one huge import txt with all the users in it with seperate copies of the contact list.
How to mass delete contats using LDIF is below.

Senario #2: Resettting everyone to a default list.
1) Create a text file that contains the following
dn: cn=UserA,o=container
changetype: modify
delete: nnmContactList

dn: cn=UserB,o=container
changetype: modify
delete: nnmContactList

ETC…

1) Run ConsoleOne from the server sys:\PUBLIC\mgmt\ConsoleOne\1.2\bin to have a Wizard option on the tool bar.
NOTE: the Wizard seems to be missing form later versions of ConsoleOne, V 1.3.7 +
2) Highlight an NDS Organization and then select the Wizard | Import / Export option from the top tool bar in ConsoleOne
3) use the NDS Import / Export utility to Import the above text file.
4) Now the next time the user logs in, they will receive the default Contact list.

NOTE: you must make sure everyone is a member of the policy that contains the default contact list. It is possible for users to have the ablity to chat (via the  GWM scope) with out being a member of any policy
Failure to do so will result in users with a blank contact list with a link to add a contact.

Senario #3: Removing an ex employee from everyones list.


Cont…


Leave a Reply

Your email address will not be published. Required fields are marked *