A machine acting as a networked ISL server must be running an SCO OpenServer system that includes TCP/IP. You cannot use the SCO OpenServer Desktop System as a remote installation server. The remote installation server you wish to use for a network installation must be able to identify the client you wish to boot by its machine name. Any SCO OpenServer software components on the server machine can be installed on client machines.
To prepare the installation server for clients' installation requests:
If you create several installation servers, assigning a different password for swadmin on each server increases security, as does changing the passwords frequently.
Supply the requested information about the client. This information includes system name, network card and parameters, IP address, netmask, broadcast address, and low-level Ethernet, or MAC, address. See the Getting Started Guide for a list of supported client network cards. If the server and client are on separate subnets, you must also supply the address for the gateway machine connecting them.
netisl client add saves this information for the client machine to use during installation. (The user at the client must also enter some information during installation.) netisl client add also configures the server to respond to the remote boot request from the client. netisl client del clientname... reverses netisl client add for the specified client(s).
Be sure to insert a new floppy disk before configuring each client, and label each one with the client name, IP address, and MAC address.
Once you have configured the server, you can run netisl client add (repeat steps 2 and 3) at any time, to specify new clients or edit the information on existing clients.
If you change the software selection available to clients on
the remote installation server, you must run the following command
on the server machine: netisl server on