Solstice AdminSuite 2.3 Installation and Release Notes

Chapter 3 Solstice AdminSuite 2.3 Installation Procedures

This chapter provides the following information for the Solstice AdminSuite 2.3 product.

Installation Overview

The Solstice AdminSuite 2.3 software is installed using the admin_install script, found at the root level directory of the CD-ROM. You can use the installation script to install the software on systems in the network, as well as standalone systems. Help is available when you run the script, and the script is designed for you to easily install the Solstice AdminSuite 2.3 product.

The installation script provides the following options:

Install AdminSuite 2.3 and AutoClient 2.1
Install SunSoft Print Client (Solaris 2.3 - 2.5.1 only)
Install Software Usage Monitoring Toolkit
Set up systems to use AdminSuite and AutoClient

The software products that are available from the main menu are installed in different ways. Some products can be installed on a server and shared with other systems, while other products must be installed directly onto each system and cannot be shared. For example, the SunSoft Print Client product is installed directly onto the file system. The Solstice AdminSuite 2.3 product and software usage monitoring product can be installed on a single system and shared with others systems using the NFS distributed file system.

Though the script uses a self-documenting interface, this section describes the major options used by the script during the installation process.

Note -

The admin_install installation program cannot be used to install the software on diskless, dataless, or AutoClient system types.

Installation Process

The installation process involves a number of tasks, which are listed in Table 3-1. Some of these tasks may or may not be required to be performed, depending upon your system configuration. Review the tasks listed in Table 3-1and perform them in the order that they are listed. If one task is not required, simply skip to the next task.

Table 3-1 Task Map: Installing the Solstice AdminSuite 2.3 Software


Activity	Description	For Instructions, Go To
Remove Previously Installed Software	Before installing your new Solstice AdminSuite software, you must remove the old version of AdminSuite (AdminSuite2.2 or earlier). Skip this activity if you do not have a previous version of Solstice AdminSuite installed.	"How to Remove Previously Installed AdminSuite Software"
Become a Member of the sysadmin group	Before you can run the `admin_install` script, you must be a member of the sysadmin group on each host you wish to install. Skip this activity if you are already a member of the sysadmin group.	"How to Add Users to the sysadmin Group Using NIS+" "How to Add Users to the sysadmin Group Using NIS" "How to Add Users to the sysadmin Group Using Local `/etc` files"
Install Solstice AdminSuite and AutoClient	Use the `admin_install` script to install the Solstice AdminSuite 2.3 software on a Solstice file server, administration system, or AdminSuite enabled system.	"Installing the Solstice AdminSuite and AutoClient Software"
Install SunSoft Print Client	Optional. Install the SunSoft Print Client software only if you are running a version of Solaris 2.3 through 2.5.1.	"Installing the Solstice AdminSuite and AutoClient Software"
Install the Software Usage Monitoring Toolkit	(Optional) Install software usage monitoring.	"How to Install the Software Usage Monitoring Toolkit" "How to Set Up the Alias for `swusage_host`"
Register Printers With the Name Service	(Optional) Register printers with a name service (NIS or NIS+) without having to individually configure each print client with remote printer information.	Solstice AdminSuite 2.3 Print Administration Guide
Set Up Automounter Support	(Optional) If you selected the automounter mount method during the installation process, you must add entries to the automounter maps that indicate the location of the Solstice AdminSuite 2.3 software.	"How to Add Automount Support by Using NIS+" "How to Add Automount Support by Using NIS" "How to Add Automount Support by Using Local `/etc` Files"

Removing Previously Installed AdminSuite Software

Before you can install your new AdminSuite software, you must remove the previously installed AdminSuite software using the following procedure.

How to Remove Previously Installed AdminSuite Software

Change directories to the /cdrom/cdrom0 directory.

Remove the AdminSuite software using the following command line.

If you have the AdminSuite 2.2 software on your system, use the following command line. This command is found in the top level of the Solstice CD.

# ./rm_admin -v 2.2 -d /opt [-f]

In this command,

`-v` `option`	Represents the version of AdminSuite you wish to remove.
`-d` `option`	Represents the directory in which the AdminSuite software is installed.
`-f` `option`	(Optional) Forces the removal of software with no confirmation prompt.

