I want to change the OU for 1000 users because of reorganization. What is the best way to do
this? All of my users reside on one server. For Example.
Michael Lazer/Expert/Domino/Lotus will change to Michael Lazer/Expert/ADMIN/Lotus We have 15 different OU1 "/Expert/" (i.e. 15 Cert IDs) Can I write a program in AdminP to do it for me? Or some way I can recertify these 1000 people with no trouble?
If they are all server based, non-replicating users, then AdminP is your best option. It will be simple and strightfoward. You simply issue a Name Change in the address book, and choose to move the person to a new certifier. Once AdminP processes the documents, the person will be updated at next server access. That's the key. The person must touch the server via an icon, file/db/open, etc. A replication will not trigger the change. I will also caution you to roll this out. One thousand changes will cause AdminP to run for a long time. Break it out into chunks of 50-100.
Feedback from questioner:
Thanks for posting my answer but the answer is not complete.
- How would I recertify Web-only users (They can't do File->DB->Open)
- Can I write a program to do this?
Web only? Then why do they have actual ID files? The ID would only be used if these are DOLS users in conjunction with iNotes. If they are Web only, I can't see why they had hierarchical IDs. In your case, you will have no luck automatically recertifying your users. It will have to be completely manual, and you will have to accept all certificates yourself (or whoever is responsible for doing the recertifications). Again, I cannot figure out why Web-only users would have physical ID files. Please explain your situation further.
Answer from questioner:
We have hierarchal ID files for Web users because:
- We use OUs for identification purpose (for example, user1/IS/DomainName).
- We use the authors & readers fields in our applications.
- We have mail files for Web users.
We don't use iNotes or DOLS.
The answer is the same, even though now I can kind of see your reasoning. It will be a
completely manual process.
This was first published in January 2003