Our users do not reset their passwords using the Lotus Notes GUI, instead we use some password management software which after a password change delivers a new ID file to the users machine.
The problem we are having is our users are setup as Roaming Users and unless the user changes their password using the Notes GUI the users ID File post password change does not get updated in their personal address book / roaming. When we then come to set up the user on a replacement laptop roaming insists on delivering the old id file it has stored which or cause is a very old password.
From
this site I found this section on how the process works
The password for the id file can be changed either through the Notes Client user interface (UI) or via the operating system (CTRL+ALT+DEL). Because of the present Notes Client functionality as it relates to a Roaming User, if the password is changed through the Notes Client UI, then the id will be flagged to indicate a change has occurred so that at the time the Notes Client is closed, the id changes will be replicated back to the roaming server. However, if the password is changed via the operating system instead, the id file will not be flagged, and unfortunately the roaming feature will believe that no change has occurred; therefore, it thinks there is no need to include these id changes for replication back to the roaming server.What I am looking for, is there a way to force the id file to be updated every time the user logs on or open notes?
Anyone have any ideas?