Note -

If you do not specify a version or directory with the rm_admin command, by default, the version the command attempts to remove will be the 2.1 version located in the /export/opt directory.

Becoming a Member of the sysadmin Group

To install the Solstice AdminSuite 2.3 software, you must be a member of the sysadmin group for each host you specify during installation. The following procedures describe how to become a member of the sysadmin group for each name service the hosts can use. To learn more about the sysadmin group and security in the Solstice AdminSuite product, see the Solstice AdminSuite 2.3 Administration Guide.

Note -

You can now install the Solstice AdminSuite and AutoClient software as root on local systems; however, to install the software remotely, you must be a member of the sysadmin group.

How to Add Users to the sysadmin Group Using NIS+

Save the group table to a temporary file.

$ niscat group.org_dir > /var/tmp/group-file

Edit the file, adding the users you want to authorize to install the Solstice AdminSuite 2.3 software.

The following sample shows users added to the sysadmin entry in the group file.
. . . sysadmin::14:user1,user2,user3
In this example,

user1,user2,user3

Represent the users you are adding to the sysadmin group.

Merge the file with the NIS+ group table.
$ /usr/lib/nis/nisaddent -mv -f /var/tmp/group-file group
The results of the merge are displayed.

Remove the temporary file.
$ rm /var/tmp/group-file

Verification of Adding Users to the sysadmin Group Using NIS+

Verify that the user is a member of the sysadmin group by entering the following commands. Perform this step for each user you added to the file.

# su - user1
$ groups
staff sysadmin
$ exit

How to Add Users to the sysadmin Group Using NIS

Edit the group file (the default directory location is /etc), adding the users you want to authorize to install the Solstice AdminSuite 2.3 software.

The following sample shows users added to the sysadmin entry in the group file.
. . . sysadmin::14:user1,user2,user3
In this example,

user1,user2,user3

Represent the users you are adding to the sysadmin group.

Note -
The directory location of the group file is specified in the NIS makefile using the $DIR variable. Consult this file if you are uncertain of the location of the group file.

Change directory to the location of the NIS makefile (the default is /var/yp) and rebuild the NIS map.
# cd /var/yp # make group
Note -
Depending on the size of the NIS map, it may take several minutes or several hours to update the maps and propagate the changes throughout the network.

Verification of Adding Users to the sysadmin Group Using NIS

Verify that the user is a member of the sysadmin group by entering the following commands. Perform this step for each user you added to the NIS master.

# su - user1
$ groups
staff sysadmin
$ exit

How to Add Users to the sysadmin Group Using Local `/etc` files

Perform these steps for each system on which you want to use the Solstice AdminSuite 2.3 software.

Edit the /etc/group file, adding the users you want to authorize to install the Solstice AdminSuite 2.3 software.

The following sample shows users added to the sysadmin entry in the group file.
. . . sysadmin::14:user1,user2,user3
In this example,

user1,user2,user3

Represent the users you are adding to the sysadmin group.

Verification of Adding Users to the sysadmin Group Using Local `/etc` Files

Verify that the user is a member of the sysadmin group by entering the following commands. Perform this step for each user you added to the system.

# su - user1
$ groups
staff sysadmin
$ exit

Installing the Solstice AdminSuite and AutoClient Software

The following procedures describe how to install the Solstice AdminSuite and AutoClient software. To learn more about Solstice AdminSuite product, see the Solstice AdminSuite 2.3 Administration Guide.

How to Install Solstice AdminSuite and AutoClient Software

Insert the product CD into your CD-ROM drive.

If your system is not running Volume Management, you must mount the CD with the following commands before accessing it:
# mkdir /cdrom # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

Log in as a member of the sysadmin group for that system (group 14).

Note -
If you are installing the software on a local system, you do not have to be a member of the sysadmin group; you can install the software as root.

Verify that you are a member of the sysadmin group.
$ groups
If the sysadmin group is listed in the output, proceed to the next step. If not, follow the instructions in "Becoming a Member of the sysadmin Group".

Change directories to the product directory on the CD.
$ cd /cdrom/solstice_sysmgt_2_3

Run the admin_install script in the product directory.

Help is available during the installation. The main installation window shown below appears.

