I have one operational Domino server (call it Domino1/ORG) and have been tasked with setting up another server (Domino2/ORG).
The catch is that the second server will be on a different network from the first (main) server and apart from initial setup, the two servers will NEVER communicate. Only a few users will be using BOTH servers, but most will just use the first.
I’m wondering how to go about setting up this second server so that the “priviledged” users can use both using their existing IDs. Again, I can have them communicate during setup (to exchange certs or cross certify or whatever I need to do) but after that, there will be no communication or replication between them.
Thanks,
Shawn
Subject: 2 Domino Servers
There are lots of options that depend on what you want to accomplish. The servers can be in separate organizations (different certifiers) and/or in separate domains (different directories, names.nsf). You would use separate organizations if you want to maximize security between the two servers and their users. You would set up different domains if you have different directory requirements.
If the goal is to just have server 2 used by a few members of the same company I’d keep things simple and have one organization and one domain. If you take this approach then you want Server 1 and Server 2 to replicate at least names.nsf and admin4.nsf. Otherwise changes managed by the administration process will not work and new employees and terminations would have to be added to each domain independently…
You can control, access to either server through the server document access fields. The “access server” filed of server 2 would have Server 1 and a group that contains the members you want to access Server 2.
Subject: RE: 2 Domino Servers
Thanks for your quick reply Mike. I like the idea of keeping things simple and keeping the existing ORG/Domain.
So could I simply setup the new server, register it with the first, and then replicate the names.nsf and admin4.nsf ONCE and be on my merry way? I’d also lock down the new server as you suggested.
Knowing that the two servers will never be able to talk to one another, could I simply copy the names.nsf and admin4.nsf from Server1 to Server2 whenever there are changes that need to be propagated (ie. new/deleted users)? There will never be a network connection between the two so this would be a copy and paste operation 
Thanks,
Shawn
Subject: RE: 2 Domino Servers
It gets a bit complicated if the two servers can never replicate because that means that key system databases in the domain (names.nsf, admin4.nsf) will not replicate and certain maintenance tasks that are automated by adminp will not work. If you can’t find a way for the servers to replicate those system databases either through a network or internet connection then you may be better off having two domains. You could still have one organization, i.e. one certifier, but users (and servers) would be assigned to different directories, aka address books, names.nsf.
This is one of those things that you can set up just about any way you want but the real key is the ongoing maintenance. At least keeping everyone in one organization simplifies things but I’d look very hard at trying to find a way to allow the servers to replicate. Finding a secure way to replicate the servers will make life easier in the future.
Hope this helps. Its difficult to make firm recommendations without really knowing the details of your situation.
Good luck
Subject: RE: 2 Domino Servers
Since the two servers will never be able to communicate…
Provided some of the individuals who will use both servers can be trusted with the Directory and other admin databases, you can have somebody replicate the Directory between their laptops and both servers. Not the ideal situation by any means, but it’ll at least give it some update frequency.
Subject: RE: 2 Domino Servers
Hello Shawn,
I think you should install the 2nd server with a new Certificate and Domain by following the Server Setup-Procedure(first Sever). I think this is the easiest way to get around of your problem. If you have done so, cross-certify the users which need access to Server 2 and do all the necessary work on their clients, i.e. connection docs , adding databases to their workspace etc.
bstrgds
Klaus