Change Administration Server

From the admin help file:

The Administration Process uses administration servers to manage administrative changes that apply to databases. Either the administrator or the database manager can specify the administration server for a database. Perform this procedure on an as-needed basis.

Note  To change the administration server for a database, you must have Manager access to the database or be designated as a Full access administrator on the Security tab of the Server document.

  1.     From the Domino Administrator, open the domain containing the server with the database for which you are setting an administration server.

  2.     From the Servers pane, select the server containing the database you are setting as an administration server.

  3.     Click the Files tab and then select the database to which you are assigning an administration server.

  4.     From the Tools pane, click Tools - Database - Manage ACL.

  5.     Click Advanced.

  6.     Complete these fields and then click OK:

Administration Server     Choose one of these:
     None - If you do not want an administration server assigned for the database.
     Server - Select a server from the list.

     Choose one of these according to whether you want modifications to the indicated fields to occur during a rename group, rename user, or rename server action; or during a delete server, delete group, or delete user action:
     Do not modify Names fields - Names fields are not updated during any of the above rename and delete actions.
     Modify all Readers and Authors fields - Reader and Author fields are updated during the rename and delete actions listed above.
     Modify all Names fields - All names fields are updated during any of the rename or delete actions listed above.

  7. If you will be processing administration requests across domains, complete the procedure "Creating a Cross-domain Configuration document."

In your case, if both machines will not be online at the same time, make sure to create the server (register it) in the address book on the old server before you start the process described above.

I actually had already read that excerpt from the Admin Help, but it seemed to apply to individual databases. I have already done that process on the names.nsf, but I wonder if I have to repeat this process again for each of the thousands of databases on this server? I hope not....

The only thing I could find in the Admin Help was a sentence that said that the Administration server is specified at the time of server install. Does this mean that I will have to install Domino again? That would be bad, as these are production servers with many users.

In my case, both Server1 and Server2 have been online for several months, so both servers were registered a long time ago. Now we wish to take Server1 offline due to an office closing. However, since Server1 is the Administration server for the domain, I am concerned as to what impact this will have. Therefore, I wish to make Server2 the new Administration server (neither server is a new server, they have both been running in production for months).

Thanks for any tips you can provide.

Regards,

Scott

as far as the servers go, just make sure you have at least 1 administration process enabled in the server document of the server, and load the adminp task.  AdminP can run on as many servers in teh database you like.

Wow, that's pretty cool. I did not know the "Administer Multiple ACL's" option in Domino Administrator was there. Funny thing is, I think at some point long ago, I had actually written a tool in LotusScript to manage ACL's on multiple databases at once. Now I come to find out this capability is built into Domino Administrator! Doh! I guess the lesson to learn is always check to see if a solution already exists before building one yourself.

Andrew, I used your suggestion above to set the Administration server for all databases to Server2. However, it still showed Server1 with the "key" icon on it (presumably indicative of Administration server). It was not until I went to Administration -> Refresh Server List -> Current Domain menu option in Domino Administrator that the "key" icon moved to Server2.

Then, just for fun, I set the Administration server for ONLY ONE database, names.nsf, back to Server1, and did the Administration -> Refresh Server List -> Current Domain again, and, BOOM, the "key" icon moved back to Server1. So I guess the system considers whichever server is the Administration server for names.nsf to be the Administration server for the domain (kinda makes sense).

I guess my main concern was just the stupid little "key" icon not being on the right server, that kind of bothered me. I had already set the Administration server for names.nsf to Server2, but the "key" icon hadn't moved from Server1. Didn't realize you have to refresh the server bookmarks to get the "key" icon to move over. That's all.

Anyway, Andrew, you were very helpful, so the points are yours and thanks a lot!

Regards,

Scott

Glad I could help.  All that "refresh" does is like pressing F9 on the view in the nab.

;-)