$ ./admin_install

Welcome to the Solstice Installation Program ...
 
To exit the installation process at any time, type 0
and press the Return key.
 
   1. Install AdminSuite 2.3 and AutoClient 2.1
   2. Install SunSoft Print Client (Solaris 2.3 - 2.5.1 only)
   3. Install Software Usage Monitoring Toolkit
   4. Set up systems to use AdminSuite and AutoClient
   5. Installation Help
 
Enter the number for one or more choices, separated by a space and
then press the Return key.
 
[default: 1]>>>

Enter option number 1 - Install AdminSuite 2.3 and AutoClient 2.1.

The AdminSuite Software Location window shown below appears.

AdminSuite Software Location
 
	1.	/opt
      
		Choose this option if you intend to support only one architecture
		of the software.
 
	2. /export/opt
 
		Choose this option if you need to support multiple architectures
		and if you will set up other systems that will NFS mount AdminSuite.
 
	3. Specify location
 
		Choose this option if you intend to set up other systems to NFS mount
		AdminSuite but you do not want to install the software in /export/opt.
 
   4. Installation Help
 
Type 1, 2, 3, or 4 and press the Return key.
 
[default: 1]>>>

Choose one of the following options that will install the software in the appropriate directory.

Option 1: /opt

This installation directory is the recommended directory; with this option, only one architecture can be used with the software. Once this option has been chosen, the following Installation Summary window appears.

==== Installation Summary ====
 
Product(s):				AdminSuite/AutoClient
Install Directory:	/opt
Host(s):	your_host_name
 
Start Installation
------------------
 
Do you want to start the installation?
			1. Start installation
			2. Cancel installation
 
>>>

After confirming that the directory and host are correct, enter 1 to continue with the installation. You will see a scrolling list of the log activities. If the installation is successful, the following message will display in your installation window:

Successfully installed product: AdminSuite/AutoClient

Option 2: /export/opt

This option enables you to support multiple architectures and enables you to set up other systems that use NFS to mount AdminSuite. Once this option is chosen, you have to specify how clients will mount the AdminSuite software. The following window appears.

How will clients mount this software?
 
	1. Systems will use the automounter
 
       Choose this option if you will be configuring the automounter
       for clients to access the software.
 
	2. Systems will mount via /etc/vfstab file
 
	   Choose this option if you will be setting up clients to use
      the /etc/vfstab to mount the software. A symlink will be made
      on the file server in /opt to point to the installation 
      directory.
 
	3. Installation Help
 
Type 1, 2 or 3 and press the Return key.
 
[default: 1]>>>

a. Choose the desired mount method.

Note -

If you choose Option 1: Systems will use the automounter, this option enables clients to access the AdminSuite software using the automounter mount method. If you choose this method, you will need to add entries indicating the location of the Solstice AdminSuite software to the automounter maps. Refer to Chapter 4, Adding Solstice AdminSuite 2.3 Support to the Automounter, for information about how to configure your automounter maps.

A note appears reminding you that you will have to add entries to your automounter map indicating where AdminSuite is installed. Press the Return key to continue.

The following AdminSuite Supported Platforms window appears.

AdminSuite Supported Platforms
 
	1.	sparc
 
		Choose this option if you intend to manage systems based
		on the SPARC platform.
 
	2.	i386
 
		Choose this option if you intend to manage systems based
		on the Intel x86 or Pentium platform.
 
Enter one or more choices separated by a space and then press the
Return key.
 
[default: 1]>>>

b. Choose the appropriate platform or platforms.

An Installation Summary window appears that looks similar to the following window.

==== Installation Summary ====
 
Product(s):				AdminSuite/AutoClient
Install Directory:	/export/opt
Architecture(s)	sparc    i386
Mount method	Edit client vfstab or User configured automounter
Host(s):	your_host_name
 
Start Installation
------------------
 
Do you want to start the installation?
 
	1. Start installation
	2. Cancel installation
 
>>>

c. After confirming the information provided in the Installation Summary window, type 1 and press Return to continue with the installation.

You will see a scrolling list of the log activities. If the installation is successful, the following message will display in your installation window:

Successfully installed product: AdminSuite/AutoClient

