Use the following values to set this variable: 0 - Server access is unrestricted 1 - Server access is restricted for the current server session. Restarting the server clears the setting. Replication is still allowed 2 - Server access is restricted persistently, even after server restarts. Replication is still allowed 3 - Acts as the first value but also blocks replication from all non administrator clients. 4 - Acts as value 3 but restarting the server will not reset the restrictions.
NOTE: Server_Restricted=2 (or 4) will prevent users from accessing the server after the Domino server is rebooted. This enable Administrators to have more time for testing the server before user are allowed access, as they can access the server. Description: This Variable enables a server to deny new open database requests and places the server in a RESTRICTED state. Users who have active connections to databases retain their connections. The Cluster Manager attempts to redirect new requests to other servers in the cluster. When an attempt to redirect is unsuccessful, the user receives a message and is not allowed access to the server. For each redirection attempt, Notes generates a failover event in the LOG.NSF. Note: You can use the Server_Restricted setting for any Domino server. This Variable is not restricted to clusters. Enables or disables server access to a server. If access is disabled, the server does not accept new Open Database requests. At the server console, type the following: Set Config Server_Restricted=1. This will prevent users from opening new sessions on the server. The following will be written to the log: 02:09:57 PM SERVER_RESTRICTED changed to 1. If the Administrator would like to disable this variable and once again allow access to the server, issue the following command: Set Config Server_Restricted=0. The following will be written to the log: 02:10:35 PM SERVER_RESTRICTED changed to 0. There are 5 possible values after installing 8.5.2 FP3 0 - Server access is unrestricted 1 - No new opens are allowed but existing opens work. The server can call out to replicate but will not accept inbound calls for replication. The server can route mail internally and outbound but not accept new emails. When the server is restarted it clears the restrictions. 2 - All of the above but restarting the server does not reset the restricted state of the server. 3 - Acts as the first value but also blocks replication from all non administrator clients. 4 - Acts as value 3 but restarting the server will not reset the restrictions.