Strange Issues with Lotus Domino

Hello all,

There are issues we are experiencing in our organization that’s making administering our Domino infrastructure a very tedious and manual process. These narrated below.

Renaming of users: Our organization is a Bank with many branches, we employ and re-deploy staff often. Users are created in a hierarchical order with the Organization name and Branch the user belongs to part of the name. The hierarchical goes like this: staffname/branchname/organization.

We also have several groups created in the organization directory; every branch has a group in the org. director with the group populated with all the branch members. There are also several other kinds of groups in the org. directory.

Whenever a staff is redeployed from a branch to the other, we always rename him to have the new branch reflect in their hierarchical name, however we discovered that the renaming process does not change the old name to reflect the new name in the groups the name is added. What I mean by this is that suppose a staff (staff1/branch1/organization) in branch1 group is redeployed to branch2, when he is renamed he becomes (staff1/branch2/organization). However, the old hierarchical name (staff1/branch1/organization) is not removed from group1 and the new one staff1/branch2/organization is not updated in the same group. This means that for each person we rename we have to remove his old name from all the groups he belongs to and add the new name to the groups they should belong to. All these are done manually and they take a lot of time.

Pls. note that redeployment is not the only reason for renaming a staff, it could also be as a result of change in name (mostly for newly married ladies) and also wrong name entry at the time of creation. Meaning that in this case when the user is renamed she should retain all the previous groups she belonged to including the branch group. But the old name is still not removed from groups she belonged to neither is the new name added to them.

Also the mail files access control list for any user who is renamed does not also get updated with the new name. Again we have to remove the old name from the mail files ACL and add the new name to it manually; otherwise the person cannot logon to his mailbox.

Again, we have observed that after renaming somebody, after a few weeks, the name gets changed to the old name automatically without the person being renamed again. We find all these strange and we’re not sure if these are the way the product works for everybody or if there anything we are doing wrong.

This is really a big challenge to us doing these manually all the time. Pls. is there anyway we can automate this? I’m really surprise that these things are not taken care of in the product. Or is it that there is something that’s missing?

Please any assistance on how to resolve these issues is very highly appreciated.

Thanks,

Austine.

Subject: Strange Issues with Lotus Domino

You haven’t explained how you are doing the rename. You should search Administrator Help for “Rename User” and then look at the Managing Users document for information on how to move a user name in the name hierarchy.

Subject: RE: Strange Issues with Lotus Domino

This is how I rename a user:

I right click on the user’s person document from the admin client and select Rename => Change Common Name => Chose a Certifier.

I enter the certifier password and then adjust the entries in the fields as needed or enter the new branch name in the Qualifying Org. Unit field if the user’s branch has changed.

I hope with this information I can be assisted.

Thanks for your willingness to help.

Subject: RE: Strange Issues with Lotus Domino

Have you checked the certification log for errors? Have you looked at the Administration Request database? Check to see that your databases (including the domino directory) have the correct Administration server listed in the ACL Advanced tab.

Subject: RE: Strange Issues with Lotus Domino

Also -

You are changing the common name, but you want their hierarchical name changed? That would require a “move to new certifier”. Common name is just for renaming for spelling errors, marriage/divorce, etc.

Are you completing the move in the adminp database? Go to the Name Move Requests view, select the request, and do “Actions - Complete Move”

Are you allowing the adminp process time to complete the rename? It can take up to 24 hours for all the renaming processes to complete. Renaming in the person document takes 1 hour.

If you look in the help, you can find info on the types of changes performed by adminp, and the time frame in which they are performed.

Make sure you make the changes on your registration server. Then make sure replication of the adminp database occurs between the registration server, and the user’s home mail server. Then make sure the user authenticates with his home mail server to start the rename process - renaming does not start until the user authenticates. If you have backup copies of the user’s ID file, you can switch to that ID, authenticate with the server, and start the rename process yourself. The rename will still take effect on the user’s ID file.

If you wait too long for the user to authenticate, the move request expires, and you have to redo it.