Option 3: Specify location

This option enables you to specify the location of the AdminSuite software. If you chose this option, you must enter the path where you wish to have the AdminSuite software installed.

Note -

If you install additional software, you must use the location that you specified in this step.

a. Enter the full pathname to the directory where you wish to install AdminSuite and then Press Return.

The following window appears.

How will clients mount this software?
 
	1.	Systems will use the automounter
 
		Choose this option if you will be configuring the automounter
		for clients to access the software.
 
	2.	Systems will mount via /etc/vfstab file
 
		Choose this option if you will be setting up clients to use
		the /etc/vfstab to mount the software. A symlink will be made
		on the file server in /opt to point to the installation directory.
 
	3.	Installation Help
 
		Type 1, 2 or 3 and press the Return key.
 
[default: 1]>>>

b. Choose the desired mount method.

Note -

If you choose option 1: Systems will use the automounter, this option enables clients to access the AdminSuite software using the automounter mount method. If you choose this method, you will need to add entries indicating the location of the Solstice AdminSuite software to the automounter maps. Refer to Chapter 4, Adding Solstice AdminSuite 2.3 Support to the Automounter, for information about how to configure your automounter maps.

A note appears reminding you that you will have to add entries to your automounter map indicating where AdminSuite is installed. Press the Return key to continue.

The following AdminSuite Supported Platforms window appears.

AdminSuite Supported Platforms
 
	1.	sparc
 
		Choose this option if you intend to manage systems based
		on the SPARC platform.
 
	2. i386
 
		Choose this option if you intend to manage systems based
		on the Intel x86 or Pentium platform.
 
Enter one or more choices separated by a space and then press the
Return key.
 
[default: 1]>>>

c. Choose the appropriate platform or platforms.

An Installation Summary window appears that looks similar to the following window.

==== Installation Summary ====
 
Product(s):				AdminSuite/AutoClient
 
Install Directory:	/export
Architecture(s)	sparc    i386
 
Mount method	Edit client vfstab or User configured automounter
 
Host(s):	your_host_name
 
 
Start Installation
------------------
 
Do you want to start the installation?
 
	1. Start installation
	2. Cancel installation
 
>>>

d. Verify the information provided in the Installation Summary window; type 1 and press Return to continue with the installation.

You will see a scrolling list of the log activities. If the installation is successful, the following message will display in your installation window: Successfully installed product: AdminSuite/AutoClient

Update your shell search path to include the location of the Solstice AdminSuite commands.

If you use the C shell, type:
% set path = ( $path /opt/SUNWadm/bin ) % set MANPATH = ( $MANPATH /opt/SUNWadm/man )
To permanently affect these changes to your shell search path, edit your .cshrc or .login startup file.

If you use the Bourne or Korn shell, type:
$ PATH = $PATH:/opt/SUNWadm/bin $ MANPATH = $MANPATH:/opt/SUNWadm/man
To permanently affect these changes to your shell search path, edit your .profile startup file.

Start the Solstice Launcher (which now contains the Solstice AdminSuite applications).
$ /usr/bin/solstice &

Installing SunSoft Print Client

If you are running a version of Solaris 2.3 through 2.5.1, you will need to install updated print client packages. You can do this using the same installation script you use to install the AdminSuite and AutoClient software (admin_install script located in the root directory). The following procedure describes how to install the SunSoft print client packages.

If you have already installed SunSoft print client packages with a previous version of AdminSuite (for example, AdminSuite 2.2 or 2.1), you do not need to re-install these print packages.

How to Install the SunSoft Print Clients

Insert the product CD into your CD-ROM drive.

If your system is not running Volume Management, you must mount the CD with the following commands before accessing it:
# mkdir /cdrom # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

Log in as a member of the sysadmin group for that system (group 14).

Note -
If you are installing the software on a local system, you do not have to be a member of the sysadmin group; you can install the software as root.

Verify that you are a member of the sysadmin group.
$ groups
If the sysadmin group is listed in the output, proceed to the next step. If not, follow the instructions in "Becoming a Member of the sysadmin Group".

Change directories to the product directory on the CD.
$ cd /cdrom/solstice_sysmgt_2_3

Run the admin_install script in the product directory.

