How do I change the capitalization of a person's name?

A user was created with the name mcBride when it should have been McBride.
How do I fix this? Rename requires actually changing the spelling of the name.

Can I fix this by creating the user again and just letting it update the person doc? Will this also update the Notes ID file?

I have to get this right the first time. It's the CFO.

Hello.

Domino has a process for renaming. Direct changes to user documents are not reflected in the ID file.

https://help.hcl-software.com/domino/12.0.0/admin/conf_renaminganotesuserscommonoralternatename_t.html

If you are setting up for the first time, we recommend that you re-register new user with the correct name.

And delete the user registered with the wrong name.

https://help.hcl-software.com/domino/12.0.0/admin/conf_deletingauser_t.html

Regards,

Shigemitsu Tanaka

Yes, I know about renaming users. Renames will only work when the name is changed. It doesn't work if all you are doing is changing the case of the characters.

I can't delete the user. He has been active for months.

>> A user was created with the name mcBride when it should have been McBride. How do I fix this? Rename requires actually changing the spelling of the name.

Response: If you say the user was registered sometime ago and the user is using the Notes client and his mail file also has emails and calendar entries in it, in this case, RENAME is the best option, as it takes care of updating most of the stuff, like the ID file, mail file owner, ACL, calendar entries, etc., through the administration process.

>> Can I fix this by creating the user again and just letting it update the person doc? Will this also update the Notes ID file? I have to get this right the first time. It's the CFO.

Response: If this is a newly registered user and the user has not yet configured the Notes client, then you can follow the below methods.

1) Delete the user mcBride and re-register the user with proper name as McBride.

OR

2) You may update the existing person document with the below steps.

2.1) If the user ID file is in ID vault database, you can delete the vault document in the vault database. If the user is not vaulted then continue the step 2.2)

2.2) In the administrator client click on Register, select the certified ID and provide the password.

2.3) Provide the correct name of the user "McBride" in the registration form.

2.4) Click on Register, it should prompt below messages say Yes to it.

Successful message shows as below.

This should update the existing person document to as below.

Thank you

Regards

Shrikant J

How will re-registering him affect the current ID file he is using? I don't have easy access to his laptop as he is traveling.

Re-Registering a user will create a new id file with a new private key: The ID that the user uses will be obsolete and cannot be used anymore. So this is not a real alternative.

As you realized a change in capitalization is not a valid name change as Domino considers "McBride" and "mcBride" to be the same name.

Unfortunately there is no "convenient" way to fix this. You need to take two Steps:

  • Rename the user and do a "real" change like adding a middle initial or adding an organizational identifier
  • After the user accepted the change (automatically by logging in to his home server) and the rename has taken place in the names.nsf and the user ID remove all AdminP- Documents for this rename so that no "real" rename in Groups, ACLs, Reader fields etc. take part
  • Rename the user again and remove the change you did in first step
  • Again: After user accepted the change remove the adminp documents for the change

That way the ACLs, Groups and Reader / Names / fields will still contain the wrong case, but it will not matter....

SUCCESS! Torsten, I discovered the issue. First of all, as of 12.0.2 FP1, a rename does allow changing the case of characters and sees that as a change. I don't know what version this fix was introduced, but I do know it works with 12.0.2 FP1 admin client.

Second, the reason it wasn't working for this particular user is because it had previously been fixed and then the user went back and started using the old ID. So the name change saw that the change I was trying to make was identical to what was already in the ID vault. Your tip was a clue. I tried renaming the user and just changed it to go to the wrong capitalization (successfully). Then renamed it back to the correct capitalization. Now everything is correct.

Thanks for your description which led to me finding the true solution and the discovery that names can now be changed in capitalization via a name change.