Problems regarding renaming users in Domino
Environment:Domino 8.5.3 on Windows 2008
Problem: Customer is now planing to change the users' OU from the child OU to
parent OU (e.g. user/IT/ABC to user/ABC). They found some problems and
would like to verify how rename works.
The Administration Process requests are put into the ADMIN4.nsf
database. The Administration Process (AdminP) runs the requests that
are placed in the ADMIN4.nsf file. An administration request is
created by the administrator performing an action; it represents an
administration task and is run by the server task adminp. When an
administration request is generated, it appears in the Administration
Requests database (ADMIN4.nsf).
You may check admin4.nsf whether response documents had been generated
to parent request,
Like following statement, admin need to go "Name Move Requests", locate
the request, then select "Complete Move for selected entries"
Move person's name in hierarchy
(From the "Name Move Requests" view) Approving the "Move person's
name in hierarchy" is done by the administrator of the target
organization. This approval allows for the posting of the "Initiate
rename in Domino Directory" request to begin the moving of the user's
name to a new hierarchy.
Question 1) The local archives cannot be opened and the ACL cannot be edited after rename.
There's a similar issue documented in technote #1598323:
Users are locked out of their local archive after a rename
This issue was reported to Quality Engineering as SPR# DBRK7F5H9N and
fixed in Notes 8.5.3 Fix Pack 3. Starting with 8.5.3 Fix Pack 3, the
client updates the ACL after a rename when an administration server
exists but replication history is empty. In this scenario, no server
replica exists from which to propagate ACL changes made on the server,
so the change will ensure that exclusively local databases will be
Question 2) Users cannot edit the booking from room and resources after rename.
A similar problem report can be found, it's considered as "working as designed".
User renames are not applied to R&R entries making changes to direct reservations impossible by the Chair.
Admin can transfer reservation to new name of people.
For more details, please refer to:
Question 3) Name change request shows "pending"
This value will be removed from person document by
admin process "Delete Obsolete Change Requests"
after 21 days (by default) automatically.
For more details:
Or if user didn't authenticate with home server within period ,
admin can manually edit the user's Person document.
click Actions -> Remove Name Change Request.
This changes the value in the Change Request field on the Administration
tab of the Person document from "Pending" to "None."
Question 4) What is the solution if the local archive contains encrypted
Answer: Notes ID remains to use original key pair during rename, until
recertified by admin or end user requested new key pair. So encrypted
message can still be opened after rename, no action needed