Help is available during the installation. The main installation window shown below appears.

$ ./admin_install

Welcome to the Solstice Installation Program ...
 
To exit the installation process at any time, type 0
and press the Return key.
 
	1. Install AdminSuite 2.3 and AutoClient 2.1
	2. Install SunSoft Print Client (Solaris 2.3 - 2.5.1 only)
	3. Install Software Usage Monitoring Toolkit
	4. Set up systems to use AdminSuite and AutoClient
	5. Installation Help
 
Enter the number for one or more choices, separated by a space and
then press the Return key.
 
[default: 1]>>>

Select option number 2 - Install SunSoft Print Client.

The following warning appears:

WARNING:	Installing the SunSoft Print Client software replaces 
the existing Solaris print software (LP) with new print
commands and a new print configuration interface.
 
If you upgrade the system to the Solaris 2.4, 2.5 or 2.5.1
 
OS Release after installing the SunSoft Print Client software,
you must re-enable the print commands in the /usr/ucb
directory by running the /usr/lib/print/upgrade_fix script.
 
Press the Return key to continue or 0 to exit the installation.
>>>

Press the Return key to continue with the installation.

The following menu appears.

Printer Configuration
 
1.	Do not convert local Solaris print (LP) printer configuration
	Choose this option if you plan to maintain printers centrally
	using the NIS or NIS+ name service.
 
2.	Convert local Solaris print (LP) printer configuration
	Choose this option if you want to access remote printers by
	using local configuration files. The Solaris print (LP)
	configuration data will be used.
 
3. Installation Help
 
Type 1, 2 or 3 and press the Return key.
 
[default: 1]>>>

Choose the desired option.

You will see an Installation Summary window similar to the following.

==== Installation Summary ====
 
Product(s):				SunSoft Print Client software
 
Host(s):	your_host_name
 
Start Installation
------------------
 
Do you want to start the installation?
			1. Start installation
			2. Cancel installation
 
>>>

Verify that the information in the Installation Summary is correct; type 1 and press Return to start the installation.

You will see a scrolling summary of the SunSoft print client software installation; if the print client packages were installed correctly, you will see the following message:
Successfully installed product: SunSoft Print Client software

Installing Software Usage Monitoring Toolkit

The software usage monitoring toolkit enables you to install software usage monitoring on clients or on multiple servers. For instance, you may be running software usage monitoring on multiple servers that share the software usage monitoring software among multiple hosts, or you could run software usage monitoring in a client/server environment. Each of these environments are set up differently; however, regardless of which environment you use software usage monitoring in, it operates basically the same.

Note -

If you have already installed software usage monitoring from a previous release of AdminSuite, you do not need to install it again.

The following procedure describes how to install the software usage monitoring toolkit.

How to Install the Software Usage Monitoring Toolkit

Log in as a member of the sysadmin group (group 14).

Note -
If you are installing the software on a local system, you do not have to be a member of the sysadmin group; you can install the software as root.

Verify that you are a member of the sysadmin group.
$ groups
If the sysadmin group is listed in the output, proceed to the next step. If not, follow the instructions in "Becoming a Member of the sysadmin Group".

Change directories to the product directory on the CD.
$ cd /cdrom/solstice_sysmgt_2_3

Run the admin_install script in the product directory.

Help is available during the installation.

$ ./admin_install

The main installation window shown below appears.

Welcome to the Solstice Installation Program ...
 
To exit the installation process at any time, type 0
and press the Return key.
 
   1. Install AdminSuite 2.3 and AutoClient 2.1
   2. Install SunSoft Print Client (Solaris 2.3 - 2.5.1 only)
   3. Install Software Usage Monitoring Toolkit
   4. Set up systems to use AdminSuite and AutoClient
   5. Installation Help
 
Enter the number for one or more choices, separated by a space and
then press the Return key.
 
[default: 1]>>>

Choose the option 3: Install Software Usage Monitoring Toolkit.

This option enables you to choose the software usage monitoring system type from the following menu.

Software Usage Monitoring System Type
 
	1. Install Software Usage Monitoring Client
	2. Install Software Usage Monitoring Server
	3. Installation Help
 
Enter the number for one or more choices, separated by a space and
then press the Return key.
[default: 1]>>>

