Trusted Solaris Installation and Configuration

Client Configuration Tasks

Configuring a name service client is similar to configuring its master, except that configuration details the client receives from the master do not have to be repeated.

If the client machine was installed from a CD-ROM--you should expect to complete the configuration tasks in the following table. Depending on your site configuration, some procedures can be omitted.

Table 6-1 Task Map for Clients Installed from CD-ROM

Task 

Described 

"Initial Configuration"

Covers protecting the hardware, setting up the labels, and initializing the administration tools. 

"(Optional) Configuring Routing"

Covers how to set up static routing. 

"Configuring the Network"

Covers how to specify the hosts that are contacted during boot. 

"Connecting to the Name Server"

Covers how to connect to the name service. 

"Sharing Critical File Systems"

Covers how to share the home directory and mail server. 

"Finish Configuring the System"

Points you to auditing setup information, how to share and mount file systems, and how to delete the install user. 

If the client machine was installed over the network--you should expect to complete the configuration tasks in the following table in the appropriate role.

Table 6-2 Task Map for Clients Installed Over a Network

Role 

Task Responsibility After Network Installation 

secadmin role 

 

"SPARC: Protect Machine Hardware" or "IA: Protect the BIOS"

 

"Install the Name Service Master's label_encodings File"

 

"Copy the Name Service Master's Tnrhtp Database"

 

"Initialize the SMC Server", then "Assign Templates to Remote Hosts"

 

"Set Up Auditing to Match the Master Server"

 

"(Optional) Set Security Attributes on Mounted File Systems"

admin role 

 

"Mount the Diskette With Configuration Files"

 

"(Optional) Configuring Routing"

 

"Initialize the SMC Server", then "Add Hosts to be Contacted During Booting"

 

"(Optional) Remove the 0.0.0.0 Network"

 

"Copy the SMC Name Server Toolbox Definitions to the Client"

 

"Copy Network Files to the /etc Directory"

If the client machine was installed using JumpStart scripts--you should expect to complete the configuration tasks in the following table in the appropriate role.

Table 6-3 Task Map for Clients Installed Using JumpStart

Role 

Task Responsibility After Network Installation 

secadmin role 

 

"SPARC: Protect Machine Hardware" or "IA: Protect the BIOS"

 

"Set Up Auditing to Match the Master Server"

admin role 

 

"Initialize the SMC Server"

 

"Connecting to the Name Server"