Using Domino silent server setup

A silent setup is one in which you do not view the setup screens as you run the server setup profile. You can do a silent setup at the server you are setting up or from a client system.

About this task

Before running the setup command, complete any pending reboot actions.

To do a silent setup at the server

About this task

Procedure

Install the Domino® server program files on a server system, but do not run the Domino server setup program.
At the command prompt on the server, from the Domino program directory, do one of the following:
- On a Windows™ server, enter
```
nserver -silent c:\myprofile.pds
```
- On a UNIX™ server, enter
```
server -silent  /myprofile.pds
```
  Note: If the profile file is not in the root directory, use the profile's full path in the command.
  
  Note: Entering nserver -help or server -help displays the parameters available for working with server setup profiles.
If the profile uses existing server, certifier, or administrator IDs that require passwords, do the following:
1. Create a text file that contains the passwords for the existing IDs. The keywords in this are:
  
  Server=
  
  AddServer=
  
  Certifier=
  
  OUCertifier=
  
  Administrator=
2. Add a parameter in the command line for the name of the password file. For example, on Windows enter:
```
nserver -silent c:\myprofile.pds c:\passwd.txt
```
If this is a partitioned server setup, add the = parameter to the command line to specify the NOTES.INI file in this partition's Domino data directory. For example, on Windows enter:
```
nserver -silent c:\myprofile.pds =c:\lotus\domino\data2\notes.ini
```
Check the errorlog.txt file in the Domino data directory to confirm that the setup is complete, or to view any error messages that were generated during setup.

To do a silent setup from a Windows client with Domino Administrator

Procedure

Make sure that you selected Remote server setup when you installed Domino Administrator on the client system.
Install the Domino server program files on a server system, but do not run the Domino server setup program.
At the command prompt on the server system, from the Domino program directory, do one of the following:
- On a Windows server, enter
```
nserver -listen
```
- On a UNIX server, enter
```
server -listen
```
At the command prompt on the client system, from the Notes® program directory, enter:
```
serversetup -silent c:\myprofile.pds -remote serveraddress
```
Where myprofile is the name you gave the setup profile and serveraddress is the host name or network address of the server you are setting up.

Note: If the profile file is not in the root directory, use the profile's full path in the command.
If the profile uses existing server, certifier, or administrator IDs that require passwords, do the following:
1. Create a text file that contains the passwords for the existing IDs. The keywords in this are:
  
  Server=
  
  AddServer=
  
  Certifier=
  
  OUCertifier=
  
  Administrator=
2. Add a parameter in the command line for the name of the password file. For example, on Windows enter:
```
serversetup -silent c:\myprofile.pds c:\passwd.txt -remote serveraddress
```
If this is a partitioned server setup, add the = parameter to the command line to specify the NOTES.INI file in this partition's Domino data directory. For example, on Windows enter:
```
serversetup -silent c:\myprofile.pds -remote serveraddress =c:\lotus\domino\data2\notes.ini
```
Check the errorlog.txt file in the Notes data directory to confirm that the setup is complete, or to view any error messages that were generated during setup.

To do a silent setup from a Windows client without Domino Administrator or from a UNIX workstation

About this task

Install the Domino server program files on a server system, but do not run the Domino server setup program.

Procedure

At the command prompt on the server system, from the Domino program directory, do one of the following:
- On a Windows server, enter
```
nserver -listen
```
- On a UNIX server, enter
```
server -listen
```
On the client system, install the Java™ runtime environment.
Create a temporary directory on the client system. For example, enter the following at the command prompt:
- On a Windows client:
```
mkdir c:\temp
```
- On a UNIX workstation:
```
mkdir /temp
```
Do one of the following:
- From a Windows client, copy the remote setup files CFGDOMSERVER.JAR, JHALL.JAR, and REMOTESETUP.CMD from the server to the directory you created on the client system. These files are in C:\Domino program directory on the server.
- From a UNIX workstation, copy the remote setup files CFGDOMSERVER.JAR, JHALL.JAR, and REMOTESETUP from the server to the directory you created on the workstation. These files located in the following directories:
  /Domino program directory/lotus/notes/latest/ibmpow/ on an IBM® AIX® server
  
  /Domino program directory/lotus/notes/latest/linux/ on a Linux™ server
At the command prompt on the client system, from the Notes program directory, enter:
```
remotesetup -silent c:\myprofile.pds -remote serveraddress
```
Where myprofile is the name you gave the setup profile and serveraddress is the host name or network address of the server you are setting up.

Note: If the profile file is not in the root directory, use the profile's full path in the command.
If the profile uses existing server, certifier, or administrator IDs that require passwords, do the following:
1. Create a text file that contains the passwords for the existing IDs. The keywords in this are:
  
  Server=
  
  AddServer=
  
  Certifier=
  
  OUCertifier=
  
  Administrator=
2. Add a parameter in the command line for the name of the password file. For example, on Windows enter:
  
  remotesetup -silent c:\myprofile.pds c:\passwd.txt -remote serveraddress
If this is a partitioned server setup, add the = parameter to the command line to specify the NOTES.INI file in this partition's Domino data directory. For example, on Windows enter:
```
remotesetup -silent c:\myprofile.pds -remote serveraddress =c:\lotus\domino\data2\notes.ini
```
Check the errorlog.txt file to confirm that the setup is complete, or to view any error messages that were generated during setup.