Choose option 1 or 2 depending upon the system type (client or server) you wish to install.

You will see an Installation Summary window similar to the following.

==== Installation Summary ====
 
Product(s):		Software Usage Monitoring Client software
 
Host(s):	lorna
 
Start Installation
------------------
 
Do you want to start the installation?
 
	1. Start installation
	2. Cancel installation
 
>>>

Note -

For each client you wish to run software usage monitoring on, you will have to run the installation script for each client.

Alias the server you wish to be the host server to swusage_host.

Refer to "How to Set Up the Alias for swusage_host" for information about how to set the alias swusage_host to your server.

How to Set Up the Alias for `swusage_host`

Start the Database Manager provided with the Solstice Launcher.

Note -
See the Solstice AdminSuite 2.3 Administration Guide for detailed information about how to use the Database Manager.

Select the name service used with your computer network.

You can chose NIS, NIS+, or none.

Check that the domain or host name is correct.

If not, type the domain or host name you need to access.

Select the Hosts file.

Click on OK.

The Database Manager main window is displayed with the file contents displayed.

Select the host you wish to designate as the swusage_host.

From the Edit pull-down menu, choose Modify.

In the Database Manager Modify pop-up window, add swusage_host to the Aliases field.

Click on OK to save and apply the changes.

You should see that your addition is now listed in the aliases column for that host.

Verify that the swusage_host alias is set correctly.
$ ping swusage_host swu_host is alive
The ping command may produce a different line specifying that a different workstation other than swusage_host is alive; for example, the line may read buck is alive.

Example of Using the Database Manager to Set Up the Host Alias for Software Usage Monitoring.

This example shows how to set up the host alias for software usage monitoring using the Solstice Database Manager. In this example, the host alias of swusage_host needs to be set to the machine named buck.

Within the Database Manager Hosts Database window, select the host buck and then choose Modify from the Edit menu. The Modify window is displayed.

Within the Aliases field, you would enter the name swusage_host to represent the software usage monitoring host server. To apply and save these entries, click on OK.

Setting Up Systems to Use AdminSuite

If you wish to run AdminSuite software on a system or wish to administer systems using AdminSuite software, you must initially set these up. You can set up these systems using the installation script you used to install AdminSuite and AutoClient. The following procedure describes how to set up these systems.

How to Set Up Systems to Use AdminSuite and AutoClient

Insert the product CD into your CD-ROM drive.

If your system is not running Volume Management, you must mount the CD with the following commands before accessing it:
# mkdir /cdrom # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

Log in as a member of the sysadmin group for that system (group 14).

Note -
If you are running the installation script on a local system, you do not have to be a member of the sysadmin group; you can run the installation script as root.

Verify that you are a member of the sysadmin group.
$ groups
If the sysadmin group is listed in the output, proceed to the next step. If not, follow the instructions in "Becoming a Member of the sysadmin Group".

Change directories to the product directory on the CD.
$ cd /cdrom/solstice_sysmgt_2_3

Run the admin_install script in the product directory.

Help is available during the installation. The main installation window shown below appears.

$ ./admin_install

Welcome to the Solstice Installation Program ...
 
To exit the installation process at any time, type 0
and press the Return key.
 
	1. Install AdminSuite 2.3 and AutoClient 2.1
	2. Install SunSoft Print Client (Solaris 2.3 - 2.5.1 only)
	3. Install Software Usage Monitoring Toolkit
	4. Set up systems to use AdminSuite and AutoClient
	5. Installation Help
 
Enter the number for one or more choices, separated by a space and
then press the Return key.
 
[default: 1]>>>

Select Option 4 - Set up systems to use AdminSuite and AutoClient.

The following menu appears.

Set up systems to use AdminSuite and AutoClient
 
	1.	Set up systems to run AdminSuite
      
		Configure systems to NFS mount AdminSuite from a file server
		so that they can run the AdminSuite applications.
 
	2.	Set up systems to be managed
 
		Configure systems to NFS mount AdminSuite from a file server
		so that they can be managed by the administration applications.
 
	3. Installation Help
 
Type 1 or 2 and press the Return key.
[default: 1]>>>

