I've a client who has been recycling local names.nsf files for new users. When a computer was assigned to a new employee, instead of wiping it and giving the new employee a fresh installation of Notes, they have simply been changing the location document in the existing Notes installation to be used for the new user. We're now moving to roaming profiles and implementing security policies and this is causing a problem. I've caught numerous instances where the names.nsf files of several users have the same replica ID's and have corrected that. However, the policies seem to be applied in a strange way which, I think, may have something to do with the recycled names files. Does anyone know of any other instance like this, what ramifications there may be from recycling names.nsf files rather than creating new files and how to fix this without deleting and re-creating the user?
Software/Hardware used:
Lotus Notes Domino
ASKED:
February 8, 2010 5:41 PM
UPDATED:
February 9, 2010 4:53 PM
Yep, you have a situation where the local address books have the same replica id. I’m not sure why things were done this way to begin with but now you have to deal with the resulting problem.
As Stiletto said, you will need to create a new copy of the local address books for the users. I believe there are also some utiils out there that can change the rep id on databases but haven’t tried them.