When i try out this option on the test server I get the final option as :
Honor old names for up to <21> days" field,
and the minimum is 14 days…
My question is when a user has requested for a name change why do we need atleast 14 days for the name change to be affected… Why cannot it be instantaneous?
I have several users who after knowing that their name change has been affected may call back to enquire that their name has not been changed yet after logging in and finding that their name is still the same?
Also after a name change is affected will it :
Change the name in the mail preferences of "This mail file belongs to: also…
Subject: Logic behind “Honor old names for up to <21> days”
Many different questions here… have you looked up “Rename person” in the Administrator guide?
There is a timetable explained in the help document.
Also, when you create the name change request, you can follow it’s status in the Administration Requests database as the Adminp process tells you what it did and when it completed each task in the name change request.
There are several similar posts, but for the 21 days, both the old and new name will be accepted by Domino - for mail delivery and access. This is good if the person is on vacation, out of the office, or who automatically selects “NO” when the name change request dialog box pops up (and I can’t tell you how many people blow by this dialog box and refuse the name change)
Hope this helps… I’m sure there are others who will add to this post.
Subject: Logic behind “Honor old names for up to <21> days”
because theres no such thing as instantaneous when it comes to distributed systems like domino. my admin server could be on the other side of the planet (or even the next room but) with a 4 hour replication cycle.
the rename starts pretty much straight away but it takes time for everything to get processed. check the administration requests database to see exactly what it does for a rename.
the 21 days, i believe, is how long it delays before the delete part of the rename kicks in (and possibly some of the ACL renames too)
the mail file owner definately gets renamed as part of the process, the database title does not.
if you really wanted to you could always drop it down to 1 day and see what happens, personally i wouldn’t but that’s only because it works fine with the 21 day value for us and it’s not something i want to play around with.
Subject: RE: Logic behind “Honor old names for up to <21> days”
Hi,Thank you both for the response. However let me add that the minumum that can be set is 14 days and we cannot go below that.
I only hope that as part of the renaming process a mail goes to the particular user that the entire process of renaming would come into effect with those ‘n’ number of days.
Subject: RE: Logic behind “Honor old names for up to <21> days”
I only hope that as part of the renaming process a mail goes to the particular user that the entire process of renaming would come into effect with those ‘n’ number of days.
To the extent that I can understand the two questions I see embedded in that statement, the answers are Yes.
Name changes are not instantaneous in Domino (as they are in Windoze) because Domino, unlike Windoze, doesn’t use SIDs. In the M$ world, every ACL entry contains only the SID for the entry you add, not the “display name,” so changing a username or group name consists solely of editing the “display name” for that user or group in the single place it lives: in the account stored in the SAM or AD. As soon as that change replicates to all Domain Controllers, it’s done. However, in the Domino world, there are no SIDs. The contents of an entry in an ACL or a server document security field or an ECL or anywhere else a username shows up are the actual characters it takes to spell out the username, not a SID. Therefore, username changes involve finding every instance of that username, everywhere it exists, and changing it explicitly. Since the name might be in many fields/ACLs/etc in many dbs on many servers, it cannot be done instantaneously, so it’s done instead via the admin process.
The n-day period refers to how long the user’s ID file will contain the old name, so that the user can continue to authenticate against not-yet-updated server document security fields, ACLs, Readers/Authors fields, etc with the old name until those instances of the old name are updated.
As Marilyn explained, the reason is to accommodate any delays by using a period which is much longer than should reasonably be necessary for a name change. This does not mean that the name change isn’t “done” until the 21- or 14-day period (or up to as much as 60 days, actually) is over. Each part of the name change is “done” when it gets done. As soon as the person document contains the new name, the user can receive mail addressed to their new name (as well as their old names, forever). As soon as the Owner field in their mailfile’s Calendar Profile is updated, outgoing mail will no longer be sent “by” New Name “on behalf of” Old Name, etc.