Choose one of the following options that will either allow systems to run AdminSuite or be managed by AdminSuite.

Option 1: Set up systems to run AdminSuite

This option enables you to specify the systems you wish to be able to run AdminSuite from the server.

The following menu appears when you choose this option.

How should clients mount AdminSuite?
 
	1.	Software access will be via the automounter
		
		Choose this option if you want to configure the
		automounter for systems to access the software.
 
	2.	Systems will mount via /etc/vfstab file
 
		Choose this option to have this program update each
		systems /etc/vfstab file to access the software.
 
	3.	Installation Help
 
Type 1, 2 or 3 and press the Return key.
 
[default: 1]>>>

Choose the method in which the clients will mount the AdminSuite software from the server.

Option 1: Software access will be via the automounter

This option enables clients to access the AdminSuite software using the automounter mount method. If you choose this method, you will need to add entries indicating the location of the Solstice AdminSuite software to the automounter maps. Refer to Chapter 4, Adding Solstice AdminSuite 2.3 Support to the Automounter, for information about how to configure your automounter maps.

A note appears reminding you that you will have to add entries to your automounter map indicating where AdminSuite is installed. Press the Return key to continue.

Option 2: Systems will mount via /etc/vfstab file

This option enables clients to access the AdminSuite software using the /etc/vfstab file on the server where AdminSuite is installed. If you choose this method, the following window appears.
File Server Name The File Server is the system already installed with AdminSuite software that systems will access. Type the host name of the File Server and press the Return key. >>>
Type the name of the file server that has AdminSuite installed and then press the Return key.

The Systems for Installation menu is now in your window (see the following menu); enter the systems you wish to be able to remotely run AdminSuite.

Systems for Installation
 
Type the host names of the systems for installation.
List hosts separated by a single space (for example, 
hosta hostb hostc) and press the Return key.
 
You can also specify the path to a file that contains a 
list of hostnames (for example, /path/to/file).
 
[default: your_host_name]>>>

An Installation Summary screen appears.

==== Installation Summary ====
 
Product(s):	Set up systems to run AdminSuite
Host(s):	lorna
 
Start Installation
------------------
Do you want to start the installation?
 
	1. Start installation
	2. Cancel installation
 
>>>

Verify the information on the screen and, if it is correct, enter 1 to start the installation.

Option 2: Set up systems to be managed

This option enables you to specify the systems you wish to be able to manage using AdminSuite. The following menu appears when you choose this option.

How should clients mount AdminSuite?
 
	1.	Software access will be via the automounter
		Choose this option if you want to configure the
		automounter for systems to access the software.
 
	2.	Systems will mount via /etc/vfstab file
 
		Choose this option to have this program update each
		systems /etc/vfstab file to access the software.
 
	3.	Installation Help
 
Type 1, 2 or 3 and press the Return key.
 
[default: 1]>>>

Choose the method in which the clients will mount the AdminSuite software from the server.

Option 1: Software access will be via the automounter

This option enables clients to access the AdminSuite software using the automounter mount method. If you choose this method, you will need to add entries indicating the location of the Solstice AdminSuite software to the automounter maps. Refer to Chapter 4, Adding Solstice AdminSuite 2.3 Support to the Automounter, for information about how to configure your automounter maps. A note appears reminding you that you will have to add entries to your automounter map indicating where AdminSuite is installed. Press the Return key to continue.

Option 2: Systems will mount via /etc/vfstab file

This option enables clients to access the AdminSuite software using the /etc/vfstab file on the server where AdminSuite is installed. If you choose this method, the following window appears.
File Server Name The File Server is the system already installed with AdminSuite software that systems will access. Type the host name of the File Server and press the Return key. >>>
Type the name of the file server that has AdminSuite installed and then press the Return key.

The Systems for Installation menu is now in your window (see the following menu); enter the systems you wish to be able to remotely run AdminSuite.

Systems for Installation
 
Type the host names of the systems for installation.
List hosts separated by a single space (for example, hosta hostb hostc)
and press the Return key.
You can also specify the path to a file that contains a list of host
names (for example, /path/to/file).
 
[default: your_host_name]>>>

An Installation Summary screen appears.

==== Installation Summary ====
 
