Is there a policy can send updated user.id to recovery DB automatically?

After user changed OU, it will change it in user’s local id file when the user connect to server. Is there a way sending new copy of user.id file to recovery/backup DB without user awareness?

Subject: Is there a policy can send updated user.id to recovery DB automatically?

It does that automatically in Notes 6 – R5 used to prompt the user, but Notes 6 just goes ahead and does it.

Subject: I think so. But somehow it doesn’t work in our environment

What could cause it stopping working?

Subject: The backup doesn’t go out instantly

The backup doesn’t go out instantly - the process is fairly compute-heavy, so it waits until the client has been idle and logged in for about 5 minutes with no dialog boxes open.

Subject: The problem is it’s never working

Whatever register new user or renaming, there is not user.id file been sending to backup db.I remembered it did work long time ago since upgrading to R6. What reason could be?

Subject: RE: The problem is it’s never working

Check your Recovery Authorities on the cert id. If one of the authorities listed is no longer a valid user in that domain the process will fail. At least I had seen this behaviour in R5, haven’t tested in 6…

Subject: They are all valid users

There are three ids in recovery info.

Is there other reasons?

Subject: Got it work.

Multiple match for the recovery mail-in DB.