Product(s):		Set up systems to run AdminSuite
 
Host(s):	lorna
 
Start Installation
------------------
 
Do you want to start the installation?
 
	1. Start installation
	2. Cancel installation
 
>>>

Verify the information on the screen and, if it is correct, enter 1 to start the installation.

Troubleshooting

This section describes problems that you may encounter when you use the Solstice AdminSuite product. If you run into any of these problems, follow the advice that is provided.

Running the admin_install Script

If the admin_install script hangs, try re-running the script after waiting a few minutes. If the script continues to hang, try running it using another UID in the sysadmin group. If this fails, try adding yourself to the sysadmin entry in the /etc/group file on the system you wish to install.
If the admin_install script (running on system installed with Solaris 2.3 or 2.4 release) hangs after the following message is displayed:
Installing Solstice enabling packages ...

You can recover by becoming root and using the following commands.

# /usr/lib/nfs/mountd
# umount /usr/snadm/classes/tmp_system.2.1

Launching the Solstice AdminSuite

If you logged in as root and used the su command to become a member of group 14, the Solstice AdminSuite software may reject your requests. Log in as a user who is a member of group 14 rather than as root.
If you attempt to launch the Solstice AdminSuite software on a station manager using the solstice command and receive the following error message:
Solstice Registry Error [-14]: unable to locate registry

There are two possible conditions that can cause this error to arise.

The administration system was not installed with the software supporting its native platform. Reinstall the Solstice AdminSuite 2.3 software using the admin_install script, and add the software for the administration system's platform (for example, SPARC or x86).
The administration system was inadvertently installed using the automounter managed host mount method, when the /etc/vfstab file option should have been selected. Create the following links:
# ln -s /basedir/platform/SUNWadm /opt/SUNWadm # ln -s /basedir/all/SUNWadmd /opt/SUNWadmd

In these commands,

`basedir`	Is the directory where the software is installed.
`platform`	Is the station manager platform (either `sparc` or `i386`).

Upgrading to the Solaris 2.4 OS Release

If you upgrade a system installed with the Solstice AdminSuite 2.3 software and the Solaris 2.3 release to the Solaris 2.4 release, Printer Manager will not function properly. This occurs because an incorrect version of the FNS software is installed.

To correct this problem, you must remove the installed FNS software packages and replace them with correct versions found on the Solaris 2.5 or Solaris 2.5.1 CD.

Remove the FNS software:
# pkgrm SUNWfns SUNWfnspr

This step assumes that your system is running Volume Management. Insert the Solaris 2.5 or Solaris 2.5.1 CD into your CD-ROM drive, and install the correct version of the FNS software:

# pkgadd -d /cdrom/cdrom0/s0/Solaris_2.5 SUNWfns SUNWfnspr

Chapter 3 Solstice AdminSuite 2.3 Installation Procedures

Installation Overview

Installation Process

Removing Previously Installed AdminSuite Software

How to Remove Previously Installed AdminSuite Software

Becoming a Member of the sysadmin Group

How to Add Users to the sysadmin Group Using NIS+

Verification of Adding Users to the sysadmin Group Using NIS+

How to Add Users to the sysadmin Group Using NIS

Verification of Adding Users to the sysadmin Group Using NIS

How to Add Users to the sysadmin Group Using Local /etc files

Verification of Adding Users to the sysadmin Group Using Local /etc Files

Installing the Solstice AdminSuite and AutoClient Software

How to Install Solstice AdminSuite and AutoClient Software

Installing SunSoft Print Client

How to Install the SunSoft Print Clients

Installing Software Usage Monitoring Toolkit

How to Install the Software Usage Monitoring Toolkit

How to Set Up the Alias for swusage_host

Example of Using the Database Manager to Set Up the Host Alias for Software Usage Monitoring.

Setting Up Systems to Use AdminSuite

How to Set Up Systems to Use AdminSuite and AutoClient

Troubleshooting

Running the admin_install Script

Launching the Solstice AdminSuite

Upgrading to the Solaris 2.4 OS Release

How to Add Users to the sysadmin Group Using Local `/etc` files

Verification of Adding Users to the sysadmin Group Using Local `/etc` Files

How to Set Up the Alias for `swusage_host`